Queue process seems to keep starting and aborting!!

[Matthew]

I have some peculiar behaviour today in my T2, viewing the auto.log I see:

386    04/01/2019 15:13:02 - Aborting, not yet time to run.
385    04/01/2019 15:12:02 - Auto de-queue processed 0 items in 0.162 seconds.
384    04/01/2019 15:12:02 -   elapsed (minutes): 37 (<60)
383    04/01/2019 15:12:02 - Aborting, not yet time to run.
382    04/01/2019 15:12:02 - Registered detectads with priority 200
381    04/01/2019 15:12:02 - Registered shrink with priority 400
380    04/01/2019 15:12:02 - Registered mpg with priority 300
379    04/01/2019 15:12:02 - Registered mp3 with priority 300
378    04/01/2019 15:12:01 - Registered decrypt with priority 900
377    04/01/2019 15:12:01 - Auto de-queue starting

Which has been repeating continuously since the last boot?

Then once a recording has started?

442    04/01/2019 15:28:02 - Aborted, recording in progress.
441    04/01/2019 15:27:02 - Aborted, recording in progress.
440    04/01/2019 15:27:02 - Aborted, recording in progress.
439    04/01/2019 15:26:02 - Aborted, recording in progress.
438    04/01/2019 15:26:02 - Aborted, recording in progress.
437    04/01/2019 15:25:02 - Aborted, recording in progress.
436    04/01/2019 15:25:02 - Aborted, recording in progress.
435    04/01/2019 15:24:02 - Aborted, recording in progress.
434    04/01/2019 15:24:02 - Aborted, recording in progress.

I`ve never seen this before? The box has 'frozen' twice in the last day though (no crashes etc for many months)

Anyone any idea whats going on?

 

[MymsMan]

Anyone any idea whats going on?

Business as usual!

The two halves of the auto process, Scan and Deq, run every minute but quit if it is not time for the next Scan run, Deq finds nothing on the queue or if you have asked for Auto process not to be run during recordings or at certain times of the day.

It might help if the log messages indicated which program was issuing the message - I was a little confused at first why you had 2 Aborted, recording in progress. every minute. You can reduce the log level to reduce the volume of logging

 

[Matthew]

Thanks for your excellent reply, detailed and clear.

I`ve checked the cron and yes both Scan and Deq are run every minute, and I assume as both are run independently together create the 2 aborts per minute, do they really need to run that often?

 

[MymsMan]

You are free to play with the crontab settings but they do very little when run with nothing to do, if they were less frequent you would have a longer gap between adding something to the queue and it being processed. It alleviates the need for updating the crontab when changing the auto settings.