Plesk Health Monitor not an RRD error

[bellini13]

I receive the error below after installing the Health Monitor for the first time.
Running Plesk 10.4.4 Update #20, on Linux 2.6.18-028stab095.1

{"status":"error","statusMessages":[{"status":"error","class":"","content":"rrdtool execution failed: ERROR: '\/usr\/local\/psa\/var\/health\/data\/localhost\/load\/load.rrd' is not an RRD file","title":"Error"}]}

i've tried to restart psa, and also tried to perform "detect hardware changes" and "revert to default configuration"

 

[bellini13]

bumping this topic, this issue still exists in microupdate 27

 

[bellini13]

bumping this topic, this issue still exists in microupdate 29

 

[bellini13]

bumping this topic, this issue still exists in microupdate 40

 

[bellini13]

finally after a lot of research and no help from parallels on this topic, I finally corrected the issue by simply following the steps in this topic http://forum.parallels.com/showthread.php?p=629338

The important step was "step 3" in which the existing data was removed from /usr/local/psa/var/health/data/localhost/
Once I deleted the existing folders/files and restarted the process, the original rdd error went away.

Now I am waiting for data to be collected, will report back with results.

3) sw-collectd data collection interval is too low

In previous Plesk versions sw-collectd data collection interval was not set explicitly. By default it is 10 or 0 (can't remember right now which one), the latter means "collect data as often as you can". This, obviously, usually results in noticeable CPU and other systems' load.

In Plesk 11 (on clean installations, i.e. not upgrades) this interval is set to 300 (5 minutes). However, upgraded installations will have their interval value unchanged. There is a serious reason for that: simply changing interval value in configuration file and restarting sw-collectd may lead to unexpected behavior. E.g. on my test installation just increasing this value led to rrdtool showing only either zero or NaN values.

Symptoms: sw-collectd process consumes a lot of CPU time and/or other resources.

Solution: properly set data collection interval to some reasonably high value. E.g. 300 seconds. I'm not entirely sure (so don't quote me on this), but I doubt setting it to lower value brings any benefits now, since Health monitor module rereads resource usage values at this rate. Note that to safely increase the interval you must drop entire previous statistics.

1. # /etc/init.d/sw-collectd stop
2. Edit file /etc/sw-collectd/collectd.conf to include 'Interval 300' line at top level. Replace '300' with your desired interval in seconds. E.g. (relevant chunk of file, just to give you a context):
Quote:
BaseDir "/usr/local/psa/var/health/data"
#TypesDB "/etc/sw-collectd/types.db"
FQDNLookup true
Hostname localhost
Interval 300
3. Notice the BaseDir and Hostname directives in the configuration file. From them a path to the statistics storage is assembled. You have to remove any collected data:
        # rm -rf /usr/local/psa/var/health/data/localhost/*
4. # /etc/init.d/sw-collectd restart