The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

tailwatchd failed on ns1 and ns2

Discussion in 'General Discussion' started by nobodyk, May 11, 2011.

  1. nobodyk

    nobodyk Well-Known Member

    Joined:
    Aug 1, 2010
    Messages:
    90
    Likes Received:
    0
    Trophy Points:
    6
    tailwatchd failed @ Thu May 12 01:35:05 2011. A restart was attempted automagically.
    Service Check Method: [check command] tailwatchd is not running

    I keep getting these e-mails from my cpanel server. I check the tailwatchd --status and everything is running fine. I got a msg saying there's some queries that haven't been run, but I ran them manually and I'm still receiving the tailwatchd failed e-mails every hour.

    The title is tailwatchd failed on ns1.mydomain.com
    and the other email is tailwatchd failed on ns2.mydomain.com

    I'm running my nameservers on a cpanel dns cluster. When I logged in to ssh to my cpanel dns servers, tailwatchd wasn't running. Is that normal?
     
  2. cPanelTristan

    cPanelTristan Quality Assurance Analyst
    Staff Member

    Joined:
    Oct 2, 2010
    Messages:
    7,623
    Likes Received:
    21
    Trophy Points:
    38
    Location:
    somewhere over the rainbow
    cPanel Access Level:
    Root Administrator
    I've checked two DNS only machines to see what services it runs and tailwatchd does run on DNS only machines. Can you please check the cPanel tailwatchd log while trying to restart tailwatchd on one of the DNS only servers?

    Code:
    tail -fn0 /usr/local/cpanel/logs/tailwatchd_log
     
  3. nobodyk

    nobodyk Well-Known Member

    Joined:
    Aug 1, 2010
    Messages:
    90
    Likes Received:
    0
    Trophy Points:
    6
    I can't start tailwatchd on the dns servers, it's enabled, but I can't start it.

    tail -fn0 didn't work and froze my command line. I tried tail -20

    Code:
    [2011-05-12 13:58:59 +0400] [Cpanel::TailWatch] [INFO] Opened /usr/local/cpanel/logs/tailwatchd_log in append mode
    [2011-05-12 13:58:59 +0400] [main] [START] 7825 1305194339
    [2011-05-12 13:58:59 +0400] [Cpanel::TailWatch] [INFO] Restored /var/log/maillog (size:0) to 0 (requested 0)
    [2011-05-12 13:58:59 +0400] [Cpanel::TailWatch] [INFO] Restored /var/log/exim_mainlog (size:606544) to 2845 (requested 2845)
    [2011-05-12 13:58:59 +0400] [Cpanel::TailWatch] [INFO] Caught up /var/log/maillog to 0
    [2011-05-12 13:58:59 +0400] [Cpanel::TailWatch] [INFO] Reading back thirty lines starting at 0 (small file)
    [2011-05-12 13:58:59 +0400] [Cpanel::TailWatch] [INFO] Restoring /var/log/maillog to catch up position 0
    [2011-05-12 13:58:59 +0400] [Cpanel::TailWatch] [INFO] Restored /var/log/maillog to position 0
    install_driver(mysql) failed: Can't locate DBD/mysql.pm in @INC (@INC contains: /usr/local/cpanel /usr/local/cpanel/Cpanel/CPAN/overload/__Time /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .) at (eval 10) line 3.
    Perhaps the DBD::mysql perl module hasn't been fully installed,
    or perhaps the capitalisation of 'mysql' isn't right.
    Available drivers: DBM, ExampleP, File, Gofer, Proxy, SQLite, Sponge.
     at /usr/local/cpanel/Cpanel/TailWatch/Eximstats.pm line 252
    Same msg on both dns servers. The main cpanel server seems fine, tailwatchd is running.
     
    #3 nobodyk, May 12, 2011
    Last edited: May 12, 2011
  4. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    676
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Hello :)

    This particular error message indicates a problem with MySQL. You can try reinstalling the DBD::mysql Perl module via:

    Code:
    # /scripts/perlinstaller --force DBD::mysql
    Once that completes, you can restart Tailwatchd to determine if the issue persists:

    Code:
    # /scripts/restartsrv_tailwatchd
    Thank you.
     
  5. nobodyk

    nobodyk Well-Known Member

    Joined:
    Aug 1, 2010
    Messages:
    90
    Likes Received:
    0
    Trophy Points:
    6
    That worked, thanks Michael and Tristan.
     
Loading...

Share This Page