Cant start watchdog after upgrading..

[mike2010]

The only significant error i've noticed when upgrading from 9.2.3 to 9.3.

I cant turn on Watchdog. I get the following error when attempting to from Plesk -

Wdcollect service does not respond. Refer to Parallels technical support for help.

Any ideas ? I'm running CentOs 5

 

[mike2010]

anybody have an idea ? I'm not even sure what Wdcollect is for.

 

[mike2010]

Just checked my logs and they haven't been updating since I did the upgrade either.

none of my important logs are updating (the /var/log/ stuff )

Cant I get some kind of direction ? Everything seems to be running fine otherwise...The sites, databases , plesk all working... except for Watchdog and my Log reporting.

 

[mike2010]

the last logs from /var/log/messages 2 days ago -

Apr 2 16:23:05 host kernel: input: AT Translated Set 2 keyboard as /class/input/input1
Apr 2 16:23:56 host shutdown[3983]: shutting down for system reboot
Apr 2 16:23:56 host init: Switching to runlevel: 6
Apr 2 16:23:56 host wdcollect[2760]: Service is being stopped
Apr 2 16:23:56 host wdcollect[2760]: Server stopped
Apr 2 16:23:57 host smartd[2748]: smartd received signal 15: Terminated
Apr 2 16:23:57 host smartd[2748]: smartd is exiting (exit status 0)
Apr 2 16:23:57 host avahi-daemon[2666]: Got SIGTERM, quitting.
Apr 2 16:23:57 host avahi-daemon[2666]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::250:48ff:fe59:3743.
Apr 2 16:23:57 host avahi-daemon[2666]: Leaving mDNS multicast group on interface eth0.IPv4 with address my.server.ip.address.
Apr 2 16:24:03 host xinetd[2061]: Exiting...
Apr 2 16:24:07 host named[2190]: shutting down: flushing changes
Apr 2 16:24:07 host named[2190]: stopping command channel on 127.0.0.1#953
Apr 2 16:24:07 host named[2190]: no longer listening on 127.0.0.1#53
Apr 2 16:24:07 host named[2190]: no longer listening on my.server.ip.address#53
Apr 2 16:24:07 host named[2190]: exiting
Apr 2 16:24:09 host auditd[1860]: The audit daemon is exiting.
Apr 2 16:24:09 host kernel: audit(1274250649.572:149): audit_pid=0 old=1860 by auid=4294967295
Apr 2 16:24:09 host kernel: Kernel logging (proc) stopped.
Apr 2 16:24:09 host kernel: Kernel log daemon terminating.
Apr 2 16:24:10 host exiting on signal 15

 

[Expert]

anybody have an idea ? I'm not even sure what Wdcollect is for.

Watchdog is for restart frozen or die software (apache2, mysql, qmail e.t.c.)
In 9.3 I have some troubles with apache2 and mysql.

If I start apache with:
Listen 127.0.0.1:80
or other IPs
watchdog not see the runned apache and says that it is not run.
if start with:
Listen 80
it's all is ok

mysql start with:
/var/run/mysqld/mysqld.sock, but watchdog every minute write in log: connection established.

 

[mike2010]

Can somebody help ? Nobody seems to know why this is occuring. All my logs at /var/log/ except for the /httpd/ logs haven't reported anything since the update.

Cant get Watchdog to start either. I get the Wdcollect message.

I have php version 5.2.13 and apache 2.2.3

 

[mike2010]

Another update -

I think were getting close..

Log file at /usr/local/psa/var/modules/watchdog/log/monit.log

shows -

[PDT Apr 2 16:09:40] monit: pidfile `/var/run/sw-cp-server.pid' does not contain a valid pidnumber
[PDT Apr 2 16:09:41] monit: pidfile `/var/run/sw-cp-server.pid' does not contain a valid pidnumber
[PDT Apr 2 16:09:41] 'plesk_apache' failed to start
[PDT Apr 2 16:09:42] 'plesk_apache' service timed out and will not be checked anymore
[PDT Apr 2 16:23:56] Shutting down monit HTTP server
[PDT Apr 2 16:23:56] monit HTTP server stopped
[PDT Apr 2 16:23:56] monit daemon with pid [2762] killed

And the PID settings in :

/usr/local/psa/etc/modules/watchdog/monitrc

are :

set pidfile /usr/local/psa/var/modules/watchdog/run/monit.pidset statefile /usr/local/psa/var/modules/watchdog/run/monit.state

But I just checked the folder location at

/usr/local/psa/var/modules/watchdog/run/

and monit.pidset & monit.state are not listed there. The only file I can visibly see at that location is "securscan.sid"

Any ideas ?

 

[TylerR]

Have you tried removing the watchdog RPM manually

(rpm -e psa-watchdog)

and reinstalling it and running the latest autoinstaller?

/usr/local/psa/admin/bin/autoinstaller

 

[mike2010]

Have you tried removing the watchdog RPM manually

(rpm -e psa-watchdog)

and reinstalling it and running the latest autoinstaller?

/usr/local/psa/admin/bin/autoinstaller

Negative..

Plus, I dont see how this would help troubleshoot the bug. All I did was upgrade from 9.2.3 to 9.3 and now Watchdog's no good.

 

[mike2010]

Codero tech support put out a bug tracker ticket regarding this issue. Any update on the status from parallels is appreciated.

 

[mike2010]

Somehow it fixed itself on its own after doing a secondary Reboot.

During the initial reboot, Syslog never started on its own. So it had to be manually started. Then the secondary reboot must of knocked things back into place.

All is well again with Watchdog again.