From: Bob Booth - UIUC (booth@UIUC.EDU)
Date: Wed Feb 19 2003 - 13:13:56 EST
Something in the crontab that root or another user is attempting to run may
not be exiting properly.
Check all crontabs in /var/spool/cron/crontabs for possible program problems.
When the crontab is filed with crontab -e the crontab program attempts to
signal cron that a crontab has changed, so you don't have to signal cron
yourself. If cron is not responding, or can't be killed you will receive an
error message from the crontab command.
cron is set to respawn in /etc/inittab, so if you attempt to kill it without
turning it off in inittab, init will just start it up again.
bob
On Wed, Feb 19, 2003 at 11:46:57AM -0600, Gipson, Mat wrote:
> 7026-6H1
> AIX4.3.3
> ML10
>
> Cron seems to be in a zombie state with 2 child process that are defunct:
>
> #pstree 36728
> -+= 36728 root /usr/sbin/cron
> |--- 27892 calltech <defunct>
> \--- 31124 root <defunct>
>
> Also whenever I save a crontab I receive this error message:
>
> #crontab -e
> ....
> ....
> <shift+ZZ>
> 0481-120 The cron program may need to be started.
>
> ...however the cron process is already running!
>
> There have been no patches applied to this server. It is a clone of a test
> server and the test does not suffer the same issues. The result is that cron
> jobs don't run<obviously>....kind of stumped. I have already searched the
> archives. Any help offered is greatly appreciated!
>
> Mathew Gipson
> matt.gipson@americredit.com <mailto:matt.gipson@americredit.com>
> 817.525.7123
>
>
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:16:36 EDT