tailwatchd failed

zap1

New Member
Hi,

I recently got my VPS and am receiving an email from cpanel every day notifying me that:

Code:
tailwatchd failed @ [I]date/time[/I]. A restart was attempted automagically.
Service Check Method: [check command] tailwatchd is not running
It was being followed by another email, "exim failed" until yesterday when I upgraded to more memory. Now the tailwatchd email is being followed by an "imap failed" email.

Cpanel, my site and my email are always down when I check them after receiving these emails and I have to restart the container to get them running again.

Where is the best place to start looking for the cause of these problems? I have looked at tailwatchd_log but am not sure what to do with the info:
Code:
2009-05-14 16:35:09 UTC [Cpanel::TailWatch::ChkServd] Opened /usr/local/cpanel/logs/tailwatchd_log in append mode
2009-05-14 16:35:09 UTC [Cpanel::TailWatch::ChkServd] Opening /var/log/chkservd.log in append mode
2009-05-14 16:35:29 UTC [main] [STOP Ok] 28109
2009-05-14 16:35:29 UTC [Cpanel::TailWatch::Utils::Stop] 2009-05-14 16:35:29 UTC [main] Current process '28109' stopped
2009-05-14 16:35:29 UTC [Cpanel::TailWatch::ChkServd] Opened /usr/local/cpanel/logs/tailwatchd_log in append mode
2009-05-14 16:35:29 UTC [Cpanel::TailWatch::ChkServd] Opening /var/log/chkservd.log in append mode
2009-05-14 16:35:29 UTC [main] [START] 3734 1242318929
2009-05-14 16:35:29 UTC [Cpanel::TailWatch] Restored /var/log/exim_mainlog (size:1920333) to 1248727 (requested 1248727)
2009-05-14 16:35:29 UTC [Cpanel::TailWatch] Restored /var/log/maillog (size:1404701) to 1403639 (requested 1403639)
DBD::mysql::st execute failed: Duplicate entry '2009-05-14 12:08:02-1M4dTW-0006CS-5b-site@host.url' for key 1 at /usr/local/cpanel/Cpanel/TailWatch/Eximstats.pm line 352.
2009-05-14 16:35:29 UTC [Cpanel::TailWatch] Could not execute query, logging SQL to /var/cpanel/sql
2009-05-14 16:35:29 UTC [Cpanel::TailWatch::Eximstats] Opened /var/cpanel/sql/eximstats.sql in append mode
DBD::mysql::st execute failed: Duplicate entry '2009-05-14 12:08:02-1M4dTW-0006CU-9C-site@host.url' for key 1 at /usr/local/cpanel/Cpanel/TailWatch/Eximstats.pm line 352, <GEN0> line 3.
2009-05-14 16:35:29 UTC [Cpanel::TailWatch] Could not execute query, logging SQL to /var/cpanel/sql
DBD::mysql::st execute failed: Duplicate entry '2009-05-14 12:08:02-1M4dTW-0006Ca-CW-site@host.url' for key 1 at /usr/local/cpanel/Cpanel/TailWatch/Eximstats.pm line 352, <GEN0> line 4.
2009-05-14 16:35:29 UTC [Cpanel::TailWatch] Could not execute query, logging SQL to /var/cpanel/sql

-------lots more of these SQL messages removed-------

2009-05-14 16:35:31 UTC [Cpanel::TailWatch] Caught up /var/log/exim_mainlog to 1920333
2009-05-14 16:35:31 UTC [Cpanel::TailWatch] Reading back thirty lines of /var/log/exim_mainlog starting at 1903949
2009-05-14 16:35:31 UTC [Cpanel::TailWatch] Restoring /var/log/exim_mainlog to catch up position 1920333
2009-05-14 16:35:31 UTC [Cpanel::TailWatch] Restored /var/log/exim_mainlog to position 1920333
2009-05-14 16:35:31 UTC [Cpanel::TailWatch] Caught up /var/log/maillog to 1404701
2009-05-14 16:35:31 UTC [Cpanel::TailWatch] Reading back thirty lines of /var/log/maillog starting at 1388317
2009-05-14 16:35:31 UTC [Cpanel::TailWatch] Restoring /var/log/maillog to catch up position 1404701
2009-05-14 16:35:31 UTC [Cpanel::TailWatch] Restored /var/log/maillog to position 1404701
Any help is much appreciated.
 

Dan

Moderator
Hello Zap1,

After a bit of googling I have seen some recommendations to do a force update (in SSH /scripts/upcp --force) but if I were you I would submit a ticket to support and ask them to take a look at it for you. Could even link to your post here for reference for them.

It sounds like you're running out of memory but if you just upgraded I would think you wouldn't be having that problem still so my guess is that there is something wrong with a log or something causing tailwatchd to run away.

Hope that helps!
 

zap1

New Member
Thanks for your reply Dan. I received 39 of these emails overnight so will contact support.
 

MadMax

New Member
Me too.....I have over 30 emails since last night with failed processes including this one. I hope we can figure this out.:rolleyes:
 

KH-Paul

CTO
Staff member
MadMax,

Out of few tickets we've received related to this the following is the cause (sorted by how often it happens):
- Resource shortage in the VPS. Take a look at Resource Alerts screen in the Power Panel to see if anything is reported there;
- Process reached amount of memory specified on the WHM >> Server Configuration >> Tweak Settings screen. This one isn't really easy to confirm but this is quite a possibility in case of large log files, good amount of activity, etc;
- Some sort of a problem with cPanel installation. Usual fix is to run the "/scripts/upcp --force" to reinstall cPanel.
 

Dan

Moderator
Did this problem get sussed out for everyone? Do we know what was causing the problems?
 
Top