T2 continually rebooting

[jpp]

My T2, which has been working flawlessly over the past 4 years or more has started to sporadically do a cold reboot - about every 15 to 30 min or so.

It happened just today - is was running perfectly yesterday. I've opened it up and checked that it was not running too hot (my 2 small fans still running happily too). Prodded the appropriate parts to check for loose connections etc etc, but all to no avail.

Is this a known issue with a known cause? If not, then I think I'm in the market for either a pre-loved T2 (my first choice - bare with no disc just fine) or a V2. Just looking briefly at the V2 Forum, I gather that there is still some way to go to get it to the "appliance" status of the T2.

Any thoughts anyone?

[Grumpy_Geoff]

IceTV?
viewtopic.php?f=50&t=14484&p=190632#p190632

Try disabling IceTV and see what happens.

[jpp]

OK, thanks for the quick heads-up Geoff. See that others are having other symptoms as well since this morning.

Disabled ICETV at 3.55pm.

Makes a lot of sense actually, as on average, the reboots occurred around 15 min, i.e ICETV's regular fetch and send.

[Grumpy_Geoff]

Oh, I see our T2 is doing the same.

Code: Select all

Sat Oct 24 08:48:02 AWST 2020: executing /usr/bin/enigma2_pre_start.sh
Sat Oct 24 08:48:03 AWST 2020: /usr/bin/enigma2_pre_start.sh terminated with code 0
Sat Oct 24 08:48:03 AWST 2020: executing enigma2
Sat Oct 24 11:23:34 AWST 2020: enigma2 terminated with code 1
Sun Oct 25 08:47:58 AWST 2020: executing /usr/bin/enigma2_pre_start.sh
Sun Oct 25 08:47:58 AWST 2020: /usr/bin/enigma2_pre_start.sh terminated with code 0
Sun Oct 25 08:47:58 AWST 2020: executing enigma2
Sun Oct 25 09:19:33 AWST 2020: enigma2 terminated with code 137
Sun Oct 25 09:19:33 AWST 2020: executing /usr/bin/enigma2_pre_start.sh
Sun Oct 25 09:19:33 AWST 2020: /usr/bin/enigma2_pre_start.sh terminated with code 0
Sun Oct 25 09:19:33 AWST 2020: executing enigma2
Sun Oct 25 10:24:21 AWST 2020: enigma2 terminated with code 137
Sun Oct 25 10:24:22 AWST 2020: executing /usr/bin/enigma2_pre_start.sh
Sun Oct 25 10:24:22 AWST 2020: /usr/bin/enigma2_pre_start.sh terminated with code 0
Sun Oct 25 10:24:22 AWST 2020: executing enigma2
Sun Oct 25 11:02:39 AWST 2020: enigma2 terminated with code 137
Sun Oct 25 11:02:40 AWST 2020: executing /usr/bin/enigma2_pre_start.sh
Sun Oct 25 11:02:41 AWST 2020: /usr/bin/enigma2_pre_start.sh terminated with code 0
Sun Oct 25 11:02:41 AWST 2020: executing enigma2
Sun Oct 25 11:41:34 AWST 2020: enigma2 terminated with code 137
Sun Oct 25 11:41:35 AWST 2020: executing /usr/bin/enigma2_pre_start.sh
Sun Oct 25 11:41:39 AWST 2020: /usr/bin/enigma2_pre_start.sh terminated with code 0
Sun Oct 25 11:41:39 AWST 2020: executing enigma2
Sun Oct 25 12:20:45 AWST 2020: enigma2 terminated with code 137
Sun Oct 25 12:20:46 AWST 2020: executing /usr/bin/enigma2_pre_start.sh
Sun Oct 25 12:20:51 AWST 2020: /usr/bin/enigma2_pre_start.sh terminated with code 0
Sun Oct 25 12:20:51 AWST 2020: executing enigma2

T2 uses IceTV, and I see the plugin's log entries don't amount to much (except to indicate it's knackered) -

Code: Select all

2020-10-25 12:21:25 IceTV started
2020-10-25 12:21:29 Start update
2020-10-25 12:36:25 Start update

Looking in /var/log/messages I can see the OOM (out of memory) killer steps in and nukes enigma2.

I've disabled IceTV.
I see from OWIF's Box Info the T2 had (then) only 25MB free.
I rebooted the T2 and it's now reporting ~105MB free.

[Grumpy_Geoff]

I just checked the T4 and I can see the same unsuccessful IceTV updates.

[Grumpy_Geoff]

Crap in the guide data?

Code: Select all

...
{910}< 12708.446> [EPGFetcher] ERROR: lookup of 0x12 "Action" returned "Adventure"
{910}< 12708.446> [EPGFetcher] ERROR: lookup of 0x13 "Fantasy" returned "Sci-Fi"
{910}< 12708.449> [EPGFetcher] ERROR: lookup of 0x20 "Current Affairs" returned "News"
{910}< 12708.451> [EPGFetcher] ERROR: lookup of 0x10 "Drama" returned "Movie"
{910}< 12708.452> [EPGFetcher] ERROR: lookup of 0x11 "Thriller" returned "Crime"
{910}< 12708.453> [EPGFetcher] ERROR: lookup of 0x11 "Mystery" returned "Crime"
{910}< 12708.464> [EPGFetcher] ERROR: lookup of 0x11 "Mystery" returned "Crime"
{910}< 12708.487> [EPGFetcher] ERROR: lookup of 0x10 "Drama" returned "Movie"
{910}< 12708.505> [EPGFetcher] ERROR: lookup of 0x10 "Drama" returned "Movie"
{910}< 12708.525> [EPGFetcher] ERROR: lookup of 0x20 "Current Affairs" returned "News"
{910}< 12708.532> [EPGFetcher] ERROR: lookup of 0xa0 "Lifestyle" returned "Infotainment"
{910}< 12708.550> [EPGFetcher] ERROR: lookup of 0x11 "Thriller" returned "Crime"
{910}< 12708.561> [EPGFetcher] ERROR: lookup of 0x10 "Drama" returned "Movie"
{910}< 12708.561> [EPGFetcher] ERROR: lookup of 0x11 "Thriller" returned "Crime"
{910}< 12708.562> [EPGFetcher] ERROR: lookup of 0x11 "Mystery" returned "Crime"
{910}< 12708.564> [EPGFetcher] ERROR: lookup of 0x10 "Drama" returned "Movie"
{910}< 12708.565> [EPGFetcher] ERROR: lookup of 0x11 "Thriller" returned "Crime"
{910}< 12708.566> [EPGFetcher] ERROR: lookup of 0x11 "Mystery" returned "Crime"
{910}< 12708.575> [EPGFetcher] ERROR: lookup of 0x10 "Drama" returned "Movie"
{910}< 12708.580> [EPGFetcher] ERROR: lookup of 0xa0 "Lifestyle" returned "Infotainment"
{910}< 12708.593> [EPGFetcher] ERROR: lookup of 0x10 "Drama" returned "Movie"
{910}< 12708.600> [EPGFetcher] ERROR: lookup of 0xa0 "Lifestyle" returned "Infotainment"
{910}< 12708.606> [EPGFetcher] ERROR: lookup of 0x20 "Current Affairs" returned "News"
{910}< 12708.608> [EPGFetcher] ERROR: lookup of 0x01 "Horse Racing" returned "Cult"
{910}< 12708.617> [EPGFetcher] ERROR: lookup of 0x10 "Drama" returned "Movie"
{910}< 12708.618> [EPGFetcher] ERROR: lookup of 0x13 "Fantasy" returned "Sci-Fi"
{910}< 12708.621> [EPGFetcher] ERROR: lookup of 0xa0 "Lifestyle" returned "Infotainment"
{910}< 12708.623> [EPGFetcher] ERROR: lookup of 0xa0 "Lifestyle" returned "Infotainment"
{910}< 12708.628> [EPGFetcher] ERROR: lookup of 0x10 "Drama" returned "Movie"
{910}< 12708.866> Unhandled Error
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
    
  File "/usr/lib/python2.7/threading.py", line 754, in run
    
  File "/usr/lib/python2.7/site-packages/twisted/_threads/_threadworker.py", line 46, in work
    
  File "/usr/lib/python2.7/site-packages/twisted/_threads/_team.py", line 190, in doWork
    
--- <exception caught here> ---
  File "/usr/lib/python2.7/site-packages/twisted/python/threadpool.py", line 250, in inContext
    
  File "/usr/lib/python2.7/site-packages/twisted/python/threadpool.py", line 266, in <lambda>
    
  File "/usr/lib/python2.7/site-packages/twisted/python/context.py", line 122, in callWithContext
    
  File "/usr/lib/python2.7/site-packages/twisted/python/context.py", line 85, in callWithContext
    
  File "/usr/lib/enigma2/python/Plugins/SystemPlugins/IceTV/plugin.py", line 517, in doWork
    
exceptions.OverflowError: Python int too large to convert to C long

Over 3,000 of the "ERROR: lookup" entries per IceTV fetch.

[Grumpy_Geoff]

IceTV support are aware of the issue -
http://forum.icetv.com.au/iceforum/beyo ... 1#msg34181

[Paul_oz53]

I just checked the T4 and I can see the same unsuccessful IceTV updates.

The U4 had a spontaneous reboot earlier. Likely the same cause. No crash log.

My IceTV log is showing an error: "Error trying to fetch: Python int too large to convert to C long".

Same thing as Grumpy_Geoff reports.

[Grumpy_Geoff]

IceTV support say it is now fixed, but they don't know the root cause.

Huh?

[Paul_oz53]

IceTV support say it is now fixed, but they don't know the root cause.

Huh?

Working fine on my machines now.

[jpp]

Hmm... My T2 has now begun to show frozen/inoperative remote commands with spinning wheel??
Just now had a reboot again.

[Grumpy_Geoff]

Hmm... My T2 has now begun to show frozen/inoperative remote commands with spinning wheel??
Just now had a reboot again.

What enigma2 exit codes are reported for the relevant time in file "enigma2_execution.log"?
"enigma2 terminated with code {n}"

[Paul_oz53]

Hmm... My T2 has now begun to show frozen/inoperative remote commands with spinning wheel??
Just now had a reboot again.

I doubt it is the IceTV thing again. All four of my T/U units are now working normally.

Was the reboot spontaneous or did you reboot it?

If the former, it could be a hardware or PSU problem. If you have a spare 12v preferably 2 to 3 amp rated PSU available you can try that if the plug fits.

As Grumpy_Geoff requested, check the error codes. It may give us a clue to solving the problem.

[peteru]

I doubt it is the IceTV thing again.

It sounds like IceTV never figured out what went wrong at their end. The problem may be intermittent and could reoccur spontaneously until they figure out the root cause and institute measures to provide a permanent fix.

Perhaps disabling IceTV for a couple of days may be simpler than swapping power supplies.

[Paul_oz53]

I doubt it is the IceTV thing again.

It sounds like IceTV never figured out what went wrong at their end. The problem may be intermittent and could reoccur spontaneously until they figure out the root cause and institute measures to provide a permanent fix.

Perhaps disabling IceTV for a couple of days may be simpler than swapping power supplies.

Fair point Peter.

To know if the cause is hardware or firmware related we need to eliminate IceTV as a possible factor. Instability whilst IceTV is off would indicate that it requires further investigation.

[jpp]

Yes, I think ICETV is still the problem here as after I disabled it there were no more issues for the following 3 hours till about 11pm. My T2 then goes into deep sleep at midnight and reboots at 4pm for a 15 min ICETV fetch run and then goes into standby. So I don't have any activity till then and no opportunity for memory being gobbled up or corrupted till 4pm.

I did check the power supply, but the voltage was sitting nicely at 12.3V with the T2 running and disk spinning (measurement taken from inside the case, just at the back of the power connector)

[raj]

G'day,

This happened over the weekend to me in Sydney.

Essentially, I lost control of the remote control. The remote control functioned perfectly normally, however after around 20 or so minutes, the TV (LG 43" smart TV) would not respond to the remote, and then after around a further 20 minutes, the T2 would do a reboot.

Fortunately for me I was using the TV to watch the 24 Hours of Spa on the TV, but when I did venture on to the T2, it would either be rebooting or not responding to the remote.

[prl]

Using IceTV? The IceTV server went a bit strange on Sunday. After it was restarted, things seemed to settle down.

[raj]

Using IceTV?

Yes.

All good now.

Thanks.

[jpp]

OK here too now.
Ran the T2 with ICETV enabled for 4 hours last night with no issues. Maybe due to ICETV having removed the extra genres?
Are you still releasing an updated ICETV App to cater for extra genres PRL?

[prl]

... Maybe due to ICETV having removed the extra genres?

IceTV was only ever using two new genres, "Motorsport" and "Politics". "Motorsport" was removed on Sunday (changed to continuing genre "Motor Sport"), so "Politics" is the only remaining new genre in use.

"Politics" is currently being used to tag "QLD Votes 2020," ABC NEWS, 18:30, Sat, 31 Oct and "Biden V Trump: The Choice 2020," SBS/SBS HD, 20:30, Sun, 1 Nov.

The other genre errors, including the ones that Grumpy_Geoff still reports as seeing are errors on genres that are already in the IceTV plugin genre tables. I think that that's due to a continuing server-side problem, and that's the very next thing I'm going to look at.

Are you still releasing an updated ICETV App to cater for extra genres PRL?

"still releasing" => "already released"

I submitted the new tables yesterday, with about 90 new genres (including "Politics").

[prl]

The other genre errors, including the ones that Grumpy_Geoff still reports as seeing are errors on genres that are already in the IceTV plugin genre tables. I think that that's due to a continuing server-side problem, and that's the very next thing I'm going to look at.

I think that the error messages Grumpy_Geoff is still seeing are with adoxa's IceTVDesc plugin, but I haven't checked. I've asked Geoff to try uninstalling it and seeing whether the errors go away.

More details in the posts following the one I linked to.

[Grumpy_Geoff]

I think that the error messages Grumpy_Geoff is still seeing are with adoxa's IceTVDesc plugin, but I haven't checked. I've asked Geoff to try uninstalling it and seeing whether the errors go away.

They did