Seite 1 von 1

Hang after EPG Update

Verfasst: Do 9. Mai 2019, 23:30
von keith_leitch
Hello,

I have had a problem for some time, and have been gathering logs and posting them on the Australian forum at

https://oztoppy.forumchitchat.com/post/ ... e-10109022

Please tell me if you would like to re-post the logs here.

In short, the problem is that my PVR hangs when 1) A recording ends less than 3 minutes before an EPG update, and 2) the PVR possibly tries to enter sleep state (I am not sure of this), and 3) the channel-scan and EPG update run. After a hang, the SE logs show "A backup has been created" as its final entry. Live TV continues to play, but no operations are possible from the remote or front panel. I must force a sleep state using the front-panel power button, following which the familiar "Checking HDD" process repairs the file system.

I have logs of three cases where this happens.

Re: Hang after EPG Update

Verfasst: Fr 10. Mai 2019, 17:43
von Twilight
do you have an hddinfo log? maybe there is a problem with the harddisk...or maybe it is a problem with the filesystem. you can try to check the filessytem with jfs_fsck from firebird.

twilight

Re: Hang after EPG Update

Verfasst: Sa 11. Mai 2019, 21:20
von keith_leitch
I will do some of those checks. I didn't know about jfs_fsck. However, I doubt this is the problem, because the cause is very consistent. Every time a recording ends about 2 minutes before an EPG update, the system hangs after the update. Every time there is more time between the events, the system does not hang. DMC mentioned on our forum that this may have happened to him, too.

Re: Hang after EPG Update

Verfasst: Sa 11. Mai 2019, 21:23
von keith_leitch
One thing that could help with a workaround is to set the daily time for the EPG update to an unlikely recording time. In the menu, I can set it to half-hour intervals (5:00, 5:30, etc.) Is there some way using an .ini file to set it to 5:07, for example?

Re: Hang after EPG Update

Verfasst: Sa 11. Mai 2019, 22:16
von Twilight
no, you can just set a time which could be the earliest scan time. the receiver will do this on that time when no other timer is set to this time.

twilight

Re: Hang after EPG Update

Verfasst: So 12. Mai 2019, 20:59
von keith_leitch
Thanks for your reply. Yes, I understand. I thought there might be finer control of it to set it to 5:07 or 5:08 instead of 5:00 or 5:30.

When another recording conflicts the EPG scan time changes, but occasionally does not change quite enough to avoid this problem.

Re: Hang after EPG Update

Verfasst: Di 14. Mai 2019, 01:56
von keith_leitch
This morning I had a recurrence of this problem. Here are two log excerpts.

The first excerpt is the end of a previous recording. SE shuts down after this recording finishes. SE then starts up again about three minutes later to commence the EPG update. I am assuming that the PVR enters the sleep state and awakens again between these events. It is possible that it does not enter the sleep state, or makes an incomplete attempt to enter the sleep state.

The second excerpt shows what happens after the EPG update is complete. As you can see, SE does not shut down. This is where my PVR "freezes" and must be rebooted.

This is the fourth case I have logged that follows this pattern. I have reported the other three on the Australian site (follow the link above) with much more complete logs. I have also checked successful cases from many other days, and they always have a much larger gap between a recording and the update. Usually this gap is hours long.

I am starting to see that it is probably the PVR sleeping and reactivating too quickly that causes the problem. If you are planning any more updates to SE, postponing the EPG update for a longer time after a conflict could protect against this. I understand that you may be finished supplying patches, and I respect that. I am just reporting this for your information in case it helps you.

END OF RECORDING AND START OF UPDATE:

2019-05-14 05:00:09 Recording of "Thunderbirds Are Go-2.mpg" stopped
2019-05-14 05:00:09 End of a recording detected
2019-05-14 05:00:17 InfoboxMode: IBDM_Hidden - IBM_TV - IBPM_Rec
2019-05-14 05:01:01 ScanTimer: last successful scan @ 2019-05-13 05:04
2019-05-14 05:01:01 ScanTimer: next start slot @ 2019-05-14 05:00
2019-05-14 05:01:01 ScanTimer: advanced to @ 2019-05-14 05:05
2019-05-14 05:01:01 TimerDB: deleting DB timer '01 'SmartEPG' (2019-05-14 05:05/2') (R=fedc, V=0000)'
2019-05-14 05:01:01 ScanTimer: slot needs to be @ 20 minutes
2019-05-14 05:01:01 ScanTimer: timer has been set to @ 2019-05-14 05:05
2019-05-14 05:01:01 EventDBCache: '/mnt/hd/ProgramFiles/Settings/SmartEPG_TMS/EPGDB/EDBC_LiveEPG.tmp' has been destroyed
2019-05-14 05:01:01 SE shutdown finished
2019-05-14 05:04:46 ===================================================
2019-05-14 05:04:46 SmartEPG_TMS V7.3a
2019-05-14 05:04:46 SysID=32026(TRF-2460), Firmware=TF-BCPF 2.16.00 (Jan 29 2016) (0x0216), Rec=.mpg
2019-05-14 05:04:46 TimeZone = 600 min
2019-05-14 05:04:46 System type: TMS DVBt (208)
2019-05-14 05:04:46 RemoteType: 2100
2019-05-14 05:04:48 EventDBCache: '/mnt/hd/ProgramFiles/Settings/SmartEPG_TMS/EPGDB/EDBC_LiveEPG.tmp' created successfully

END OF UPDATE:


2019-05-14 05:10:36 ScanTimer: next start slot @ 2019-05-15 05:00
2019-05-14 05:10:36 TimerDB: deleting DB timer '21 'SmartEPG' (2019-05-15 05:00/2') (R=fedc, V=0000)'
2019-05-14 05:10:36 ScanTimer: slot needs to be @ 20 minutes
2019-05-14 05:10:36 ScanTimer: timer has been set to @ 2019-05-15 05:00
2019-05-14 05:10:36 FlashTimerDebug: difference found @ 'Exit'
2019-05-14 05:13:17 A backup has been created
2019-05-14 05:33:48 ===================================================

Re: Hang after EPG Update

Verfasst: Mo 27. Mai 2019, 22:48
von keith_leitch
An interesting development. Today the problem recurred with exactly the same circumstances. However, this time I did not force the PVR to sleep. Instead, I accessed my second PVR and used a WebControl API to send a stop command SmartEPG on this PVR.

I think it worked. When I returned, the PVR was in the sleep state, and started up without Checking HDD. The SE log before shutdown looks like this. Note the difference in time between the backup being created and the shutdown process. I think that 6:23 was when I remotely requested the stop.

2019-05-28 05:09:41 ScanTimer: timer has been set to @ 2019-05-29 05:00
2019-05-28 05:09:41 FlashTimerDebug: difference found @ 'Exit'
2019-05-28 05:12:31 A backup has been created
2019-05-28 06:23:50 Searching for SmartBackup
2019-05-28 06:23:50 SB found at '/ProgramFiles/SmartBackup.tap'
2019-05-28 06:23:50 Launching SmartBackup
2019-05-28 06:28:57 SmartBackup has finished
2019-05-28 06:28:57 Today's scan took 83 minutes
2019-05-28 06:29:27 ScanTimer: last successful scan @ 2019-05-28 05:08
2019-05-28 06:29:27 ScanTimer: next start slot @ 2019-05-29 05:00
2019-05-28 06:29:27 TimerDB: deleting DB timer '16 'SmartEPG' (2019-05-29 05:00/2') (R=fedc, V=0000)'
2019-05-28 06:29:27 ScanTimer: slot needs to be @ 90 minutes
2019-05-28 06:29:27 ScanTimer: timer has been set to @ 2019-05-29 05:00
2019-05-28 06:29:28 EventDBCache: '/mnt/hd/ProgramFiles/Settings/SmartEPG_TMS/EPGDB/EDBC_LiveEPG.tmp' has been destroyed
2019-05-28 06:29:28 SE shutdown finished
2019-05-28 06:41:12 ===================================================