Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

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.

SOLVED The service tailwatchd appears to be down.

Discussion in 'General Discussion' started by imsarah, Dec 7, 2016.

Tags:
  1. imsarah

    imsarah Member

    Joined:
    Dec 7, 2016
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    hong kong
    cPanel Access Level:
    Root Administrator
    Hi there, I am receiving email alert saying the tailwatchd is down.

    Code:
    
    Dec 08 16:31:37  systemd[1]: Starting tailwatchd...
    Dec 08 16:31:37  restartsrv_tailwatchd[9700]: tailwatchd is already running (tailwatchd) with PID 17294 by root
    Dec 08 16:31:37  systemd[1]: tailwatchd.service: control process exited, code=exited status=1
    Dec 08 16:31:37  systemd[1]: Failed to start tailwatchd.
    Dec 08 16:31:37  systemd[1]: Unit tailwatchd.service entered failed state.
    Dec 08 16:31:37  systemd[1]: tailwatchd.service failed.
    

    Then I check using /scripts/restartsrv_tailwatchd --status. It says it is down and so I restart cpanel and force update cpanel

    Then the tailwatchd status is as follows:

    Code:
    tailwatchd is enabled
    Not running
      Driver (Active: 1) Cpanel::TailWatch::ChkServd
      Driver (Active: 1) Cpanel::TailWatch::RecentAuthedMailIpTracker
      Driver (Active: 1) Cpanel::TailWatch::MailHealth
      Driver (Active: 1) Cpanel::TailWatch::ModSecLog
      Driver (Active: 0) Cpanel::TailWatch::JailManager
      Driver (Active: 1) Cpanel::TailWatch::Eximstats
      Driver (Active: 1) Cpanel::TailWatch::cPBandwd
    

    Code:
    [17294] [2016-12-08 11:00:00 +1300] [Cpanel::TailWatch::Eximstats] Resetting email limits to new starttime of 1481148000
    [17294] [2016-12-08 12:00:00 +1300] [Cpanel::TailWatch::Eximstats] Resetting email limits to new starttime of 1481151600
    [17294] [2016-12-08 13:00:00 +1300] [Cpanel::TailWatch::Eximstats] Resetting email limits to new starttime of 1481155200
    [17294] [2016-12-08 14:00:00 +1300] [Cpanel::TailWatch::Eximstats] Resetting email limits to new starttime of 1481158800
    [17294] [2016-12-08 15:00:00 +1300] [Cpanel::TailWatch::Eximstats] Resetting email limits to new starttime of 1481162400
    [17294] [2016-12-08 16:00:00 +1300] [Cpanel::TailWatch::Eximstats] Resetting email limits to new starttime of 1481166000
    [10554] [2016-12-08 16:47:29 +1300] [Cpanel::TailWatch] [INFO] Opened /usr/local/cpanel/logs/tailwatchd_log in append mo                   de
    [10554] [2016-12-08 16:47:29 +1300] [Cpanel::TailWatch] [INFO] inotify support not available (Linux::Inotify2 missing or                    non-functional)
    [10554] [2016-12-08 16:47:29 +1300] [Cpanel::TailWatch] The tailwatchd driver 'Cpanel::TailWatch::JailManager' is not en                   abled.
    [10554] [2016-12-08 16:47:29 +1300] [Cpanel::TailWatch::Eximstats] Loading email sending limits from 1481166000 - 148116                   9600
    
    After a few minutes and recheck the status, TailWatchd is down again.
    How can I fix this?
    Thanks.
     
  2. imsarah

    imsarah Member

    Joined:
    Dec 7, 2016
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    hong kong
    cPanel Access Level:
    Root Administrator
    never mind. I have found that there are multiple process checking using
    ps aux |grep tail
    I killed the process manually in WHM and tailwatchd restarted sucessfully.
     
  3. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    38,658
    Likes Received:
    1,425
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Hello,

    I'm happy to see the issue is now resolved. Thank you for updating us with the outcome.
     
Loading...

Share This Page