• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Server Health not updating

<?xml version="1.0" encoding="ISO-8859-1"?>

<xport>
<meta>
<start>1340709480</start>
<step>10</step>
<end>1340710670</end>
<rows>120</rows>
<columns>1</columns>
<legend>
<entry></entry>
</legend>
</meta>
<data>
<row><t>1340709480</t><v>NaN</v></row>
<row><t>1340709490</t><v>NaN</v></row>
<row><t>1340709500</t><v>NaN</v></row>
[...] No data (NaN) for all rows!
</data>
</xport>

---

ps ax |grep sw-collectd
2654 ? Ssl 14:35 /usr/sbin/sw-collectd -C /etc/sw-collectd/collectd.conf -P /var/run/sw-collectd.pid

---

ls -al /opt/psa/var/health/data
total 12
drwxr-xr-x 3 root root 4096 Jun 12 09:54 .
drwxr-xr-x 3 root root 4096 Jun 12 09:52 ..
drwxr-xr-x 30 root root 4096 Jun 12 09:55 localhost

ls -al /opt/psa/var/health/data/localhost/
total 120
drwxr-xr-x 30 root root 4096 Jun 12 09:55 .
drwxr-xr-x 3 root root 4096 Jun 12 09:54 ..
drwxr-xr-x 2 root root 4096 Jun 12 09:54 cpu-0
drwxr-xr-x 2 root root 4096 Jun 12 09:54 cpu-1
drwxr-xr-x 2 root root 4096 Jun 12 09:54 cpu-2
drwxr-xr-x 2 root root 4096 Jun 12 09:54 cpu-3
drwxr-xr-x 2 root root 4096 Jun 24 14:58 df
drwxr-xr-x 2 root root 4096 Jun 12 09:55 disk-md0
drwxr-xr-x 2 root root 4096 Jun 12 09:55 disk-md1
drwxr-xr-x 2 root root 4096 Jun 12 09:55 disk-sda
drwxr-xr-x 2 root root 4096 Jun 12 09:55 disk-sda1
drwxr-xr-x 2 root root 4096 Jun 12 09:55 disk-sda2
drwxr-xr-x 2 root root 4096 Jun 12 09:55 disk-sda3
drwxr-xr-x 2 root root 4096 Jun 12 09:55 disk-sdb
drwxr-xr-x 2 root root 4096 Jun 12 09:55 disk-sdb1
drwxr-xr-x 2 root root 4096 Jun 12 09:55 disk-sdb2
drwxr-xr-x 2 root root 4096 Jun 12 09:55 disk-sdb3
drwxr-xr-x 2 root root 4096 Jun 12 09:54 interface
drwxr-xr-x 2 root root 4096 Jun 12 09:54 load
drwxr-xr-x 2 root root 4096 Jun 12 09:54 memory
drwxr-xr-x 2 root root 4096 Jun 12 09:54 processes
drwxr-xr-x 2 root root 4096 Jun 12 09:54 processes-Mail
drwxr-xr-x 2 root root 4096 Jun 12 09:54 processes-MySql
drwxr-xr-x 2 root root 4096 Jun 12 09:54 processes-Panel
drwxr-xr-x 2 root root 4096 Jun 12 09:54 processes-Web
drwxr-xr-x 2 root root 4096 Jun 12 09:54 swap
drwxr-xr-x 2 root root 4096 Jun 12 09:54 sw_mem-Mail
drwxr-xr-x 2 root root 4096 Jun 12 09:54 sw_mem-MySql
drwxr-xr-x 2 root root 4096 Jun 12 09:54 sw_mem-Panel
drwxr-xr-x 2 root root 4096 Jun 12 09:54 sw_mem-Web

ls -al /opt/psa/var/health/data/localhost/cpu-0/
total 1192
drwxr-xr-x 2 root root 4096 Jun 12 09:54 .
drwxr-xr-x 30 root root 4096 Jun 12 09:55 ..
-rw-r--r-- 1 root root 148656 Jun 26 13:40 cpu-idle.rrd
-rw-r--r-- 1 root root 148656 Jun 26 13:40 cpu-interrupt.rrd
-rw-r--r-- 1 root root 148656 Jun 26 13:40 cpu-nice.rrd
-rw-r--r-- 1 root root 148656 Jun 26 13:39 cpu-softirq.rrd
-rw-r--r-- 1 root root 148656 Jun 26 13:40 cpu-steal.rrd
-rw-r--r-- 1 root root 148656 Jun 26 13:40 cpu-system.rrd
-rw-r--r-- 1 root root 148656 Jun 26 13:39 cpu-user.rrd
-rw-r--r-- 1 root root 148656 Jun 26 13:40 cpu-wait.rrd
 
* Try to restart sw-collectd if you didn't restart it.

* Try to decrease "Interval" parameter in file "/etc/sw-collectd/collectd.conf".
Now it's 300. It means that every 300 seconds daemon collect values and put it to files.
You can set 100 or 200, for example. One time we had the same problem with interval.
Warning: If you set too little value, resource usage of server will be greatly increased.
 
i already did a restart.

interval is set to 100. i checked the status after approx. 5 minutes and saw some values for memory, disk usage and processes but not for apache, mysql, interfaces. now after 40 minutes all values are "0" again!

very interesting...
 
Try to make sw-collectd logging:

vi /etc/sw-collectd/collectd.conf

Add following after "LoadPlugin interface":

LoadPlugin logfile
<Plugin logfile>
LogLevel "debug"
File "/var/log/sw-collectd.log"
Timestamp true
</Plugin>

You can set LogLevel "debug" or "info".

Restart sw-collectd:
/etc/init.d/sw-collectd restart
Look at log file after 5-10 minutes passed:
less /var/log/sw-collectd.log

Maybe you will see some errors in log-file.
 
Having the same problem, with the health monitoring.
I enabled the logging and after 10 minutes this is all there is.

[2012-06-27 09:15:32] Exiting normally.
[2012-06-27 09:15:32] collectd: Stopping 5 read threads.
[2012-06-27 09:15:32] rrdtool plugin: Shutting down the queue thread. This may take a while.
[2012-06-27 09:15:34] Initialization complete, entering read-loop.

I'm using Plesk 11.0.9 upgraded from 10.4.4 On Ubuntu 10.04.4 LTS

edit:
after a few hours i see the following in the log:

[2012-06-27 12:01:01] processes plugin: Failed to open `/proc/27330/cmdline': No such file or directory.
[2012-06-27 12:01:01] processes plugin: Failed to open `/proc/27331/cmdline': No such file or directory.
[2012-06-27 12:01:01] processes plugin: Failed to open `/proc/27332/cmdline': No such file or directory.
[2012-06-27 12:01:01] processes plugin: Failed to open `/proc/27333/cmdline': No such file or directory.
[2012-06-27 12:01:01] processes plugin: Failed to open `/proc/27334/cmdline': No such file or directory.
[2012-06-27 12:01:01] processes plugin: Failed to open `/proc/27335/cmdline': No such file or directory.
[2012-06-27 12:01:01] processes plugin: Failed to open `/proc/27338/cmdline': No such file or directory.
[2012-06-27 12:01:01] processes plugin: Failed to open `/proc/27339/cmdline': No such file or directory.
[2012-06-27 12:01:01] processes plugin: Failed to open `/proc/27340/cmdline': No such file or directory.
[2012-06-27 12:01:01] processes plugin: Failed to open `/proc/27341/cmdline': No such file or directory.
[2012-06-27 12:02:41] processes plugin: Failed to open `/proc/10741/cmdline': No such file or directory.
[2012-06-27 12:02:41] processes plugin: Failed to open `/proc/10742/cmdline': No such file or directory.
[2012-06-27 12:02:41] processes plugin: Failed to open `/proc/10743/cmdline': No such file or directory.
[2012-06-27 12:04:21] processes plugin: Failed to open `/proc/13937/cmdline': No such file or directory.
[2012-06-27 12:04:21] processes plugin: Failed to open `/proc/13939/cmdline': No such file or directory.
[2012-06-27 12:06:01] processes plugin: Failed to open `/proc/18972/cmdline': No such file or directory.
[2012-06-27 12:06:01] processes plugin: Failed to open `/proc/18973/cmdline': No such file or directory.
[2012-06-27 12:06:01] processes plugin: Failed to open `/proc/18974/cmdline': No such file or directory.
[2012-06-27 12:07:41] processes plugin: Failed to open `/proc/29213/cmdline': No such file or directory.
[2012-06-27 12:07:41] processes plugin: Failed to open `/proc/29216/cmdline': No such file or directory.

and many many more like these.
 
Last edited:
sw-collectd debug logfile after 24 hours:

[2012-06-27 08:54:13] Initialization complete, entering read-loop.
[2012-06-27 10:43:01] Exiting normally.
[2012-06-27 10:43:01] collectd: Stopping 5 read threads.
[2012-06-27 10:43:01] rrdtool plugin: Shutting down the queue thread. This may take a while.
[2012-06-27 10:43:03] Initialization complete, entering read-loop.
[2012-06-27 10:51:24] processes plugin: Failed to open `/proc/28712/cmdline': No such file or directory.
[2012-06-27 10:51:24] processes plugin: Failed to open `/proc/28713/cmdline': No such file or directory.
[2012-06-27 14:36:23] processes plugin: Failed to open `/proc/17877/cmdline': No such file or directory.
[2012-06-27 18:16:23] processes plugin: Failed to open `/proc/4677/cmdline': No such file or directory.
[2012-06-27 18:16:23] processes plugin: Failed to open `/proc/4681/cmdline': No such file or directory.
[2012-06-27 18:16:23] processes plugin: Failed to open `/proc/4683/cmdline': No such file or directory.
[2012-06-27 20:34:43] processes plugin: Failed to open `/proc/15462/cmdline': No such file or directory.
[2012-06-27 20:59:43] processes plugin: Failed to open `/proc/17324/cmdline': No such file or directory.
[2012-06-28 01:01:23] processes plugin: Failed to open `/proc/14062/cmdline': No such file or directory.
[2012-06-28 01:01:23] processes plugin: Failed to open `/proc/14063/cmdline': No such file or directory.
[2012-06-28 01:01:23] processes plugin: Failed to open `/proc/14064/cmdline': No such file or directory.
[2012-06-28 01:01:23] processes plugin: Failed to open `/proc/14065/cmdline': No such file or directory.
[2012-06-28 02:59:43] processes plugin: Failed to open `/proc/7752/cmdline': No such file or directory.
[2012-06-28 03:06:23] processes plugin: Failed to open `/proc/8520/cmdline': No such file or directory.
[2012-06-28 06:14:43] processes plugin: Failed to open `/proc/21964/cmdline': No such file or directory.
[2012-06-28 06:38:03] processes plugin: Failed to open `/proc/4339/cmdline': No such file or directory.
[2012-06-28 06:39:43] processes plugin: Failed to open `/proc/20725/cmdline': No such file or directory.
 
sw-collectd debug logfile after 24 hours:
[2012-06-27 10:51:24] processes plugin: Failed to open `/proc/28712/cmdline': No such file or directory.
[2012-06-27 10:51:24] processes plugin: Failed to open `/proc/28713/cmdline': No such file or directory.
[2012-06-27 14:36:23] processes plugin: Failed to open `/proc/17877/cmdline': No such file or directory.
[2012-06-27 18:16:23] processes plugin: Failed to open `/proc/4677/cmdline': No such file or directory.
[2012-06-27 18:16:23] processes plugin: Failed to open `/proc/4681/cmdline': No such file or directory.
[2012-06-27 18:16:23] processes plugin: Failed to open `/proc/4683/cmdline': No such file or directory.

I guess thats a race condition. There is a small time window between checking the processlist and checking the entries in /proc/≤pid>

During this time the process with the PID 28712,28713 etc gets terminated. I think it shouldn't be anything to worry about ...
 
To everyone with a problem: take a look at http://forum.parallels.com/showthread.php?p=629338, section 3 (sw-collectd data collection interval is too low) and execute the proposed solution (even if you already have a large enough sw-collectd interval value). Note that it has important 3rd step.

Please report whether it helped you or not.

Regarding the "Failed to open `/proc/28712/cmdline': No such file or directory." errors. abdi is quite right. It is a harmless race condition in the collectd.
 
Mine is also down and none of the above has worked

I am on a CentOS 6.2 final with plesk 11 which just updated again on the 8th. Prior to the 8th the Health monitor was working fine and now, nothing. Everything is zeros. I did the restart and it says it restarted fine but that made no change in the monitor report.

Any other ideas plesk folks? I use the monitor quite a bit when working with mysql .....
 
Back
Top