Batch Job Run By Task Scheduler Stays Suspended After Running

Get help for specific problems
AlexD
Posts: 10
Joined: 5 Apr 2019

Post by AlexD • 08 Aug 2019, 08:38

Hi guys,

I use the Donator version of FFS to run a Batch Job on Server 2016, Task Scheduler Runs the Batch ever two hours and it mirrors our Network Shares to a Synology NAS. The actual Mirror works great, however over the last few months, finished batche jobs seem to just sit in Task Manager as suspended, this used to happen maybe once a week before but now happens almost every time the job is run.

Is there something i need to change in task scheduler to stop this happening?

http://prntscr.com/opxkos

http://prntscr.com/opxm1q

http://prntscr.com/opxmhf

http://prntscr.com/opxmr3

In the Task History i can see that it is trying to end each of the Suspended tasks listed in Task Manager before attempting to run the new task.

Thanks

Alex

AlexD
Posts: 10
Joined: 5 Apr 2019

Post by AlexD • 15 Aug 2019, 12:50

Anyone have any insight?

User avatar
Plerry
Posts: 762
Joined: 22 Aug 2012

Post by Plerry • 16 Aug 2019, 10:01

I noticed a couple of things:

Unless I am misinterpreting things, it seems you are stopping/suspending RTS after two hours.
It is unclear what https://prnt.sc/opxmhf relates to, but it may even be that you start RTS every two hours.
RTS is intended to run continuously, and not stopped or suspended every two hours.
At best it may be restarted every two hours, in case it would have stopped for whatever reason.
RTS monitors folders for changes, and upon detecting any changes in the monitored folder(s) will launch the specified task, usually an FFS sync.
I don't know the details here, but perhaps if RTS gets suspended after two hours, all tasks launched by RTS also get suspended. So, if an FFS task is running when RTS gets suspended, the FFS task also gets suspended?

FFS syncs on the other hand are suitable task to be started (and occasionally: stopped) by the Scheduler.
Can it be that the FFS sync (including its preceding Compare phase) has over time grown and can now (structurally or incidentally) take over two hours to run? Then that may explain your suspended FFS jobs piling up.
Making things work as before may then be as simple as increasing the two hour setting into some suitable bigger value.

AlexD
Posts: 10
Joined: 5 Apr 2019

Post by AlexD • 16 Aug 2019, 11:14

Hi Perry,

Currently i am not running RTS, Just a Batch Job for FFS.

Previously the time was set to 1 hour and i experienced similar behavior, if i monitor it in real time i can see that the comparison usually only takes 10 - 20 minutes. This gives it about a minimum 1 hour 40 mins to perform the mirror - which should be ample time.

It seems to be that these residual processes that have been suspended maybe as a result of FFS not closing correctly after the Mirror has been performed.

Thanks

Alex

User avatar
Plerry
Posts: 762
Joined: 22 Aug 2012

Post by Plerry • 17 Aug 2019, 14:05

Another (obvious) question is:
Did you checkmark the Auto-close and Ignore Errors checkboxes when saving the FFS batch job?