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
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
Which recordings were they?
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.
Xtrend ET10K, 2 x satellite tuners 28.2 (Sky FTA), 2 x hybrid (UK Freeview), Zgemma H9S (satellite)
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.
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.
Last edited by tappari; 03-03-22 at 07:34.
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.
Last edited by ccs; 03-03-22 at 11:52. Reason: typo