Task Scheduler not running script

[Father Of Dragons]

Hi everyone,

New Synology user here, having used a QNAP NAS for many years, when it had a failed motherboard around Christmas time I decided to try Synology - a DS720+

One of the tasks I use the NAS for is storing snapshots from several IP cameras. On the QNAP I added lines to the crontab to auto-delete these files when they were older than e.g. 7 days.

I was pleased to see that Synology provide a Task Scheduler to (hopefully!) save having to SSH in and edit the crontab file, so I have created some simple user-defined scripts in task scheduler, e.g.

find /volume1/FrontCam/ -type f -mtime +7 -delete

When I enable this task and click on "Run" it works perfectly. However, when left to run automatically once a day it does nothing at all. Output.log and Script.log files are created at the run time, which suggests that something is happening, but the output.log file is empty and the files are not deleted.

It makes no difference if I run it as User, admin or root.

A search indicates that this question, or a very similar one, has been asked several times in various forums but, as far as I can tell, has never been answered with a solution that works.

Can anyone shed any light on this and suggest how I can get it to work?

Thanks

 

[Father Of Dragons]

Well I've finally managed to get it working, so if this is of any help to anyone what worked for me was running (in DSM 7)

systemctl restart crond

and

systemctl restart synoscheduler

As far as I know I had done nothing to stop the cron daemon. Could it be that entering user defined scripts in the Task Scheduler doesn't actually start it? Whatever, the above worked for me.

 

[Rusty]

Could it be that entering user defined scripts in the Task Scheduler doesn't actually start it?

It should work just fine, that's the whole point.

 

[Father Of Dragons]

Well I absolutely agree - but as noted in my first post, it didn't. A search will reveal that I'm by no means the only one to have had this problem. Until the problem became evident I had not had any interaction with the Synology OS other than through the control panel, so I struggle to see how I could somehow have stopped either or both processes.

 

[Jan Janowski]

The timed script file uploaded here works.
I’m using 13 different versions of it nightly on a 718+.

 

[Father Of Dragons]

Well I'm only reporting my experience - the scheduled tasks did not run until I ssh'd in and ran those two commands as root. I posted in case that's of help to anyone else with the same problem. I'm very pleased for you if your scripts run OK, but that information doesn't really help anyone whose scripts don't. For example, someone answered the same question on another forum by saying the solution was to set the "last run time" to 23.59 - but if you have the schedule only running once per day there is no option to set a "last run time", so that solution may have worked for him, but was no use to me. The real question is why do some people have this problem at all, whilst others don't appear to?

 

[Rusty]

The real question is why do some people have this problem at all, whilst others don't appear to?

And you do run it over Task as root yes?

 

[Father Of Dragons]

As I said in my first post, I tried running it as me, as admin and as root but there was no difference. Now that it is running it runs as me quite happily.