P
petters
Guest
WdExc error
Watchdog error is common Plesk panal. Sometime I also face the same server error.
Watchdog error is common Plesk panal. Sometime I also face the same server error.
Hi Paul,ThomasR: Check your file ownership & permissions.
Hi Paul,stats-graph.php appears to dynamically build images using data from the psa.module_watchdog_sys_stat MySQL table. If I were you, I'd take a look at some of the data to ensure it has valid dates in the time field. Worst case scenario, try backing up the data using an export of the table, then empty/truncate the table to start fresh.
Hi Paul,ThomasR: Double-check your crontab (if you commented out pack-sysstats earlier) and try restarting the psa daemon like so:
/etc/init.d/psa restart
Hello Everyone. Thank you for reporting and sorry for the inconvenience.
Please try attached fixes for Plesk 8.6, 9.x, 9.5.x and 10.x.
Please don't forget to backup original files before replacement.
1. unzip archive corresponding your Plesk version
2. replace pack-sysstats located in "/usr/local/psa/libexec/modules/watchdog/cp/".
3. replace stats-graph.php located in "/usr/local/psa/admin/htdocs/modules/watchdog/".
NOTE: This is latest updated fix
------------
I just updated Plesk yesterday and now a new watchdog email bug! Will this fix still work after the panel update?
Here is the new error:
/usr/local/psa/libexec/modules/watchdog/cp/pack-sysstats: line 1: ?php: No such file or directory
/usr/local/psa/libexec/modules/watchdog/cp/pack-sysstats: line 2: syntax error near unexpected token `"The file {$_SERVER['SCRIPT_FILENAME']} is part of Plesk 9 distribution. It cannot be run outside of Plesk 9 environment.\n"'
/usr/local/psa/libexec/modules/watchdog/cp/pack-sysstats: line 2: ` ***die("The file {$_SERVER['SCRIPT_FILENAME']} is part of Plesk 9 distribution. It cannot be run outside of Plesk 9 environment.\n");'
Me & Roland Leurs - we have Plesk 8.4.0...what can we do? Is it safe to try the 8.6 fix on a live server?
Watchdog weekly report Jan 1 said:Watchdog is running since Jan 17, 2011 01:00 AM.
Watchdog is monitoring services:
Plesk Web Server
Web Server (Apache)
SMTP Server (QMail)
IMAP/POP3 Server (Courier-IMAP)
DNS Server (BIND)
MySQL
Watchdog is not monitoring disks.
Security scans number: 0.
No events registered for the period.
Watchdog weekly report Jan 9 said:Watchdog is running since Jan 17, 2011 01:00 AM.
Watchdog is monitoring services:
Plesk Web Server
Web Server (Apache)
SMTP Server(Postfix)
IMAP/POP3 Server (Courier-IMAP)
DNS Server (BIND)
Tomcat
MySQL
Watchdog is monitoring:
[normal] /dev/vzfs (mount point /)
Security scans number: 0.
No events registered for the period.
Last week we updated all our servers with the provided patch. After all this works for the graphs in the Watchdog module itself, but now it comes out that the weekly reports still continue to falter:
For a Plesk 8.6 server:
For a Plesk 9.5.4 server:
Parallels, please do take you responsibility and test, debug and fix this annoying problem. I can open a support ticket for it, but as this is clearly a worldwide bug I refuse to do this.
Last week we updated all our servers with the provided patch. After all this works for the graphs in the Watchdog module itself, but now it comes out that the weekly reports still continue to falter:
For a Plesk 8.6 server:
For a Plesk 9.5.4 server:
Parallels, please do take your responsibility and test, debug and fix this annoying problem. I can open a support ticket for it, but as this is clearly a worldwide bug I refuse to do this.
Last week we updated all our servers with the provided patch. After all this works for the graphs in the Watchdog module itself, but now it comes out that the weekly reports still continue to falter:
Serguei Beloussov (Parallels CEO) and Birger Steen (Parallels President) said:Customer Support was mentioned as an area where Parallels needs to improve. As many of you know, we are changing our Customer Support processes to improve response and resolution times, and we also introduced a better quality control process. In addition to these changes, we are implementing a closer cooperation between our Engineering and Customer Support to be able to reduce the number of incidents in the first place.