Bug 154031 - Should report error and not run if prior cron.daily/monthly/etc is still running.
Should report error and not run if prior cron.daily/monthly/etc is still runn...
Status: CLOSED WORKSFORME
Product: Fedora
Classification: Fedora
Component: crontabs (Show other bugs)
5
All Linux
medium Severity medium
: ---
: ---
Assigned To: Marcela Mašláňová
Brock Organ
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-06 13:31 EDT by Orion Poplawski
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-11-14 08:14:30 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Orion Poplawski 2005-04-06 13:31:20 EDT
Description of problem:

We've been running into problems where scripts in cron.daily are hanging.  This
can result cases where you have multiple instances of cron.daily running.  It
would be useful if there was a pidfile and if valid that cron.daily aborted with
an error to alert the administrator.

This possibly could tie into a solution for bug #150228.

Version-Release number of selected component (if applicable):
crontabs-1.10-7

How reproducible:
Fairly
Comment 1 Jason Vas Dias 2005-08-01 16:01:07 EDT
I'm currently working on an enhancement that will provide a per-job cron option
or cron job syntax to run jobs "exclusively" - ie. not to run the next scheduled
instance of a job if the previous instance of the same job is still running.
Comment 2 Matthew Miller 2006-07-10 16:49:13 EDT
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!
Comment 3 Orion Poplawski 2006-07-10 17:03:19 EDT
Jason - I'm starting to see messages like:

/etc/cron.weekly/0anacron:

anacron: Cannot run - another anacron process is already running.: Resource
deadlock avoided

but I've only seen it for anacron.  Is it also in place for the normal crons?
Comment 4 Matthew Miller 2006-07-10 17:04:52 EDT
(Please note that FC4 is entering legacy status in a few weeks.)
Comment 5 Jitka Kozana 2006-08-31 08:43:12 EDT
Please update your system and try with the latest version of crontabs. Let me know, if the 
problem still occurs.
Thanks for cooperation.
Comment 6 Orion Poplawski 2006-08-31 13:30:18 EDT
Um, I don't see any evidence that there has been an update to crontabs.  It
seems like run-parts would need to be updated to use a per directory lock file. 
Comment 7 Marcela Mašláňová 2006-09-20 08:47:35 EDT
Problem from comment#3 are related with anacron. Try to update on anacron-2.3-
40.fc5 and let me know.
Thank you.

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