I have an entry ./root/scriptname.sh (the script is in /root/scriptname.sh)
First of all I would try a different directory for script storage. I am not sure If the daily cron job can access a root directory. The admin user may have root rights. Therefore you can start the job from the WebUI successfully.
Another reason could be your extension '.sh'. Some scripts are only executed it they have no extension.
For testing purpose you could change the execution intervall to hourly or to a certain point of time.
First of all I would try a different directory for script storage. I am not sure If the daily cron job can access a root directory. The admin user may have root rights. Therefore you can start the job from the WebUI successfully.Another reason could be your extension '.sh'. Some scripts are only executed it they have no extension.
For testing purpose you could change the execution intervall to hourly or to a certain point of time.
Ok I'll try your suggestions. News ASAP.
What are the difference between Daily (with no time chose possibility) and setting every day??
Afaik, the daily jobs are sent from cron to anacron. If a time is set, cron handles the start. If the computer isn't running at that moment, the script won't get executed. Anacreon would take care of that with the next start.
Anacreon would take care of that with the next start.
For some reasons this doesn´t work in OMV(3) (My experience). There was a anacron plugin availabe for OMV2, which was ported to OMV3 by @ryecoaaron and is still available in the testing repo.
I have solved it by putting the script in /etc/cron.daily, /etc/cron.weekly a.s.o. In my experience the scripts then are executed with the next start after a certain delay.
I have never tested the ported Anacron plugin because I have a working solution. Maybe I / someone should do this yet?
There was a anacron plugin availabe for OMV2, which was ported to OMV3 by @ryecoaaron and is still available in the testing repo.
I wrote the plugin and it went away for a while because the scheduled jobs had similar features. I brought it back because they were cron-based not anacron-based.
I have solved it by putting the script in /etc/cron.daily, /etc/cron.weekly a.s.o. In my experience the scripts then are executed with the next start after a certain delay.
If you use scheduled jobs and select daily or weekly, it should do the same thing.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
