hanj Veteran
Joined: 19 Aug 2003 Posts: 1490
|
Posted: Mon Oct 03, 2022 12:27 pm Post subject: No cron.hourly after cronie update [SOLVED] |
|
|
After updating cronie to sys-process/cronie-1.6.1-r1, now logsentry doesn't fire off on all of my gentoo servers.
I can manually execute /etc/cron.hourly/logsentry.cron and it works as expected.
My crontab seems to be working, along with items in cron.daily. Just cron.hourly is having a problem.
Nothing has changed with the logsentry/logcheck script in years.
I did the obvious /etc/init.d/cronie restart several times after the update.
Any ideas?
Code: |
[ebuild R ] sys-process/cronie-1.6.1-r1::gentoo USE="inotify pam -anacron (-selinux)" 147 KiB
[ebuild R ] app-admin/logsentry-1.1.1-r2::gentoo 30 KiB
|
Also, I added a test.cron script in /etc/cron.hourly that just echos "hourly test message" to eliminate logsentry/logcheck and did not receive that alert message.
Here is what's in the logs when grep'ing on hourly
Code: | Oct 2 04:22:01 comp CROND[26641]: (root) CMD ([ ! -f /etc/cron.hourly/0anacron ] && run-parts /etc/cron.weekly)
Oct 2 04:22:02 comp CROND[26636]: (root) CMDEND ([ ! -f /etc/cron.hourly/0anacron ] && run-parts /etc/cron.weekly)
Oct 2 04:36:33 comp CROND[858]: (root) CMDEND ([ ! -f /etc/cron.hourly/0anacron ] && run-parts /etc/cron.daily)
Oct 3 04:02:01 comp CROND[19443]: (root) CMD ([ ! -f /etc/cron.hourly/0anacron ] && run-parts /etc/cron.daily)
Oct 3 04:27:17 comp CROND[19439]: (root) CMDEND ([ ! -f /etc/cron.hourly/0anacron ] && run-parts /etc/cron.daily) |
UPDATE
I did a diff on the latest version...
Code: | colordiff cronie-1.6.1-r1.ebuild cronie-1.6.1-r2.ebuild
13c13
< KEYWORDS="~alpha amd64 arm arm64 hppa ~ia64 ~loong ~m68k ~mips ppc ppc64 ~riscv ~s390 sparc x86"
---
> KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~m68k ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86"
81c81
< doins contrib/dailyjobs
---
> doins contrib/{0hourly,dailyjobs}
|
This seems to be the problem. Weird that I'm the only one noticing this? Updating to sys-process/cronie-1.6.1-r2
UPDATE
Updating to cronie-1.6.1-r2 fixed it. _________________ Server Admin Blog - Uno-Code.com |
|