cPanel update failure in upcp script - tailwatchd

vponteras

• December 20, 2017 03:55

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

• 

  rpvw

  • December 20, 2017 09:33

  Could you run the following code in a terminal and let us know what output you get
  awk '$4=="E"' /var/cpanel/updatelogs/update.xxxxxxxxxx.log
  (Replace the xxxxxxxxx with the number of the latest log file in /var/cpanel/updatelogs/)

  0
• 

  vponteras

  • December 20, 2017 09:38

  [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

  0
• 

  rpvw

  • December 20, 2017 09:56

  Try running /usr/local/cpanel/scripts/restartsrv_eximstats in a terminal and let us know the output

  0
• 

  vponteras

  • December 20, 2017 11:35

  [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.

  0
• 

  rpvw

  • December 20, 2017 14:02

  This looks like the error reported in the following thread: cPanel 68 - Maintenance ended due to eximstats error If you are unable to restart tailwatch using the command /scripts/restartsrv_tailwatchd you may need to open a support ticket to cPanel for assistance. More information on the TailWatch process can be found at TailWatch - cPanel Knowledge Base - cPanel Documentation

  0
• 

  cPanelMichael

  • December 20, 2017 18:03

  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:
  ps aux | grep [t]ailwatchd
  If so, try manually killing the process ID number you see in the output with a command like this:
  kill -9 PID
  Then, restart the tailwatchd process again:
  /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.

  0

Please sign in to leave a comment.