Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#43738 - crond crashes with getrlimit error glibc 2.21-1

Attached to Project: Arch Linux
Opened by Gene (GeneC) - Sunday, 08 February 2015, 14:37 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 08 February 2015, 15:51 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: After updating glibc to 2.21-1 crond now crashes with:

crond[952]: PAM unable to dlopen(/usr/lib/security/pam_unix.so): /usr/lib/libpthread.so.0: symbol __getrlimit, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
crond[952]: PAM adding faulty module: /usr/lib/security/pam_unix.so
crond[952]: segfault at 59d6 ip 00000000000059d6 sp 00007fffea697798 error 14 in crond[400000+d000]
systemd-coredump[953]: Process 952 (crond) of user 0 dumped core.



Additional info:
* package version(s)
cronie 1.4.12-1
pam 1.1.8-5
glibc 2.21-1

* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Dave Reisner (falconindy)
Sunday, 08 February 2015, 15:51 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Working as intended
Comment by Gene (GeneC) - Sunday, 08 February 2015, 14:42 GMT
In case it's helpful:

# ls -l /usr/lib/security/pam_unix.so
52 -rwxr-xr-x 1 root root 51984 Jun 16 2014 /usr/lib/security/pam_unix.so*
Comment by Gene (GeneC) - Sunday, 08 February 2015, 15:06 GMT

Also - the errors and SEGV started after the glibc update - and have repeated on the hour, the half hour and at 1 minute past the hour.

The cron events are not processed - one key event is the nightly backups ... unfortunately.
Comment by Dave Reisner (falconindy) - Sunday, 08 February 2015, 15:39 GMT
You must restart crond (and anything else which uses dlopen on glibc libs) after a major glibc release. Nothing new here.
Comment by Gene (GeneC) - Sunday, 08 February 2015, 15:45 GMT
Yah duh on me - I thought I rebooted after the update but in fact it came in after. Will reboot and confirm all is well and close.

thanks

Loading...