crond won't start - how to find out what's failing?

[caderoux]

crontab -e shows my crontab is empty.

[root@alarm /]# rc.d start crond
:: Starting crond daemon [FAIL]

This is on a Pogoplug, pacman -Syu shows everything is up to date.

How do I find out what's failing? - I've looked in a few logs but am not seeing anything.

/var/log/

checked out daemon.log, crond.log

[WarheadsSE]

everything.log?

[karog]

You can always try the brute force method of looking at the script /etc/rc.d/crond and debug it like any other script; eg make a copy of it and add echo's to see where it is failing or run the commands therein one by one manually.

[caderoux]

$this->bbcode_second_pass_quote('WarheadsSE', 'e')verything.log?

[WarheadsSE]

$this->bbcode_second_pass_quote('WarheadsSE', 'e')verything.log?

[caderoux]

I found what I did from this article (https://wiki.archlinux.org/index.php/Cron) I added a -M to the parameters in /etc/conf.d/crond; removing that stopped the problem. So now back to the original errors with deleting etc...

[caderoux]

I think most of my problems were due to path issues - i.e. not having the full path on commands (zip needed to be /usr/bin/zip)

I need to read up more about conventions for this.

It seems silly to have scripts have to know about the full paths for cron purposes.

now I still need to figure out what to do about all this mail piling up in /var/mail/root instead of being sent.