[Bug 580438] New: cronie: The next instance cannot run
http://bugzilla.novell.com/show_bug.cgi?id=580438 http://bugzilla.novell.com/show_bug.cgi?id=580438#c0 Summary: cronie: The next instance cannot run Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: mseben@novell.com ReportedBy: mseben@novell.com QAContact: qa@suse.de Found By: --- Blocker: --- from Patrick : http://lists.opensuse.org/opensuse-factory/2010-02/msg00148.html ----- I replaced cron with cronie and experienced problems with repetitive processes hanging, expecially: */10 * * * * /usr/bin/mairix -p > /dev/null ----- The next instance cannot run because the previous has not cleared/ended. And the only thing I had done was install cronie. Reinstalling cron corrected the problem. ----- -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=580438 http://bugzilla.novell.com/show_bug.cgi?id=580438#c1 --- Comment #1 from patrick shanahan <pat@indy.rr.com> 2010-02-18 01:36:06 UTC --- it appears cronie is starting more than one, probably three instances of mairix. The database is being updated, but I am receiving the following email cron error reports: Date: Wed, 17 Feb 2010 20:20:01 -0500 (EST) From: Cron Daemon <root@wahoo.no-ip.org> To: pat@wahoo.no-ip.org Subject: Cron <pat@wahoo> /usr/bin/mairix -p > /dev/null Database /home/pat/mail/mairix_database appears to be locked by (pid,node,user)=(28734,wahoo,pat) Date: Wed, 17 Feb 2010 20:20:02 -0500 (EST) From: Cron Daemon <root@wahoo.no-ip.org> To: pat@wahoo.no-ip.org Subject: Cron <pat@wahoo> /usr/bin/mairix -p > /dev/null Database /home/pat/mail/mairix_database appears to be locked by (pid,node,user)=(28734,wahoo,pat) the database: 20:21 wahoo:~ > l mail/mairix_database -rw------- 1 pat users 34623716 2010-02-17 20:20 mail/mairix_database note that reverting to "cron" requires: rpm -e --force cronie -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=580438 http://bugzilla.novell.com/show_bug.cgi?id=580438#c2 --- Comment #2 from patrick shanahan <pat@indy.rr.com> 2010-02-18 01:38:34 UTC --- sould be rpm -e --nodeps cronie -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=580438 http://bugzilla.novell.com/show_bug.cgi?id=580438#c3 --- Comment #3 from Michal Seben <mseben@novell.com> 2010-02-18 07:38:34 UTC --- just a notice : for remove cronie use "zypper rm cronie" - zypper will install old cron automatically -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=580438 http://bugzilla.novell.com/show_bug.cgi?id=580438#c4 patrick shanahan <pat@indy.rr.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME --- Comment #4 from patrick shanahan <pat@indy.rr.com> 2010-02-18 13:32:58 UTC --- apparently updating from cron to cronie provided two or more instances of cron/crond running at the same time. Ending the extra processes solves the problem. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=580438 http://bugzilla.novell.com/show_bug.cgi?id=580438#c5 --- Comment #5 from Michal Seben <mseben@novell.com> 2010-03-26 09:56:57 UTC --- Hi Patrick, you were right, I found that after updating from cron to cronie old cron was still running, which lead to state when two daemons were running (old cron and new crond) I fix is in Base:System cronie I know, you close this bug as worksforme, I want just thank you for this bug report and testing cronie, so thanks ! -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com