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.

cPanel update failure in upcp script - tailwatchd

Discussion in 'General Discussion' started by vponteras, Dec 20, 2017.

Tags:
  1. vponteras

    vponteras Registered

    Joined:
    May 16, 2017
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Philippines
    cPanel Access Level:
    Root Administrator
    I am receiving this email notification. cPanel & WHM update failure in upcp script.

    I already did
    yum clean all
    yum update
    /scripts/upcp --force

    But still no luck
     
  2. rpvw

    rpvw Well-Known Member

    Joined:
    Jul 18, 2013
    Messages:
    582
    Likes Received:
    177
    Trophy Points:
    43
    Location:
    Spain
    cPanel Access Level:
    Root Administrator
    Could you run the following code in a terminal and let us know what output you get
    Code:
    awk '$4=="E"' /var/cpanel/updatelogs/update.xxxxxxxxxx.log
    (Replace the xxxxxxxxx with the number of the latest log file in /var/cpanel/updatelogs/)
     
    cPanelMichael likes this.
  3. vponteras

    vponteras Registered

    Joined:
    May 16, 2017
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Philippines
    cPanel Access Level:
    Root Administrator
    [root@vps centos]# awk '$4=="E"' /var/cpanel/updatelogs/update.1513762471.log
    [2017-12-20 04:39:03 -0500] E [/usr/local/cpanel/scripts/restartsrv_eximstats] The “/usr/local/cpanel/scripts/restartsrv_eximstats” command (process 10822) reported error number 255 when it ended.
    [2017-12-20 04:39:11 -0500] E Post Maintenance ended, however it did not exit cleanly (256). Please check the logs for an indication of what happened
     
  4. rpvw

    rpvw Well-Known Member

    Joined:
    Jul 18, 2013
    Messages:
    582
    Likes Received:
    177
    Trophy Points:
    43
    Location:
    Spain
    cPanel Access Level:
    Root Administrator
    Try running /usr/local/cpanel/scripts/restartsrv_eximstats in a terminal and let us know the output
     
    #4 rpvw, Dec 20, 2017
    Last edited: Dec 20, 2017
    cPanelMichael likes this.
  5. vponteras

    vponteras Registered

    Joined:
    May 16, 2017
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Philippines
    cPanel Access Level:
    Root Administrator
    [root@vps centos]# /usr/local/cpanel/scripts/restartsrv_eximstats
    Waiting for “tailwatchd” to restart ………Job for tailwatchd.service failed because the control process exited with error code. See "systemctl status tailwatchd.service" and "journalctl -xe" for details.
    …failed.

    Cpanel::Exception::Services::StartError
    Service Status
    tailwatchd (tailwatchd) is running as root with PID 1744 (systemd+/proc check method).

    Service Error
    (XID 9vm2xu) The “tailwatchd” service failed to start.

    Startup Log
    Dec 20 07:30:54 vps.litfirepublishing.com systemd[1]: Starting tailwatchd...
    Dec 20 07:30:54 vps.litfirepublishing.com restartsrv_tailwatchd[24877]: tailwatchd is already running (tailwatchd) with PID 1744 by root
    Dec 20 07:30:54 vps.litfirepublishing.com systemd[1]: tailwatchd.service: control process exited, code=exited status=1
    Dec 20 07:30:54 vps.litfirepublishing.com systemd[1]: Failed to start tailwatchd.
    Dec 20 07:30:54 vps.litfirepublishing.com systemd[1]: Unit tailwatchd.service entered failed state.
    Dec 20 07:30:54 vps.litfirepublishing.com systemd[1]: tailwatchd.service failed.

    tailwatchd has failed. Contact your system administrator if the service does not automagically recover.


    and tried restarting tailwatchd, but still got an error.
    [root@vps centos]# /scripts/restartsrv_tailwatchd
    Waiting for “tailwatchd” to restart ………Job for tailwatchd.service failed because the control process exited with error code. See "systemctl status tailwatchd.service" and "journalctl -xe" for details.
    …failed.

    Cpanel::Exception::Services::StartError
    Service Status
    tailwatchd (tailwatchd) is running as root with PID 1744 (systemd+/proc check method).

    Service Error
    (XID fknbd6) The “tailwatchd” service failed to start.

    Startup Log
    Dec 20 07:33:25 vps.litfirepublishing.com systemd[1]: Starting tailwatchd...
    Dec 20 07:33:25 vps.litfirepublishing.com restartsrv_tailwatchd[25251]: tailwatchd is already running (tailwatchd) with PID 1744 by root
    Dec 20 07:33:25 vps.litfirepublishing.com systemd[1]: tailwatchd.service: control process exited, code=exited status=1
    Dec 20 07:33:25 vps.litfirepublishing.com systemd[1]: Failed to start tailwatchd.
    Dec 20 07:33:25 vps.litfirepublishing.com systemd[1]: Unit tailwatchd.service entered failed state.
    Dec 20 07:33:25 vps.litfirepublishing.com systemd[1]: tailwatchd.service failed.

    tailwatchd has failed. Contact your system administrator if the service does not automagically recover.
     
  6. rpvw

    rpvw Well-Known Member

    Joined:
    Jul 18, 2013
    Messages:
    582
    Likes Received:
    177
    Trophy Points:
    43
    Location:
    Spain
    cPanel Access Level:
    Root Administrator
  7. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    41,509
    Likes Received:
    1,616
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Hello,

    This can happen on CentOS/CloudLinux 7 systems if the tailwatchd process is started outside of systemd. To solve this issue, check to see if a stale tailwatchd process is active on the server with the following command:

    Code:
    ps aux | grep [t]ailwatchd
    If so, try manually killing the process ID number you see in the output with a command like this:

    Code:
    kill -9 PID
    Then, restart the tailwatchd process again:

    Code:
    /scripts/restartsrv_tailwatchd
    This should allow it to start normally, and for the cPanel update to succeed. Note the following case in cPanel version 70 will address this issue:

    Fixed case CPANEL-17072: Make sure we can start tailwatchd processes with systemd.

    Thank you.
     
Loading...

Share This Page