From: Green, Simon (Simon.Green@EU.ALTRIA.COM)
Date: Thu Feb 20 2003 - 07:32:27 EST
The simplest thing to do may be to kill these processes - including cron
itself. It should re-spawn.
It would be sensible to figure out what these defunct processes are and make
sure whatever the problem is gets cleared up. I presume that the problem
lies with a script scheduled from cron, rather than cron itself.
Simon Green
Altria ITSC Europe s.a.r.l.
AIX-L Archive at http://marc.theaimsgroup.com/?l=aix-l
<http://marc.theaimsgroup.com/?l=aix-l&r=1&w=2> &r=1&w=2
AIX FAQ at http://www.faqs.org/faqs/aix-faq/
<http://www.faqs.org/faqs/aix-faq/>
N.B. Unsolicited email from vendors will seldom be appreciated.
-----Original Message-----
From: Gipson, Mat [mailto:Mat.Gipson@AMERICREDIT.COM]
Sent: 19 February 2003 17:47
To: aix-l@Princeton.EDU
Subject: Problem with cron...
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!
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:16:36 EDT