Hide Forgot
Description of problem: Example problem: $ tail -n 1 /etc/crontab 0 5 * * * echo date > /tmp/date.txt This file is invalid: in the system crontab, the sixth field is the user field. Here the user "echo" does not exist, so cronie should log an error. Version-Release number of selected component (if applicable): cronie-1.4.8-10.fc16.x86_64 How reproducible: Every time. Steps to Reproduce: 1. 2. 3. Actual results: Silence. No error logged. Expected results: Log an error if something is wrong. Additional info:
System crontables have errors in log: Feb 7 09:06:02 localhost /usr/sbin/crond[1095]: (CRON) bad username (/etc/crontab) If you are using crontab, then you see errors in your crontab immediately.
But I didn't get any error - that's why I reported the bug.
This works: * * * * * root echo date > /tmp/works.txt This doesn't: * * * * * echo date > /tmp/fail.txt
Can you look into the /var/log/messages or other log files? It might be possible that interaction with systemd breaks the logging and puts the message in incorrect logfile.
Aha! You're right! cron no longer logs to messages! It has its own log now "/var/log/cron". Thanks!
Yes, crond is using /var/log/cron for really long time.