unchecked eximstats - but it's still running and not disabled?

[aww]

Unchecked eximstats under the service manager under the "TailWatch Drivers"

Cpanel did it's thing and I thought it was stopped.

But I am still seeing eximstats queries in the mysql slow log?

I cannot find eximstats running under ps aux, but I never could so maybe it runs intermittently...

Since it's now under tailwatch I cannot find it under chkconfig --list either.

 

[cPanelTristan]

Could you try moving the eximstats database as well after stopping MySQL temporarily? Just move it out of /var/lib/mysql entirely to another location. After it has been moved, then start MySQL again.

You might also want to move the binary:

mv /usr/sbin/eximstats /usr/sbin/eximstats.bak

 

[aww]

Could you try moving the eximstats database as well after stopping MySQL temporarily? Just move it out of /var/lib/mysql entirely to another location. After it has been moved, then start MySQL again.

You might also want to move the binary:

mv /usr/sbin/eximstats /usr/sbin/eximstats.bak

Ah the idea was just to temporarily suspend it for a day to see if was contributing to load spikes, didn't want to do database deletion (or moving).

Certainly removing the binary is going to stop it, but where is it actually being called, I guess tailwatch is still firing away on it? Where can I examine the tailwatch configuration?

 

[cPanelTristan]

Yeah, tailwatchd would still be calling it. You can see the logs for tailwatchd at /usr/local/cpanel/logs/tailwatchd_log file.

You cannot examine the tailwatchd configuration itself as it's a binary at /usr/local/cpanel/bin/tailwatchd

 

[aww]

That's for all the details, good to know how eximstats works on cpanel.

The good news is it seems to have corrected itself and I don't see anymore eximstats mysql queries, didn't have to do anything but it took overnight to stop. Pretty sure the queries were not on delay so it might have just been tailwatch restarting itself or some other cache clearing.

 

[aww]

Aha! Nope it's not disabled, I'll have to investigate your other suggestions, this just showed up in the slow log - we had improved our mysql setup so it was faster and eximstats was now escaping the time limit

# [email protected]: eximstats[eximstats] @ localhost []
# Query_time: 1.562439  Lock_time: 0.000080 Rows_sent: 0  Rows_examined: 3970
use eximstats;
SET timestamp=1343701315;
update smtp INNER JOIN sends ON (sends.msgid=smtp.msgid) set smtp.processed=3 where smtp.transport_is_remote=1 and sends.user IN ('-remote-','root','mailman') and smtp.processed=0;

So still running a day or two later after disabled.

[319] [2012-07-28 15:27:47 -0400] [Cpanel::TailWatch::Utils::EnableDisable] [319] [2012-07-28 15:27:47 -0400] [main] 
Cpanel::TailWatch::Eximstats was successfully disabled

ps. Does the eximstats database table have all the indexes it should have for best performance?

 

[aww]

What do you think of just renaming /usr/local/cpanel/Cpanel/TailWatch/Eximstats.pm

I guess eximstats has two parts, one that collects the data into mysql, then the post-processor.

Either one or both of them is still firing.

 

[cPanelTristan]

It might be better off to open up a ticket for us to see why this is still running even after it has been unchecked. Even with tailwatchd handling it, it should stop running queries if you've unchecked the service.

 

[aww]

Not positive but I think I finally tracked this down.

eximstats builds a backlog of queries at /var/cpanel/sql/eximstats.sql

even though eximstats is off, cpanel checks to see if the log still exists, and if so, it slowly goes through the queries

I renamed the log and the queries seem to have stopped