Description of problem: Log watch not only runs at the scheduled time, but each time the server is rebooted. OK this is not a biggee, but it is a difference from previous behavior. Version-Release number of selected component (if applicable): FC10 as upgraded How reproducible: Each time a reboot Steps to Reproduce: 1. reboot 2. read email
Reassign to cronie component this is not logwatch bug.
I suppose you have logwatch in daily jobs (/etc/cron.daily). If you restart your computer before all daily jobs runned, then they will start again after reboot. Could you please attach log from /var/log/cron? Thank you.
Well all of the daily jobs should have run. Daily basically runs a 4am or there abouts and this problem has been observed in the noon to 5pm window.
Created attachment 327765 [details] this is the cron log It is running daily, and I am not sure why. PS this has happened more than once.
Created attachment 327766 [details] cron log Trying again. It didn't seem to like text last time.
OK I think I have this one. It is definately not rebooting that is doing this. It is the reboot after I do a yum update. and then only once. The sessions that seem to be causing this problem, and I am getting it once per server are ones that are doing a bunch of specific updates including something to the crontabs. Is it possible that installing an updated version of this file is messing with something?
This is possibly the same as bug 472275. It looks like that when vixie-cron was replaced by cronie then a cooperation between cron and anacron was seriously broken. Now anacron runs jobs completely disregarding if they were already perfomed or not and makes a mess. This happens in F8 and F9 and F10.
I am not sure what the trigger is, but my anacron occasionally runs cron.daily when it's already run for that day. I notice it because I get two logwatch emails for the same day.
Yeah I have been having this problem. Generally some times when I reboot. Usually seems to be related to doing an update. Interestingly enough I can reboot, do an update, and reboot. Then the second and not the first reboot will trigger this.
Yeah, I installed mgetty today and rebooted several times to make sure the stuff I put in /etc/event.d was all working. I wasn't paying attention to the order per se, but I installed a few packages and rebooted a couple times. logwatch (and cron.daily) ran as it was supposed to at 4 AM, then anacron ran it again at a quarter past 4 PM, and I got a second email.
I push update for testing. Please install crontabs and anacron from testing repository or go to the link below and let me know about possible problems. This solution is not nice, but it should be working. The bigger changes are planned for next release.
https://admin.fedoraproject.org/updates/anacron-2.3-66.fc10,crontabs-1.10-26.fc10
anacron-2.3-66.fc10, crontabs-1.10-26.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update anacron crontabs'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-1163
Could someone verify this fix?
(In reply to comment #14) > Could someone verify this fix? I will try it out.
[root@arturo ~]# yum --enablerepo=updates-testing --disableplugin=protectbase update anacron crontabs Setting up Update Process No Packages marked for Update Where are they?
Good question. Probably it takes more time to sync updates from bodhi to mirrors.
(In reply to comment #17) > Good question. Probably it takes more time to sync updates from bodhi to > mirrors. As soon as I get my hands on it, I will test it.
I think the real proof will be in several of us getting the update installed, and the doing at least a couple full yum updates and reboots and a couple more reboots over a period of a week or so. After all this one seems to be a bit elusive in exactly when it occurs, or at least that seems to be my experience.
I agree. The update stays in testing until confirmation from more users.
I can pretty much count on my system exhibiting this behavior after every reboot, so I'll start with that. But I agree also, input from others is required.
I'm experiencing this problem on fc9, booted last night at 02:25 after swapping some memory. Anacron started cron.daily at 02:25, it then delayed and ran normally again from crond at 04:02. I have some long running backup scripts in cron.daily that wound up running concurrently. The default 65 minute delay pushed the anacron started cron.daily to 03:30, then 000-delay.cron pushed it again 04:19. At the same time the crond cron.daily delayed until 04:50. Jan 31 04:40:55 run-parts(/etc/cron.daily)[18685]: starting 850.backup Jan 31 04:52:32 sizzo run-parts(/etc/cron.daily)[10450]: starting 850.backup Will the updated package only be going into f10?
The update will be also for F-9.
Installed anacron-2.3-66.fc10 and crontabs-1.10-26.fc10 on my system, and the behaviour of anacron after a reboot is normal. The fix looks good from here.
anacron-2.3-63.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing-newkey update anacron'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2009-1317
Seems to be fixed here too. (FC10)
This bug is now occurring in Redhat Enterprise Server.
Changes which lead to this bug weren't applied in RHEL. If you see jobs executed twice then I need more information about version of RHEL and releases of packages.
OK interesting. I ran an update on three of these servers and got the extra run of the log watch program that we have been seeing here. You might want to double check if this was indeed not pushed to this version. In the mean time I will see if I can duplicate the problem and will go through normal support channels if it is. I only noted here, because it was the same symptom.
I hope this was tested for a long time and well. Let's move it to stable.
anacron-2.3-66.fc10, crontabs-1.10-26.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
anacron-2.3-63.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 487686 has been marked as a duplicate of this bug. ***