glibc updated breaks running fcron daemon

08 August 2022, 15:49:57

Hi,

I noticed fcron fails to run my jobs sometimes after a system upgrade. I created a bug report here. (At first I was unsure of the cause and wrote a lot. Scroll to the bottom.) Now it seems it is a problem of with PAM.

Code: [Select]

authpriv.err: Aug  3 01:01:00 fcron[18828]: PAM unable to dlopen(/usr/lib/security/pam_unix.so): /usr/lib/libc.so.6: version `GLIBC_ABI_DT_RELR' not found (required by /usr/lib/libpthread.so.0)
authpriv.err: Aug  3 01:01:00 fcron[18828]: PAM adding faulty module: /usr/lib/security/pam_unix.so

readelf -s /usr/lib/security/pam_unix.so |grep GLIBC_ABI returnes nothing.

I found this arch linux forum post.
Restarting fcron works.

Now I need a reality check: IMHO it should be reasonable to expect, that an update doesn't bring daemons into a state, where they don't work anymore. But here, fcron is not run any jobs anymore, and it doesn't crash (which would be fine for fcron and actually fix the problem in this case). So it breaks the system.

Now, is this expectation reasonably, or does arch linux say: 'You have to reboot after every system upgrade!'?

Re: glibc updated breaks running fcron daemon

Reply #1 – 08 August 2022, 18:58:27

>Now, is this expectation reasonably, or does arch linux say: 'You have to reboot after every system upgrade!'?
For stuff like glibc or the kernel that would be a yes

Re: glibc updated breaks running fcron daemon

Reply #2 – 09 August 2022, 22:18:34

Some

Quote from: castilma – on 08 August 2022, 15:49:57

'You have to reboot after every system upgrade!'?

Definitely not. If you keep the kernel in the IgnorePkg array, you can be updating for months and years without the need for reboot. And even with the kernel updated, you won't notice much unless you try to modprobe a module. Some services though need a restart or reload if the symbols in linked libraries change - rsyncd comes to mind and also sshd.