crontab not working


17 posts in this topic Last Reply

Recommended Posts

Apr 25 21:47:01 unRAID crond[1304]: exit status 1 from user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null
Apr 25 21:47:01 unRAID crond[1304]: exit status 1 from user root /mnt/cache/.mrtg/crontab
Apr 25 21:47:01 unRAID kernel: crond[25940]: segfault at b77b051c ip b77b051c sp bfc04c94 error 15 in ld-2.11.1.so[b77b0000+1000]
Apr 25 21:47:01 unRAID kernel: crond[25941]: segfault at b77b051c ip b77b051c sp bfc04c94 error 15 in ld-2.11.1.so[b77b0000+1000]
Apr 25 21:48:01 unRAID crond[1304]: exit status 1 from user root /mnt/cache/.mrtg/crontab
Apr 25 21:48:01 unRAID kernel: crond[26240]: segfault at b77b051c ip b77b051c sp bfc04c94 error 15 in ld-2.11.1.so[b77b0000+1000]

 

 

 

this script Apr 25 21:48:01 unRAID crond[1304]: exit status 1 from user root /mnt/cache/.mrtg/crontab

 

seems not working

 

if i run manual, it updates.. but no work on crontab

Link to post

# 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
# Scheduled Parity Check
#cron=""
#Add sa1 data collection - 1 data point per 2 min
#*/2 * * * * /usr/lib/sa/sa1 1 1
#*/5 * * * * env LANG=C /usr/bin/mrtg --lock-file /tmp/mrtg_lockfile /boot/config/mrtg.cfg
*/1 * * * * /mnt/cache/.mrtg/crontab

 

Link to post
#Add sa1 data collection - 1 data point per 2 min

#*/2 * * * * /usr/lib/sa/sa1 1 1

 

Those look like they have been added by the SimpleFeatures Stats add-on. Upgrade to the latest versions if you haven't already. MRTG isn't included in any of the SimpleFeature plugins. Something else has disabled the SimpleFeatures Stats cron entry though, it should look like:

 

#Add sa1 data collection - 1 data point per 2 min

*/2 * * * * /usr/lib/sa/sa1 1 1

Link to post
  • 2 weeks later...
  • 1 month later...

I'm actually seeing this same issue... and I don't know why.

 

Jun 18 21:47:01 knox crond[1256]: exit status 1 from user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null 
Jun 18 21:47:01 knox kernel: crond[10650]: segfault at b774051c ip b774051c sp bfebf734 error 15 in ld-2.11.1.so[b7740000+1000]
Jun 18 22:47:01 knox crond[1256]: exit status 1 from user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null 
Jun 18 22:47:01 knox kernel: crond[27510]: segfault at b774051c ip b774051c sp bfebf734 error 15 in ld-2.11.1.so[b7740000+1000]

 

I disabled the stats add-on and there is nothing out of the ordinary in my crontab, and my /etc/cron.hourly is empty... Anyone know why this would be happening? I would just ignore it, but I am trying to add a rsync script for my other server that runs every hour, and it won't run when I add it to /etc/cron.hourly because it segfaults before it does anything.

 

root@knox:/# crontab -l
# 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
# Scheduled Parity Check
30 5 12 * * /root/mdcmd check  1>/dev/null 2>&1
root@knox:/# ls -la /etc/cron.hourly/
total 0
drwxr-xr-x  2 root root 0 2010-02-12 22:17 ./
drwxr-xr-x 25 root root 0 2012-06-18 16:34 ../
root@knox:/# 

 

Cheers,

whiteatom

 

Link to post

It is saying you are getting exit status of 1 from

/usr/bin/run-parts /etc/cron.hourly

 

what happens when you run that command from the command prompt?

 

You might even try it in a debugging mode to see if that points you to the issue:

sh -xv /usr/bin/run-parts /etc/cron.hourly

 

Did you by chance install an incompatible shared library with one of your add-ons?

 

Joe L.

Link to post

It runs fine.. That's the problem. I'm just looking in to problems with the transmission plugin that may be the cause. I'm going to tear out all the packages that have been added on and try them one at a time to see if I can track it down.

Link to post

Soo.. I deleted everything in the packages folder and removed all plugins except the basics that I need.. PMS, SAB, SB, CP - and rebooted. Each plugin installed the packages it needed (far fewer then before) but... the problem persists. I know the next step is to remove those as well, but those are why I have this box, so if that doesn't work then I'm no better off - and I certainly won't need my cron script that isn't running which is why I'm fixing this in the first place.

 

I took all of the simpleFeatures add-ons out before, but I am now trying to remove SF altogether. I'll report on what the outcome is at 10:47 :)

 

whiteatom

Link to post
  • 1 year later...

I believe that old versions of simplefeatures, and transmission would cause this error.  I am running the latest version of simplefeatures and don't get it.  I fixed a transmission plugin a long time ago to stop causing it, but there are newer plugins out there.  I no longer run transmission on unRAID so I don't know if they cause the error, but I suspect they don't.

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.