PDA

View Full Version : [TIVIAR-ALPHA+] record timers set via openwebif result in error



reverend
02-01-23, 10:26
Hi there,

A problem has developed whereby record timers that i set to record an IPTV channel using the openwebif web interface result in a zero bytes file being created, the box hanging and an error in the logs. In this example, the timer started when the box was in standby. It had been set about an hour in advance. When this happens, the box stays online (i can get to the logs via a PC on same network) but the GUI becomes inaccessible and I can't get the box out of standby. Timers to record IP channels set via the box directly are unaffected and they work fine. Timers set to record DVB-S channels are unaffected regardless of the interface used to set them

I know this is probably not an issue with the Vix image, but I thought someone might be able to give me a clue after seeing the error logs:



08:59:34.3348 [Navigation] recording service: 4097:0:1:C:226F:697C:0:0:0:0::Channel One
08:59:34.3350 [eNavigation] record: -1
08:59:34.3352 [Navigation] record returned non-zero
08:59:34.3356 [RecordTimer] 'record service' failed
08:59:34.3360 [RecordTimer] prepare failed
08:59:34.3403 [RecordTimer] activating state 1 (Prepared)
08:59:34.3452 [RecordTimer] Found enough free space to record
08:59:34.3473 [RecordTimer] Filename calculated as: '/media/hdd/movie/20230102 0857 - Channel One - Ski Jumping'


In this case, the box keeps going through the above process continually until i depower the box.

I have flashed to the latest image without settings restored, but the issue persists.

Any advice gratefully received.

Thank you

twol
02-01-23, 10:31
Hi there,

A problem has developed whereby record timers that i set to record an IPTV channel using the openwebif web interface result in a zero bytes file being created, the box hanging and an error in the logs. In this example, the timer started when the box was in standby. It had been set about an hour in advance. When this happens, the box stays online (i can get to the logs via a PC on same network) but the GUI becomes inaccessible and I can't get the box out of standby. Timers to record IP channels set via the box directly are unaffected and they work fine. Timers set to record DVB-S channels are unaffected regardless of the interface used to set them

I know this is probably not an issue with the Vix image, but I thought someone might be able to give me a clue after seeing the error logs:



08:59:34.3348 [Navigation] recording service: 4097:0:1:C:226F:697C:0:0:0:0::Channel One
08:59:34.3350 [eNavigation] record: -1
08:59:34.3352 [Navigation] record returned non-zero
08:59:34.3356 [RecordTimer] 'record service' failed
08:59:34.3360 [RecordTimer] prepare failed
08:59:34.3403 [RecordTimer] activating state 1 (Prepared)
08:59:34.3452 [RecordTimer] Found enough free space to record
08:59:34.3473 [RecordTimer] Filename calculated as: '/media/hdd/movie/20230102 0857 - Channel One - Ski Jumping'


In this case, the box keeps going through the above process continually until i depower the box.

I have flashed to the latest image without settings restored, but the issue persists.

Any advice gratefully received.

Thank you

Try recording as servicetype 1 rather than 4097 …. Menu/setup/recordings (I think, not at home at the moment)

reverend
02-01-23, 12:10
Try recording as servicetype 1 rather than 4097 …. Menu/setup/recordings (I think, not at home at the moment)

Good shout thanks. Testing......

reverend
02-01-23, 16:20
its funny, that led to different errors. a file is created of 0kb:



14:46:47.4280 [eHttpStream] openUrl: http result code: 3
14:46:47.4280 [eHttpStream] openUrl: http response code: 302
14:46:47.4387 [eHttpStream] openUrl: redirecting to: http://.....[authorisation URL with a long token]
14:46:47.5109 [eFilePushThread] wait for driver eof timeout

....

14:46:49.0769 [eFilePushThread] wait for driver eof timeout
14:46:49.3275 [eFilePushThread] wait for driver eof timeout
14:46:49.5889 [eFilePushThread] wait for driver eof timeout
14:46:49.6735 [eHttpStream] openUrl: http result code: 3
14:46:49.6735 [eHttpStream] openUrl: http response code: 200
14:46:49.6768 [eHttpStream] Thread end - have connection
14:46:49.8499 [eFilePushThread] wait for driver eof timeout
14:46:50.1109 [eFilePushThread] wait for driver eof timeout
14:46:50.1396 [MessageBox] Timeout!


However, when i set it back to not change to type 1 in the STB menu, i tried to set another record timer, and this time it worked. Recorded a playable file. Not sure what changed. I see this error in the logs repeatedly now, even though things appear to be working:


[eFilePushThread] wait for driver eof timeou