Arch Linux

cutuchiqueno

Member

Registered: 2013-07-06

Posts: 70

[SOLVED] crond raises segfault after system Reload configuration

Since yesterday cronie causes the following error messages:

-- Logs begin at Di 2014-07-15 10:38:36 CEST, end at Di 2015-02-10 16:25:01 CET. --
Feb 09 15:51:01 sputnik3arch crond[19981]: pam_unix(crond:session): session opened for user cutuchiqueno by (uid=0)
Feb 09 15:51:01 sputnik3arch CROND[19982]: (cutuchiqueno) CMD (/bin/vdirsyncer2 sync)
Feb 09 15:51:39 sputnik3arch crond[288]: sendmail: Account default nicht in /home/cutuchiqueno/.msmtprc gefunden
Feb 09 15:51:39 sputnik3arch CROND[19981]: (cutuchiqueno) MAIL (mailed 3558 bytes of output but got status 0x004e
                                           )
Feb 09 15:51:39 sputnik3arch CROND[19981]: pam_unix(crond:session): session closed for user cutuchiqueno
Feb 09 15:52:09 sputnik3arch logger[20594]: ACPI group/action undefined: processor / LNXCPU:00
Feb 09 15:52:20 sputnik3arch dbus[278]: [system] Reloaded configuration
Feb 09 15:52:20 sputnik3arch dbus[278]: [system] Reloaded configuration
Feb 09 15:52:20 sputnik3arch dbus[278]: [system] Reloaded configuration
Feb 09 15:52:20 sputnik3arch sudo[18884]: pam_unix(sudo:session): session closed for user root
Feb 09 15:57:01 sputnik3arch crond[23439]: 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
Feb 09 15:57:01 sputnik3arch crond[23439]: PAM adding faulty module: /usr/lib/security/pam_unix.so
Feb 09 15:57:01 sputnik3arch kernel: crond[23439]: segfault at 59d6 ip 00000000000059d6 sp 00007fff0abfa968 error 14 in crond[400000+d000]
Feb 09 15:57:01 sputnik3arch systemd-coredump[23440]: Process 23439 (crond) of user 0 dumped core.
Feb 09 15:58:15 sputnik3arch sudo[23517]: cutuchiqueno : TTY=pts/6 ; PWD=/etc ; USER=root ; COMMAND=/usr/bin/vimdiff locale.gen locale.gen.pacnew
Feb 09 15:58:15 sputnik3arch sudo[23517]: pam_unix(sudo:session): session opened for user root by (uid=0)
Feb 09 15:59:51 sputnik3arch sudo[23517]: pam_unix(sudo:session): session closed for user root

I posted exactly the fragment of the journal that shows the moment where cronie stoped to work normal. At the moment every cron job is causing the problem not a particular one and before everything was fine. The only thing that gives a hint that something might have changed is the *Reloaded configuration* message. I looked at the pacman log and recognized that I did an update of the following packages:

[2015-02-09 15:52] [ALPM] upgraded mpd (0.19.8-1 -> 0.19.9-1)
[2015-02-09 15:52] [ALPM] upgraded net-snmp (5.7.2.1-3 -> 5.7.3-1)
[2015-02-09 15:52] [ALPM] upgraded nodejs (0.10.36-2 -> 0.10.36-3)
[2015-02-09 15:52] [ALPM] upgraded patch (2.7.3-1 -> 2.7.4-1)
[2015-02-09 15:52] [ALPM] upgraded python-lxml (3.4.1-1 -> 3.4.2-1)
[2015-02-09 15:52] [ALPM] upgraded python2-ecdsa (0.11-2 -> 0.13-1)
[2015-02-09 15:52] [ALPM] upgraded python2-keyring (4.1.1-1 -> 5.0-1)
[2015-02-09 15:52] [ALPM] upgraded udisks2 (2.1.3-1 -> 2.1.4-1)
[2015-02-09 15:52] [ALPM] upgraded youtube-dl (2015.02.03-1 -> 2015.02.06-1)

But I can not sea how these should be related.

Basically I don't even understand what's the problem here to continue to search for solutions.

Last edited by cutuchiqueno (2015-02-11 09:43:03)

dreamersbrow

Member

From: Iowa

Registered: 2011-03-27

Posts: 24

Re: [SOLVED] crond raises segfault after system Reload configuration

I was experiencing this problem as well.  I reinstalled pam with:

#pacman -S pam

and then stopped and started the cronie service and it seems to be running okay again.

frank604

Member

From: BC, Canada

Registered: 2011-04-20

Posts: 1,212

Re: [SOLVED] crond raises segfault after system Reload configuration

If cron is segfault, try to restart cronie.service

dreamersbrow

Member

From: Iowa

Registered: 2011-03-27

Posts: 24

Re: [SOLVED] crond raises segfault after system Reload configuration

Yes.  I'm not sure if reinstalling pam was required. I forgot to try restarting the service until after I has reinstalled pam.

Last edited by dreamersbrow (2015-02-10 19:05:21)

Spider.007

Member

Registered: 2004-06-20

Posts: 1,175

Re: [SOLVED] crond raises segfault after system Reload configuration

Pretty sure this is caused by the recent glibc update; it broke a lot of services for me including cronie.

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,424

Website

Re: [SOLVED] crond raises segfault after system Reload configuration

You have to restart cronie after every glibc update, AFAIAA...

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Spider.007

Member

Registered: 2004-06-20

Posts: 1,175

Re: [SOLVED] crond raises segfault after system Reload configuration

You have to restart cronie after every glibc update, AFAIAA...

For me this means restarting a lot of machines when updating; glibc is the only package where updates are so invasive.
Is there some reading material availble somewhere on why this is and if it could possibly be avoided?

cutuchiqueno

Member

Registered: 2013-07-06

Posts: 70

Re: [SOLVED] crond raises segfault after system Reload configuration

I had to reboot again. In fact this simple solution didn't come to my mind because I thought I had already turned off the computer at least once. Came out, I hadn't for days.

Still, I learned something regarding glibc, thank you!