I normally receive the /scripts/upcp log via email, but last night it failed. This has happened a few times over the past year or so.
(Sorry, I *know* that this issue has been discussed before but I failed to find it with repeated searches)
If anyone knows where a solution topic/post lies, please could they give me the URL (plus how you found it).
Otherwise, I may have narrowed down the problem, or this may be a red-herring, but I am perl-ically-challenged and having just "pulled an all-nighter" on my regular work, I would really appreciate any feedback from the Guru's out there.
So, I first checked /var/log/exim_mainlog - found the two previous day's email entries but none for last night.
# cat /var/run/upcp.pid shows two process id's but neither are still running (ps ax).
# crontab -l shows that the upcp on this server should run at 00:34 daily
# less /var/log/cron and /00:34 finds:-
May 20 00:34:01 mail crond[12733]: (root) CMD (/scripts/upcp)
May 20 00:34:24 mail crontab[12910]: (root) LIST (root)
May 20 00:34:24 mail /usr/bin/crontab[12912]: (root) LIST (root)
May 20 00:34:24 mail crontab[12913]: (root) LIST (root)
May 20 00:35:06 mail crond[13283]: (root) CMD (/usr/local/cpanel/bin/dcpumon >/dev/null 2>&1)
May 20 00:35:06 mail crond[13284]: (root) CMD (/usr/bin/test -x /usr/local/cpanel/bin/tail-check && /usr/local/cpanel/bin/tail-check)
May 20 00:35:14 mail /usr/bin/crontab[13397]: (root) LIST (root)
May 20 00:35:14 mail /usr/bin/crontab[13398]: (root) REPLACE (root)
May 20 00:36:01 mail crond[5204]: (root) RELOAD (cron/root)
May 20 00:38:01 mail crond[14735]: (root) CMD (/usr/local/cpanel/whostmgr/bin/dnsqueue > /dev/null 2>&1)
May 20 00:40:01 mail crond[15195]: (root) CMD (/usr/local/cpanel/bin/dcpumon >/dev/null 2>&1)May 20 00:36:01 mail crond[5204]: (root) RELOAD (cron/root) - that could be Trouble (with a capital "T") - Reloading crontabs when upcp has only been running for just over a minute? Looks "dodgy" to me.
Who's messing with root's crontab? Well another clue comes from http://configserver.com 's csf/lfd (thanks Chirpy!)
lfd tells me by email that a whole bunch of files got modified, including exim. http://changelog.cpanel.net/?tree=RE...revision=36167 confirms that exim was updated last night.
the hunt goes on...
# grep 'crontab -l' /scripts/*
/scripts/bupcp:@CT=split(/\n/,`crontab -l`);
/scripts/dnsqueuecron:my $crontab = `/usr/bin/crontab -l`;
/scripts/eximcron:my(@CRONTAB) = split(/\n/, `/usr/bin/crontab -l`);
Three suspects?
My guess is /scripts/eximcron (called from /scripts/buildeximconf )
But it is many hours since I last slept. I already enlarged the font in Firefox so that I could see the screen to post this
I hope I haven't wasted anyone's time (including mine)
If this post *does* lead to an accurate bug report - please feel free to file it at https://tickets.cpanel.net/submit/in...eqtype=tickets or wherever bug reports are meant to be sent.
Thanks for reading,
Marty
p.s. I have run /scripts/upcp 2>&1 | less
and it ran OK. I'm more concerned about *why* this issue occasionally occurs.



LinkBack URL
About LinkBacks
).
May 20 00:36:01 mail crond[5204]: (root) RELOAD (cron/root) - that could be Trouble (with a capital "T") - Reloading crontabs when upcp has only been running for just over a minute? Looks "dodgy" to me.
)
Reply With Quote





