You are not logged in.
I recently noticed that cron isn't working. I think this is since a recent glib update. journalctl --unit cronie.service says the following (several of these errors, with times that coincide with crontab entries):
Aug 14 10:45:01 arch crond[25151]: PAM unable to dlopen(/usr/lib/security/pam_unix.so): /usr/lib/libresolv.so.2: symbol __h_errno, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
Aug 14 10:45:01 arch systemd-coredump[25152]: Process 25151 (crond) of user 0 dumped core.
(I use cron instead of systemd timers as different users have different crontabs, something that I think systemd timers do not allow).
Any ideas on what I've done wrong?
Last edited by Quirky (2015-08-14 09:54:36)
Offline
Have you restarted the service? I generally do that after a glibc update.
Offline
Ah, maybe not. I have a 4 day uptime (Aug-10 I rebooted after a kernel update) and the date of the last glibc is Aug-6 but I'm not sure when it really was installed. Could be that glibc came in after Aug-10. I'll give that a go...
Offline
Thanks - that did the trick! I assumed I the latest glibc was used by everyone after a recent reboot, but obviously glibc was not installed on the 6th but some time after reboot.
Offline