I am testing out a Raspberry Pi with the aim to use it in a production system for logging manufacturing data. All is working well and I have been recording test data over the last month.
For redundancy and risk management I have a bunch of Python scripts that need to be scheduled.
In the past I have been working on Windows Server environments and the Task Scheduler did everything I needed. Logging issues, retrying tasks on failure, notifications and much more.
I have been playing with cron over the last few weeks and I have wasted too much time. The log files are not helpful and since I don't have an MTA installed the real errors get lost.
Any alternative that could make scheduling easier rather than harder?
Added detail on the issue:
- I have tried the ">>" in the past with little luck. If that is the normal way to do it I will give it another go.
- The Python scrips runs fine if I run it manually. But as soon as I put it in crontab it stops working and without a log I can't resolve it or at least understand the problem.
- It seems to be an issue with writing files. The cron jobs that are working, are python scripts that connects to bluetooth devices and then logs the data in a MySQL db.
- The Cron log is trying to report output from jobs but cause MTA is not setup it just reports the MTA issue and gives me zero extra info in the actual issue. (/var/log/cron.log this is the main log,right?)
- I will look into MTA, internet connectivity is an issue and might not be available at all times.
- My data logging jobs are in "crontab -e" and I have one job that is creating image files that is sitting in "sudo crontab -e". (two different crontab files I take it)
- All of my cron jobs are similar to these : 00 6 * * * python /app/test.py
cronis normally not written in uppercase. I was a bit confused to figure out if you actually mean the job scheduler...