Also just to document it. First human interaction with box was around 9 local time.
Had this message on screen:
PXL_20230304_085911785.jpg2 jobs are running in the background!
2 jobs are running in the background!
Really shutdown now?
[Yes]
[No]
I should add. For me this is not a new problem. I have always found the EPG would occasionally corrupt in this way (lots of blank entries).Originally Posted by BrianG61UK
I've been trying to make everything that's involved with reading the OpenTV EPG run at a high priority, but it doesn't seem to make any difference. But I may have missed something.
Weirdly, it looks like the current code actually runs (or is intended to run - it looks wrong to me) the EPG reading stuff at a low priority!?
Last edited by BrianG61UK; 04-03-23 at 14:41.
Zgemma H7S, Fixed 28.2°E dish, Freeview (Hannington). ABM Providers: [Sky UK; Thames Valley SD Custom; HD swap], [Freeview (UK); Berks and North Hants]
I was curious as to why your box didn't return to deep standby after 20 minutes (you said you had a PowerTimer set and I could see it mentioned in the log during startup). But I can see in the log that the box seems to be tuning various channels by itself (not related to EPGRefresh). Is this something to do with Unicable? Something to keep the LNB powered? The fact that two jobs (whatever they are) are running is what is keeping the box from reverting to deep standby. The crash at initial startup is worrying. Maybe you should do a clean flash and restore? Maybe it's a hardware/driver issue - wouldn't be the first with Gigablue. My own GB Quad+ will throw a C++ crash/error every few months for no apparent reason. Has been stable for months now, though - fingers crossed!
I just use a conventional LNB and the only channel that is tuned by the box after a PowerTimer boot is RTE1 (as this is set as the startup channel). If I don't interact with the box while it is in standby, nothing else is ever tuned unless ABM/OpenTVZapper is set to run.
GB Quad Plus, Mut@nt HD51, AX HD61, 80cm dish and Supreme Dark motor. Sony STR-DN 1060, Sony UHP-H1 Bluray, Odroid N2+ (CoreElec), Monitor Audio Bronze 5.1 speakers
satteliter (05-03-23)
Yip, I added 'Satellite equipment setup' plugin to solve an issue.i can't remember 100% what issue i initially changed it for - think it may have been to reduce/remove initial tune failed messages. Although I will add that there had been a power timer putting the box to deep standby after being standby for 60 mins - this behaved with no issues - i will leave sat equipment plugin active and disable after next run if it fails.
Box is a Vu+ Duo 4k SE .
So, for this morning's run, I had the following settings in play.
I had set a power timer to take the box out of deep standby into standby at 7.30 and go back to deep standby at 07:55
I then had ABM set to run at 07.32 and epgrefresh set to run at 07:40.
From there, it had Saorview Information(terrestrial) and IEPG data 1 (satellite) to run,
The other thing I had set was for rte1 to be the default startup channel.
I will change EPGRefresh to not attempt shutdown just in case it's interfering with AutoTimer (power timer already set to take care of shutdown)
Still not sure what was taking the box out of standby into active such that message was on screen (assuming EPGRefresh and ABM can run in standby - thinking this may have been setting rte1 as the startup channel - now disabled) edit: I think EPGRefresh needs to be out of standby judging the wording of the description for setting 'Wakeup up from standby for EPG refresh' - i have left this set to Yes
Logs attached for this morning. Crash again - i had updated to 6.3.003 yesterday I think but will get a full flash in this week.
Enigma2_debug_2023-03-05_07-30-35.logEnigma2_crash_2023-03-05_07-30-49.logEnigma2_debug_2023-03-05_07-30-59.log
All relevant setting screens attached as they were for this morning's run.
sat equipment setting page1.jpgsat equipment setup.jpgabm.jpgepgrefresh settings full.jpgauto power timer settings.jpgautopower timer.jpgsat equipment setting page2.jpg
On a positive note, no huffman encode errors in the last couple of runs!
On the crash side, I will just leave the error message here for web/search indexing as Google returned no results. When I loosened search terms, I got one results with that numeric string having to do with Greek ISO entry or something.
< 36.4421> 07:30:49.0585 [eDVBLocalTimerHandler] remove channel 0x69f738
< 36.4423> 07:30:49.0587 [eEPGTransponderDataReader] remove channel 0x69f738
< 36.4457> 07:30:49.0622 PC: 00000000
< 36.4458> 07:30:49.0622 Fault Address: 00000000
< 36.4458> 07:30:49.0623 Error Code: 2147484167
< 36.4460> 07:30:49.0625 Backtrace:
< 36.4462> 07:30:49.0627 /usr/bin/enigma2(_Z17handleFatalSignaliP9siginfo_tPv) [0x889D4]
< 36.4464> 07:30:49.0629 /lib/libc.so.6(__default_rt_sa_restorer) [0xB5B111D0]
< 36.4464> 07:30:49.0629 -------FATAL SIGNAL (11)
Last edited by satteliter; 05-03-23 at 12:49. Reason: epgrefresh standby/active clarification
I've no idea what's causing the crash at initial startup from deep. One of the devs would need to take a look.
I think you're making things more complex than they need be. You have ABM and EPGRefresh and a PowerTimer set to wake the box. You have ABM and the PowerTimer trying to put the box in deep standby. To be honest, I would just disable EPGRefresh completely and let the built-in OpenTVZapper do the necessary. Both of these utilities tune the box to the Sky IEPG channel and the OpenTV reader downloads the schedule data for the EPG. I would leave the setting having RTE1 as the startup channel. The mere fact that it tunes RTE1 will download the Saorview EPG in seconds, assuming you have Enable EIT EPG set to YES.
What I would suggest is to leave the PowerTimer set to boot to standby at 07.30 daily and go back into deep standby at 07.55. Have ABM set to run at 07.35 on whatever days you wish, but do not set any wake or shutdown options for ABM (you are already controlling the startup/shutdown with the PowerTimer). Have OpenTVZapper enabled in the EPG options. Set a schedule time (rater than the automatic interval) in the zapper settings - you could do this at 07.40 if you wanted to wait until after ABM had run. This means that the PowerTimer is controlling the startup/shutdown and you are scheduling events to happen during the period. If one of the other plugins related to unicable or FCC or whatever is affecting the EPG acquisition, then it is a matter of eliminating the plugins one by one until the culprit is located.
My routine is that the box is scheduled to boot at 17.49 (my box is slow to boot - it's old), then at 17.52 the zapper runs and finishes by 17.55. At 18.01 I have a timer set to record the news from RTE1. If no-one is around, the box will automatically go back into deep standby after the recording is done. I have a separate ABM schedule set to run at 04.30 on Tuesday and Thursday to update any bouquet changes. It uses the ABM scheduler to boot and shutdown the box - no PowerTimer used. Here are my EPG, PowerTimer and zapper settings:
GB Quad Plus, Mut@nt HD51, AX HD61, 80cm dish and Supreme Dark motor. Sony STR-DN 1060, Sony UHP-H1 Bluray, Odroid N2+ (CoreElec), Monitor Audio Bronze 5.1 speakers
Agreed! I updated things after this morning's run to only have the power time dealing with standby on/off.
I've disabled ABM & EPGRefresh from wake/shutdown actions.
OpenTV EPG corruption was causing the issues.
If these issues persist past tomorrow, I will just use OpenTV scheduled for satellite and let terrestrial populate on boot as you've recommended.
Thanks for the screenshots.
Is that on this forum or some enigma forum/github?
Just realised how to narrow down that crash. Started when I started using EPGRefresh. I've been keeping all the logs.
I'm curious to see if it's a coincidence or not.box crash lists.jpg
abu baniaz (05-03-23),Joe_90 (05-03-23)
A couple of the OpenVix devs should be able to identify the offending module. In the meantime, if you've disabled EPGRefresh, let's see if the crashes stop.
GB Quad Plus, Mut@nt HD51, AX HD61, 80cm dish and Supreme Dark motor. Sony STR-DN 1060, Sony UHP-H1 Bluray, Odroid N2+ (CoreElec), Monitor Audio Bronze 5.1 speakers
So todays update is:
- everything worked! no crashes. EPG populated(both terrestrial & sat). EPGRefresh did it's job/ No huffman encode errors! No messages on screen -> Box was in deep standby when i went to check it.
[just to add some unrelated - i switched wifi off and went with wired for network connection.
Log(singular!) attached
Enigma2_debug_2023-03-06_07-30-40.log
wifi info in log is just fake name & pwd i set]
That's a better results - hopefully will remain stable. By the way, there is no need to set the Saorview channel in EPGRefresh - the initial tune to RTE will download the Saorview EPG in seconds. I think you also may have the OpenTV Zapper enabled as I can see entries in the log for it. I suggest that you use either OpenTV zapper or EPGRefresh - not both.
GB Quad Plus, Mut@nt HD51, AX HD61, 80cm dish and Supreme Dark motor. Sony STR-DN 1060, Sony UHP-H1 Bluray, Odroid N2+ (CoreElec), Monitor Audio Bronze 5.1 speakers
update:
yesterday morning(7th) ran fine with no crash.
this morning(8th) - i had ABM set to run(& wake from deep standby) at ~03.30. There was a crash at that time.
There was also a later crash near when EPGRefresh(not set to wake up from deep standby) ran at ~07.40.
03.30 crash:
< 38.4470> 03:29:53.0296 [eDVBLocalTimerHandler] remove channel 0x1027468
< 38.4474> 03:29:53.0299 [eEPGTransponderDataReader] remove channel 0x1027468
< 38.4510> 03:29:53.0335 PC: 00553308
< 38.4510> 03:29:53.0336 Fault Address: 00553308
< 38.4511> 03:29:53.0336 Error Code: 2147484175
< 38.4512> 03:29:53.0338 Backtrace:
< 38.4514> 03:29:53.0340 /usr/bin/enigma2(_Z17handleFatalSignaliP9siginfo_tPv) [0x889D4]
< 38.4516> 03:29:53.0341 /lib/libc.so.6(__default_rt_sa_restorer) [0xB5B511D0]
< 38.4516> 03:29:53.0342 -------FATAL SIGNAL (11)
07.37 crash:
Enigma2_crash_2023-03-08_03-29-53.log< 39.3109> 07:37:53.2914 [eDVBLocalTimerHandler] remove channel 0x1024d50
< 39.3113> 07:37:53.2918 [eEPGTransponderDataReader] remove channel 0x1024d50
< 39.3143> 07:37:53.2948 PC: 17b4aecc
< 39.3144> 07:37:53.2949 Fault Address: 17b4aecc
< 39.3144> 07:37:53.2949 Error Code: 2147484166
< 39.3146> 07:37:53.2951 Backtrace:
< 39.3148> 07:37:53.2953 /usr/bin/enigma2(_Z17handleFatalSignaliP9siginfo_tPv) [0x889D4]
< 39.3150> 07:37:53.2955 /lib/libc.so.6(__default_rt_sa_restorer) [0xB5BA11D0]
< 39.3151> 07:37:53.2955 -------FATAL SIGNAL (11)
Enigma2_debug_2023-03-08_03-29-38.log
Enigma2_debug_2023-03-08_03-30-03.log
Enigma2_debug_2023-03-08_07-37-38.log
Enigma2_crash_2023-03-08_07-37-53.log
Enigma2_debug_2023-03-08_07-38-03.log
What's interesting to note is ABM did not put box back to deep standby. i think this is because i had hdmi-cec settings which took tv out of standby when box came out of standby (which ABM (i think) did)). The TV then must have been sending the wakeup hdmi-cec signal such that the box never went back to standby(judging from log entries)
I've since moved ABM to run after the scheduled auto power timer turns box on(~07.30) and turned off 'wake/return to standby' settings for ABM.
Also disabled HDMI-CEC turn on tv settings for the time being.
I've attached log from the successful run yesterday just for the record:
Enigma2_debug_2023-03-07_07-30-39.log
Will monitor and update.
It was disabled when I installed EPGRefresh. I think those entries will be present regardless of status.
[OpentvZapper] < 1066.1597> 07:55:00.1402 [OpentvZapper] next wake up due -1
....
< 34.5017> 07:37:48.4822 [OpentvZapper-Scheduler][Scheduleautostart] AutoStart Enabled
< 34.5019> 07:37:48.4824 [OpentvZapper-Scheduler][AutoScheduleTimer] Schedule Disabled at Wed 08 Mar 2023 07:37:48 GMT
So just to close this issue off, the days since the last post have been trouble free. No crashes, no huffman errors & most importantly - no empty EPGs.
The following are the settings that were in play. The brief version is ABM and EPGRefresh no longer handled wake up or shutdown. They ran within the power timer scheduled on/off.epgrefreh schedule.jpgabm main setting.jpgabm day schedule.jpg
Here are the logs for the morning run logs for the last few days in case it provides any historical/future troubleshooting use:
9th Enigma2_debug_2023-03-09_07-30-41.log
10th Enigma2_debug_2023-03-10_07-30-37.log
11th Enigma2_debug_2023-03-11_07-30-38.log
12th Enigma2_debug_2023-03-12_07-30-44.log
If any crashes/errors discussed in this thread appear again I'll open new thread.
Thank you all for your assistance!
Do no other people find that flicking from channel to channel (satellite channels) while OpenTV EPG download starts doesn't cause a problem?I should add. For me this is not a new problem. I have always found the EPG would occasionally corrupt in this way (lots of blank entries).
I've been trying to make everything that's involved with reading the OpenTV EPG run at a high priority, but it doesn't seem to make any difference. But I may have missed something.
Weirdly, it looks like the current code actually runs (or is intended to run - it looks wrong to me) the EPG reading stuff at a low priority!?
I'm wondering if it's some weird bug that's specific to Zgemma or to the Zgemma H7.
Zgemma H7S, Fixed 28.2°E dish, Freeview (Hannington). ABM Providers: [Sky UK; Thames Valley SD Custom; HD swap], [Freeview (UK); Berks and North Hants]
Sky UK changes are normally Tuesday/Thursday. Consider changing your days to Wednesday/Friday.
satteliter (12-03-23)
Posting Permissions
Reply With Quote