Speaking of SuSe ...... cron prob

[DaveQB]

I run SuSe 10.0 at work and for some reason now cron just fails to execute anything.

Its definatly running:

Code: Select all

node3:~ # ps ax | grep cron
22783 ?        Ss     0:00 /usr/sbin/cron

and

Code: Select all

node3:~ # /etc/init.d/cron status
Checking for Cron:                                                    running

This is what turns up in the system messages log when a task is meant to start at that time:

Code: Select all

May 18 01:07:01 node3 /usr/sbin/cron[22783]: (*system*) RELOAD (/etc/crontab)
May 18 01:08:01 node3 /usr/sbin/cron[22783]: (*system*) RELOAD (/etc/crontab)

And the job isn't run.

I did remove the RPM and then re-installed, but that seems to of only been a short term answer.

Any clues ??

[dann]

Have you tried running crond with the debug option set to something a bit more informative? Maybe you want to run it with debug level 0 to start so it runs in the foreground and you can see what happens when a cronjob is executed.

crond -d

should do it. Of course, stop crond first.

[DaveQB]

Code: Select all

node3:~ # cron
cron     crontab

Don't seem to have a crond executable.

Code: Select all

node3:~ # locate crond
/etc/pam.d/crond

Best i could find.

Code: Select all

node3:~ # cron -d
cron: invalid option -- d
usage:  cron [-n] [-x [ext,sch,proc,pars,load,misc,test,bit]]

Code: Select all

node3:~ # /etc/init.d/cron -d start
Usage: /etc/init.d/cron {start|stop|status|try-restart|restart|force-reload|reload|probe}

And this didn't change the 'verbosness' in the sys logs.

Code: Select all

node3:~ # /etc/init.d/cron start -d
Starting CRON daemon                                                  done

I think I better do some googling.

[jsusanka]

if it isn't root's crontab make sure the user has permission to run cron jobs

[DaveQB]

Testing with system and root's crontab

[dann]

crond should be located in /usr/sbin, chances are /usr/sbin is not in your path.

[DaveQB]

Code: Select all

node3:/var/webmin # echo $PATH
/home/david/bin:/usr/local/bin:/usr/bin:/sbin:/usr/X11R6/bin:/usr/sbin:/bin:/usr/games:/opt/gnome/bin:/opt/kde3/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin:/usr/lib/qt3/bin

[DaveQB]

So tempted to wipe this system and go with Kubuntu or the newest Mandriva.

Now webmin wont run, logs show this:

Code: Select all

bad reqline gN@98532/
[18/May/2006:08:50:50 +1000] [127.0.0.1] Bad Request

Tried with several different browsers.

This is typical of my previous experience of SuSe.
Its looks nice, has loads of potential and I love what they are trying to do, but it has all these small, but annouying bugs that push you over the edge (to another distro)

Last time I ran it on my desktop [10.0], I was excitted but then found I couldnt launch any 3D game, even with 3D accel working. It seemed an openAL problem.
Here's the bug I reported for this for intetests sake
https://bugzilla.novell.com/show_bug.cgi?id=141966

Anyway, I will finish my rant now

[DaveQB]

Ok not that I have got the ranting off ym chest I have fixed the problem(s)

Thanks to Alowishus from #webmin for pushing me in the right direction.

I didnt account for the extra field in the /etc/crontab file for the user the job is to run as. Thus an ill formed /etc/crontab must of been creating the RELOAD in the logs when a job was scheduled.

The webmin problem is because, by default, webmin DOESN'T run on https. I thought it did as all distro's I have used it on did that, but using the package from webmin.com it defaults to http.



So SuSe aint too bad for me right now

[Gomer_X]

I just do crontab -e as the user that owns the job. I've never messed with /etc/crontab.

[DaveQB]

It needed to be root as there was some mounting involved.

But your right.

thanx