Tailwatchd - Can't locate integer.pm

[bikerdave]

Hi Folks,

any ideas what is causing this problem. I've been getting tailwatchd, exim and queueprocd errors but I can't figure out where it's going wrong. I'm getting messages every couple of minutes, which is a real pain.

I've tried forcing an update of cpanel using /scripts/upcp --force but it hasn't helped.

ATTENTION ATTENTION ATTENTION ATTENTION

The tailwatchd driver 'Cpanel::TailWatch::cPBandwd' (Cpanel/TailWatch/cPBandwd.pm) could not be initiated.

More specifically:

Can't locate integer.pm in @INC (@INC contains: /usr/local/cpanel /usr/local/cpanel/Cpanel/CPAN/overload/__Time /usr/lib/perl5/5.8.8/i686-linux /usr/lib/perl5/5.8.8 /usr/lib/perl5/site_perl/5.8.8/i686-linux /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7/i686-linux /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl/5.8.2 /usr/lib/perl5/site_perl/5.8.1 /usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl/5.6.2 /usr/lib/perl5/site_perl .) at /usr/local/cpanel/Cpanel/CPAN/overload/__Time/Time/Local.pm line 7.
BEGIN failed--compilation aborted at /usr/local/cpanel/Cpanel/CPAN/overload/__Time/Time/Local.pm line 7.
Compilation failed in require at /usr/local/cpanel/Cpanel/TailWatch/cPBandwd.pm line 33.

This is a tail of the tailwatchd_log

[2010-03-02 20:27:15 +0000] [Cpanel::TailWatch] [INFO] Caught up /var/log/maillog to 118784
[2010-03-02 20:27:15 +0000] [Cpanel::TailWatch] [INFO] Reading back thirty lines of /var/log/maillog starting at 102400
[2010-03-02 20:27:15 +0000] [Cpanel::TailWatch] [INFO] Restoring /var/log/maillog to catch up position 118784
[2010-03-02 20:27:15 +0000] [Cpanel::TailWatch] [INFO] Restored /var/log/maillog to position 118784

I'm hoping it makes sense to somebody becasue I'm stuck.

[Daniel]

Hi there,

I would try a perl modules check which seems to do a pretty good job of catching corrupt or missing perl modules and installing them again.

The command you'll want for this is:

/scripts/checkperlmodules --force

Give that a try and see what happens.

[bikerdave]

Tried it but unfortunately both exim and queueprocd are still showing as not running.


However, when I was having a search about, I found this..
http://linuxhostingsupport.net/blog/?p=519

I tried it and got exactly the same

root@host [~]# /scripts/restartsrv queueprocd
Sorry I don't know about queueprocd
root@host [~]#

I can't see anything about disabling the monitoring of queueprocd

and when I restart exim it looks as if it's running okay but WHM says it isn't.

root@host [~]# /scripts/restartsrv exim
Waiting for exim to restart..............finished.

exim (/usr/sbin/exim -bd -q60m) running as mailnull with PID 19557

exim started ok

[bikerdave]

I think I found it. It's monitored by ChkServd

[Daniel]

Originally Posted by bikerdave

I think I found it. It's monitored by ChkServd

Yep, it is. If you remove it from the config it *should* stop alerting you for it. You'll need to restart chkservd and/or cpanel to make sure the new configuration takes effect.

Did the tailwatchd emails stop after you did the checkperlmodules or are they still coming in?

In terms of why it thinks exim is not running is probably another issue separately. There's also a delay in what WHM shows for the service status, so if Exim was not running at the time it may take some time before it updates after you restarted the service.

Is exim running right now? (`ps aux|grep exim`)

[bikerdave]

It is..

mailnull 17911 0.0 0.1 6932 1208 ? S 21:31 0:00 /usr/sbin/exim -bd -q60m

I've unticked monitoring of tailwatchd, ChkServd and exim under service manager, which has stopped the emails coming in. I'm not sure if that's a good idea but it least it's leaving some room in my inbox for some spam instead.

[Daniel]

Originally Posted by bikerdave

It is..




I've unticked monitoring of tailwatchd, ChkServd and exim under service manager, which has stopped the emails coming in. I'm not sure if that's a good idea but it least it's leaving some room in my inbox for some spam instead.

Gotta love that spam.

That is a temporary fix for sure. If you don't care if cPanel monitors those services and restarts them when it sees an issue (assuming it's accurate) then leaving it unchecked is a fine fix.

You may want to submit a ticket and let a tech check the errors and configuration to see why it's actually having so we can get it to actually behave nicely for you.

[bikerdave]

Thanks Daniel, I'll probably go for that. It would be very helpful to get one of the team to cast an expert eye over it.

[Daniel]

Originally Posted by bikerdave

Thanks Daniel, I'll probably go for that. It would be very helpful to get one of the team to cast an expert eye over it.

You're welcome! It's what we're here for.