1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Cant start watchdog after fixing install...

Discussion in 'Plesk 9.x for Linux Issues, Fixes, How-To' started by scratt, Nov 1, 2010.

  1. scratt

    scratt Guest

    0
     
    Hi there,

    Probably my fault ultimately this. I managed to damage my Plesk install by not paying attention to some warnings that yum issued. But I was in fact trying to solve a host of PHP / Plesk related issues at the time - which were not of my doing!

    While working through the process of re-installing Plesk I managed to fix the PHP issues on the server, and it is now running flawlessly. I basically achieved that by using the CLI Plesk installer to overwrite existing (and some missing files - files that yum had trashed).

    The problem I have now is that the watchdog will not start up, and I get the same message that is being referred to in this thread : http://forum.parallels.com/showthread.php?t=100500

    I have worked through all the suggestions in that thread, and have also tried removing the Watchdog module, and reinstalling it both at the command line, and also via Plesk's GUI.

    I've also tried rebooting the server, several times. And manually restarting the watchdog components.
    I have also checked that the correct scheduled and startup tasks are in my Plesk settings. They are.
    But nothing seems to fix this problem.

    I would rather fix this than do a complete clean install on the server, for obvious reasons. And am quite happy to get my hands dirty doing so. But I cannot find enough technical information about the proper funtionality of the various daemons involved in making sure that it works..

    Is there a technical document?
    Or can someone suggest anything else I might try to resolve this?

    Thanks for any suggestions. :)
     
  2. IgorG

    IgorG Forums Analyst Staff Member

    49
    24%
    Joined:
    Oct 27, 2009
    Messages:
    24,557
    Likes Received:
    1,241
    Location:
    Novosibirsk, Russia
  3. scratt

    scratt Guest

    0
     
    Hi IgorG,

    Thanks for the quick reply. Yes, absolutely. I've worked through the entire setup, and resubmitted the values, just in case that would give the module a kick.

    I also referred to the troubleshooting notes in my post above, where I confirmed that I checked that the required event handlers were in place.
     
  4. IgorG

    IgorG Forums Analyst Staff Member

    49
    24%
    Joined:
    Oct 27, 2009
    Messages:
    24,557
    Likes Received:
    1,241
    Location:
    Novosibirsk, Russia
    The problem in that wdcollect cannot be started by init. This issue was already reported to developers. As possible workaround try to put attached script to /usr/local/psa/admin/bin/modules/watchdog and use it for starting wdcollect without inittab using.
    Also you can try to reinstall inittab package(sysvinit) with default settings and check how watchdog starts. And check that you have not duplicated records in /etc/inittab
     

    Attached Files:

    Last edited: Nov 1, 2010
  5. scratt

    scratt Guest

    0
     
    Hi IgorG,

    That seems to have fixed it. Thank you so much.
     
Loading...