crond segfault errors

[natiz]

Hey all,

 

For some reason, cron is not working properly, I'm pretty sure from day one (new to unraid)

 

Sep 26 01:47:01 Tower kernel: crond[27615]: segfault at 4001e51c ip 4001e51c sp bf93ab18 error 15 in ld-2.11.1.so[4001e000+1000]
Sep 26 01:47:01 Tower crond[1129]: exit status 1 from user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null

 

I've search the forum for similar issues and could only found one's related to Transmission plugin, which I don't use.

 

The thing is, when I restart crond and start it again, it works (killall crond ; crond -l6)..

 

Here is the content:

# If you don't want the output of a cron job mailed to you, you have to direct
# any output to /dev/null.  We'll do this here since these jobs should run
# properly on a newly installed system, but if they don't the average newbie
# might get quite perplexed about getting strange mail every 5 minutes. :^)
#
# Run the hourly, daily, weekly, and monthly cron jobs.
# Jobs that need different timing may be entered into the crontab as before,
# but most really don't need greater granularity than this.  If the exact
# times of the hourly, daily, weekly, and monthly cron jobs do not suit your
# needs, feel free to adjust them.
#
# Run hourly cron jobs at 47 minutes after the hour:
47 * * * * /usr/bin/run-parts /etc/cron.hourly 1> /dev/null
#
# Run daily cron jobs at 4:40 every day:
40 4 * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null
#
# Run weekly cron jobs at 4:30 on the first day of the week:
30 4 * * 0 /usr/bin/run-parts /etc/cron.weekly 1> /dev/null
#
# Run monthly cron jobs at 4:20 on the first day of the month:
20 4 1 * * /usr/bin/run-parts /etc/cron.monthly 1> /dev/null

 

What could cause this?

[dgaschk]

Attach a syslog.

[natiz]

Sorry about that, syslog attached.

 

syslog-20130925-214832.zip

[dgaschk]

This is caused by an incompatible or misconfigured add-on. What does "ls /etc/cron.daily" show?

[natiz]

It reads:

root@NAS:~# ls -all /etc/cron.daily
total 4
drwxr-xr-x  2 root root   0 2010-02-13 03:48 ./
drwxr-xr-x 30 root root   0 2013-09-26 19:52 ../
-rwxr-xr-x  1 root root 123 2010-02-13 03:48 logrotate*

 

 

[natiz]

I did some googling and found that 'ld-2.11.1.so' is part of glibc.

I am loading an updated version for glibc at /boot/extra/glibc-2.17-i486-7.txz

 

I'm guessing that since it works after I restart crond, than it might have anything to do with it; I'll test it tomorrow and update.

[dgaschk]

Sorry, i meant cron.hourly.

 

ls /etc/cron.hourly

 

from here:

Sep 26 01:47:01 Tower kernel: crond[27615]: segfault at 4001e51c ip 4001e51c sp bf93ab18 error 15 in ld-2.11.1.so[4001e000+1000]
Sep 26 01:47:01 Tower crond[1129]: exit status 1 from user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null

[natiz]

Actually, cron.hourly is empty:

 

root@NAS:~# ls -all /etc/cron.hourly
total 0
drwxr-xr-x  2 root root 0 2010-02-13 03:47 ./
drwxr-xr-x 30 root root 0 2013-09-26 22:47 ../

 

Every cron job fails, no matter what's in there.

 

I have got several of packages being installed on /boot/extra, which I believe might cause this issue. When I wipe that folder clean, the issue is not occurring.

The packages:

root@NAS:~# ls -l /boot/extra
total 33952
-rwxrwxrwx 1 root root  4188324 2013-09-26 00:45 binutils-2.23.52.0.1-i486-2.txz*
-rwxrwxrwx 1 root root   852852 2013-06-24 02:06 curl-7.31.0-i486-1.txz*
-rwxrwxrwx 1 root root   386408 2013-09-26 00:42 cxxlibs-6.0.18-i486-1.txz*
-rwxrwxrwx 1 root root   204336 2013-09-26 00:44 file-5.14-i486-1.txz*
-rwxrwxrwx 1 root root 13342928 2013-09-26 00:42 gcc-4.8.1-i486-1.txz*
-rwxrwxrwx 1 root root 12239884 2013-09-26 02:11 glibc-2.17-i486-7.txz*
-rwxrwxrwx 1 root root   652280 2013-09-26 00:46 kernel-headers-3.10.12_smp-x86-1.txz*
-rwxrwxrwx 1 root root   693036 2013-08-30 09:14 lftp-4.4.9-i486-1.txz*
-rwxrwxrwx 1 root root   402604 2013-09-26 00:45 make-3.82-i486-4.txz*
-rwxrwxrwx 1 root root   374668 2013-09-24 13:07 nano-2.3.0-i486-1.txz*
-rwxrwxrwx 1 root root  1233460 2013-02-12 05:58 openssl-solibs-1.0.1e-i486-1.txz*

 

All of which were obtained from http://search.slackware.eu/cgi-bin/search.cgi (for slackware-current ver)

 

Since ld-2.11.1.so is part of the glibc library, I'm guessing that's the smoking gun - perhaps that version is not compatible with unraid?

How would I know which version is? for that matter, what version of slackware is the current version of unraid based on?

[Barziya]

Since ld-2.11.1.so is part of the glibc library, I'm guessing that's the smoking gun

Yes.

 

what version of slackware is the current version of unraid based on?

UnRAID's package base is from Slackware version from like five years ago.  But don't worry about that.  Crond crapping out is the only side effect of using the newer glibc.  If you don't really need crond on your server, then you can just kill the thing, and ignore the problem.  Or, if you don't need the compiler packages on a daily basis, you can just install them when you actually have to do some compiling.  Or, you could get the older gcc/make/binutls/glibc/etc., but why bother?

 

 

[natiz]

Hey Pourko, thanks for the insights!

 

I've worked around this by restarting crond upon startup using the go script.

 

killall crond && crond

Simple as that. I guess its not 100% ideal, not sure what the consequences are, but so far so good