FS#36643 - [glibc][crond][pam] crond segfault due to linking symbol error in pam_unix.so
Attached to Project:
Arch Linux
Opened by PT. Ma. (BOYPT) - Friday, 23 August 2013, 07:06 GMT
Last edited by Dave Reisner (falconindy) - Friday, 23 August 2013, 11:39 GMT
Opened by PT. Ma. (BOYPT) - Friday, 23 August 2013, 07:06 GMT
Last edited by Dave Reisner (falconindy) - Friday, 23 August 2013, 11:39 GMT
|
Details
Description:
After a sys upgrade, cronie segfaults with this logs: Aug 23 14:45:01 lnode crond[6412]: PAM unable to dlopen(/usr/lib/security/pam_unix.so): /usr/lib/libpthread.so.0: symbol __call_tls_dtors, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference Aug 23 14:45:01 lnode crond[6412]: PAM adding faulty module: /usr/lib/security/pam_unix.so Aug 23 14:45:01 lnode kernel: crond[6412]: segfault at 58f6 ip 00000000000058f6 sp 00007fff387029c8 error 14 in crond (deleted)[400000+c000] Aug 23 14:45:01 lnode systemd-coredump[6413]: Process 6412 (crond) dumped core. I guess it's cause by upgrade of glibc (2.17-6 -> 2.18-2) Additional info: The system only enabled these repo: [core] [extra] [community] A few packages from AUR: # pacman -Qm geoip-citydata 20130311-1 gsutil 20110825-1 obfsproxy-git 20121205-1 openvpn-obfs 2.3.2-4 package-query 1.2-2 xapian-core-stable-with-cjk 1.2.6-1 xapian-python-bindings-stable 1.2.6-1 yaourt 1.3-1 Steps to reproduce: pacman -Syu journalctl -e |
This task depends upon
Closed by Dave Reisner (falconindy)
Friday, 23 August 2013, 11:39 GMT
Reason for closing: Not a bug
Additional comments about closing: This happens every glibc update
Friday, 23 August 2013, 11:39 GMT
Reason for closing: Not a bug
Additional comments about closing: This happens every glibc update
No ... it didn't occur to me that a restart is needed.. my bad.
closure requested ..