Autotimer does not stop recording

[tappari]

This happened in two boxes at the same time. Vu+ Duo4K SE and Ultimo4K. When checking timers/info there was no stop of recording.
I had to fix recording with reconstructapsc plugin.
Enigma2_debug_2022-03-01_17-42-15.log

[ccs]

Which recordings were they?

[tappari]

Which recordings were they?

Historia: Muhammad Ali

[adm]

Go to the completed timer and highlight it (it should say "done")

Press the info button on your remote and you should get a log of the timer and what happened.

[tappari]

Go to the completed timer and highlight it (it should say "done")

Press the info button on your remote and you should get a log of the timer and what happened.

I don`t have it anymore, but when I pressed epg-button there was not stop recording notice.

[ccs]

If you've got a settings backup from a few days ago, you could extract the file /etc/enigma2/timers.xml and see what it might have looked liked before the recording started.

[tappari]

If you've got a settings backup from a few days ago, you could extract the file /etc/enigma2/timers.xml and see what it might have looked liked before the recording started.

Look at the last lines in logfile:
48426.1680> [RecordTimer] activating state 3 (Ended)
< 48426.1682> [RecordTimer] stop recording on tuner: B
< 48426.1682> [eDVBServiceRecord] stop recording!
< 48428.2716> [gRC] main thread is non-idle! display spinner!
What does this line mean: < 48428.2716> [gRC] main thread is non-idle! display spinner!
There clock stopped.

[tappari]

This is how autotimer recording should look when pressing EPG-button in timers:Autotimer.jpg
But in the failed recording two last lines was missing.

[ccs]

As the last entry in the debug log is the spinner, it suggests the box had hung. Timer recordings will almost certainly continue despite the spinner.

Did both boxes need restarting?

Might be worth setting local time in the debug log settings in case it happens again.

[tappari]

As the last entry in the debug log is the spinner, it suggests the box had hung. Timer recordings will almost certainly continue despite the spinner.

Did both boxes need restarting?

Might be worth setting local time in the debug log settings in case it happens again.

Of cource I made boot to both boxes as soon as I noticed both cloks stopped. Then those started rest of the timers ok. Next morning I had to start both again because boxes had blind display.

[ccs]

Of cource I made boot to both boxes as soon as I noticed both cloks stopped. Then those started rest of timers ok. Next morning I had to start both because boxes had blind display.

That'll be why the autotimers overran, the boxes hung (at the same time, which is a bit of a coincidence).

[tappari]

As the last entry in the debug log is the spinner, it suggests the box had hung. Timer recordings will almost certainly continue despite the spinner.

Did both boxes need restarting?

Might be worth setting local time in the debug log settings in case it happens again.

This I have done. Now it`s local time.

[tappari]

That'll be why the autotimers overran, the boxes hung (at the same time, which is a bit of a coincidence).

Coincidence with two boxes at the same time? Are you kidding?

[ccs]

Coincidence with two boxes at the same time? Are you kidding?

Not kidding, but post #1 had no mention of them hanging.

So what do both boxes do at exactly the same time when the spinner was activated?

Or what might have accessed these 2 boxes externally?

[tappari]

Not kidding, but post #1 had no mention of them hanging.

So what do both boxes do at exactly the same time when the spinner was activated?

Or what might have accessed these 2 boxes externally?

Enigma2_debug_2022-03-01_08-17-19.log