Bug 114307 - 100's of cronds running, all stuck in either "do_for" or "coredu" state
Summary: 100's of cronds running, all stuck in either "do_for" or "coredu" state
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: vixie-cron
Version: 1
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jason Vas Dias
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-01-26 15:07 UTC by David Alden
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-08-04 21:06:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description David Alden 2004-01-26 15:07:34 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Gecko/20031114

Description of problem:
Load on this system jumped from an average of 0.2 to over 455.  A
ps shows 456 crond programs running.  It seems to be pairs of crond's
(a parent and a child) -- the parent is in "do_for" state and the
child is in "coredu".  Note that I have 7 machines (3 that are
100% identitical to this one) running FC1, none of the others have
exhibited this symptom.  A reboot fixed the problem.  It's only
occurred once even though this machine has been running FC1 for over
2 months.


Version-Release number of selected component (if applicable):
vixie-cron-3.0.1-76

How reproducible:
Couldn't Reproduce


Additional info:

Comment 1 Slava Kulik 2004-02-21 09:38:38 UTC
I see the same problem. I installed Fedora Core 1 on 5 machines, 4 of
them had this problem. All soon after being installed. After
rebooting, it never came back. but I'm running it for only 3 weeks, so
it might happen again. I'm using LDAP to manage user names and groups.
It might something to do with that. I don't know.

Comment 2 Jason Vas Dias 2004-08-04 21:06:46 UTC
never reoccurred with vixie-cron-4.1-+. Closing bug - unreproducible.


Note You need to log in before you can comment on or make changes to this bug.