cron_logging
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| cron_logging [2016/08/29 11:59] – created walkeradmin | cron_logging [2023/03/09 22:35] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Cron Logging ====== | ====== Cron Logging ====== | ||
| + | <color darkorange> | ||
| + | \\ | ||
| \\ | \\ | ||
| \\ | \\ | ||
| If Cron is seemingly not working, then we need to check the logs at <color red>/ | If Cron is seemingly not working, then we need to check the logs at <color red>/ | ||
| + | \\ | ||
| \\ | \\ | ||
| \\ | \\ | ||
| Line 9: | Line 12: | ||
| sudo nano / | sudo nano / | ||
| \\ | \\ | ||
| + | Look for the line: | ||
| + | \\ | ||
| + | #cron.* and remove the # | ||
| + | \\ | ||
| + | Now restart rsyslog: | ||
| + | \\ | ||
| + | sudo / | ||
| + | \\ | ||
| + | \\ | ||
| + | After the next time your Cron job was due to run, you can check the log <color red>/ | ||
| + | \\ | ||
| + | \\ | ||
| + | |||
cron_logging.1472468369.txt.gz · Last modified: 2023/03/09 22:35 (external edit)