Hello,
in webgui in Scheduled jobs I have one job, see attach. My crontab seems like this, see attach. I should run on sundays. It doesnt seems to me... Server is often at this time off, so anacron should do this. Anyway seems to me it is not running even if the server is on. I can not find this job in folder cron.weekly, see attach. In log /var/log/cron-apt/log there is nothing. Running the script manually is ok, even in the webgui. Please help. Thank you.
All jobs go into /etc/cron.d/openmediavault-userdefined
Time or frequency is set there, the actual command is defined in another file at /var/lib/openmediavault/cron.d
@weekly should run on Sunday at 0;00. If the server is off on Sunday's at that time, then use anacron or cron.weekly
I corrected my post. No bug, you can put your script in anacrontab or use cron.weekly folder which is run by anacron, which will ensure your script is runned at least one once a week.
Why a bug? You said yourself that the server is off on Sunday.
The webui I s using @weekly which is a short for.
"0 0 * * 0"
The scheduled jobs uses cron not anacron
You have to check the syslog at that time or redirect the output to an email.
The scheduled jobs uses cron not anacron
This is interesting particularily @ryecoaaron wrote in this thread post no. 2 about the anacron plugin rsnapshot + autoshutdown/WOL - flexible daily backups
The anacron plugin was stopped because the anacron functionality is now integrated into scheduled tasks.
So it seems that in the past there was a dedicated anacron plugin, which became redundant.
I did a lot of investigations and tests and I never get it to run that a cron job was executed later by anacron. If the OMV Nas was switched off when a cron job had to be executed, it was never executed later when the NAS was switched on again. So I cannot comprehend ryecoaaron´s statement.
I found this thread Anacron Daily won't Execute and it leads me to the solution I found at the end:
1. Copy your script to
- /etc/cron.hourly for hourly execution
- /etc/cron.daily for daily execution
- /etc/cron.weekly for weekly execution
- /etc/cron.monthly for monthly execution
2. The script must not have any file extension (.sh ) because otherwise it is not executed by anacron run-parts.
3. Of course the executable bit of the script must be set.
4. It is not necessary to define the job also in OMV Scheduled Jobs. In this case it could be that the job is executed twice.
Nevertheless I did it because it is a good possibility to test the script manually. But afterwards I disabled the entry.
In this way every job is executed by anacron later when the OMV Nas is switched on again. Not immediately but within one hour after switching on.
I told @ryecoaaron that anacron was built in ST, it was a mistake, since it was using just abbreviations for some equivalent cron dates that are documented in crontab man. It looked similar, they should work the same if nas is on all the time. Anacron is better for the on/off server people.
I guess I can port the anacron plugin to omv 3.x.
I told @ryecoaaron that anacron was built in ST, it was a mistake, since it was using just abbreviations for some equivalent cron dates that are documented in crontab man. It looked similar, they should work the same if nas is on all the time.
I am not sure if I have understood that sentence properly, but it sounds to me that there is currently (OMV 3.0.84) no anacron support in scheduled task.
Please do not misunderstand, I don´t want to blame anybody! It´s only for my clarification, because there a some threads in this forum, which deals with anacron functionality, but didn´t help me to get it going.
Thus is it right that there are two possible solutions currently?
a) Adding a script in /etc/cron.xxx - folder like described above in post no. 10
b) Wait until @ryecoaaron has ported the old anacron plugin.
Read further back. There is no anacron in scheduled tasks. If you're not sure just look at the mkconf script that creates the jobs.
Wait until @ryecoaaron has ported the old anacron plugin.
I ported the plugin and it is in the testing repo. Seems to be working for me.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
