Just for something different

[csutak40]

Starting yesterday, the T2 sometimes decides to split a recording into bits. Not with all, so no idea why it picks on the ones that it does. There were about 3 last night - two today

1_0_1_313_310_3202_EEEE0000_0_0_0_20201027010822.jpg (90.38 KiB) Viewed 1475 times

Any ideas what would cause this?

[Grumpy_Geoff]

If I was to take a guess, I'd say either -
(i) the GUI/enigma2 crashed a few times whilst recording The Late Late Show With James Corden, or
(ii) there were driver crashes and the GUI was restarted a few times.

Your T2 is networked, so you can use Windows File Explorer from your computer, exploring the network connection to the Wiz to access the T2's "Logs" Samba share (\\BEYONWIZT2\Logs).
What enigma2 exit codes are reported for the relevant times in file "enigma2_execution.log", if any?
The format will be "enigma2 terminated with code {n}"
If there were only executing enigma2 entries and no matching enigma2 terminated entries then I'd suspect a driver crash of some sort.

Are there any crash logs present for the relevant times? If so, fetch a couple and post them here.

[Paul_oz53]

Judy,

Are you using IceTV ? It caused many T2s to crash at regular intervals over the weekend. That could explain your split recordings.

Paul

[prl]

Are you using IceTV ? It caused many T2s to crash at regular intervals over the weekend. That could explain your split recordings.

That's what I wondered, too, but the broken-up recording on Judy's screenshot is for a recording late on the evening of Mon 26 Oct. The current date/time is showing as Tue 27 01:08 and the recordings are all showing as "Yesterday 23:25", which makes it late Monday evening.

The IceTV server restart that fixed the IceTV issue was in the afternoon of Sun 25 Oct.

Not impossible, but if the time I got for that broken-up recording is correct, it seems unlikely.

[Brainz]

Have you power cycled the box since the Sunday IceTV crashes?
My T2 was in a bit of a state even after the server problems were sorted.

[Paul_oz53]

...

Not impossible, but if the time I got for that broken-up recording is correct, it seems unlikely.

Agree. My machines were all ok at the same time but worth being sure it's not a factor.

If it's not IceTV and it keeps happening we have to worry about hardware and/or firmware failures. I hope its not either of these.

Brainz suggestion is definitely worth a try.

[prl]

Brainz suggestion is definitely worth a try.

I agree. It will do no harm, and may help.

[csutak40]

Have you power cycled the box since the Sunday IceTV crashes?
My T2 was in a bit of a state even after the server problems were sorted.

Yes, I did... Hasn't happened yesterday. I was about to ask stupid questions, (like where do I find the logs...) but will now wait to see if it happens again. Happened two days in a row (all late at night) so will now keep my fingers crossed.
Surely both Wizes can't die on me...

[Grumpy_Geoff]

I was about to ask stupid questions, (like where do I find the logs...) but will now wait to see if it happens again. Happened two days in a row (all late at night) so will now keep my fingers crossed.

Did you have trouble understanding the Windows File Explorer method I described on how to get to the logs directory from your computer?
It should be as simple as clicking on the "BEYONWIZT2" entry under "Network" in Windows File Explorer.

As an alternative, click on this link -> file://BEYONWIZT2/Logs/ (if it doesn't show as a link, copy the text and paste it in the address bar in a browser).

Regardless, back in May you were able to show us the contents of the enigma2 execution log using File Commander (Sources / Files) - here.

Don't wait for it to happen again, check for any crash logs, and also show the contents of the enigma2 execution log.

[csutak40]

I didn't have trouble understanding it, had trouble finding it
This is what the folder looks like in explorer

2020-10-28_15-04-55.png (5.3 KiB) Viewed 1318 times

Anyway, after lots of fiddling (TBH not even sure how I managed) I found the correct folder
Now.. to see if I can find it again in order to attach it here (if not, I will have to copy/paste it

enigma2_execution.log

(16.61 KiB) Downloaded 34 times

Ah! putting a shortcut into Quick Access was a good idea!
There are also 4 crash logs there 19th 20th and 2x22nd. Should I attach those as well?

[csutak40]

Hmm. Can you open that file? It says "not downloaded yet"

[csutak40]

In case you can't open it, I discovered that the October entries aren't that long, so here they are:

Mon Oct 19 20:55:04 AEDT 2020: enigma2 terminated with code 5
Mon Oct 19 20:55:05 AEDT 2020: executing enigma2
Tue Oct 20 21:09:50 AEDT 2020: enigma2 terminated with code 5
Tue Oct 20 21:09:52 AEDT 2020: executing enigma2
Thu Oct 22 01:16:29 AEDT 2020: enigma2 terminated with code 5
Thu Oct 22 01:16:30 AEDT 2020: executing enigma2
Thu Oct 22 17:41:11 AEDT 2020: enigma2 terminated with code 5
Thu Oct 22 17:41:12 AEDT 2020: executing enigma2
Sun Oct 25 04:59:01 AEDT 2020: enigma2 terminated with code 137
Sun Oct 25 04:59:02 AEDT 2020: executing enigma2
Sun Oct 25 05:42:00 AEDT 2020: enigma2 terminated with code 137
Sun Oct 25 05:42:03 AEDT 2020: executing enigma2
Sun Oct 25 06:19:20 AEDT 2020: enigma2 terminated with code 137
Sun Oct 25 06:19:24 AEDT 2020: executing enigma2
Sun Oct 25 07:03:18 AEDT 2020: enigma2 terminated with code 137
Sun Oct 25 07:03:21 AEDT 2020: executing enigma2
Sun Oct 25 07:51:24 AEDT 2020: enigma2 terminated with code 137
Sun Oct 25 07:51:27 AEDT 2020: executing enigma2
Sun Oct 25 08:46:11 AEDT 2020: enigma2 terminated with code 137
Sun Oct 25 08:46:14 AEDT 2020: executing enigma2
Sun Oct 25 09:25:05 AEDT 2020: enigma2 terminated with code 137
Sun Oct 25 09:25:08 AEDT 2020: executing enigma2
Sun Oct 25 09:57:57 AEDT 2020: enigma2 terminated with code 137
Sun Oct 25 09:57:59 AEDT 2020: executing enigma2
Sun Oct 25 10:24:26 AEDT 2020: enigma2 terminated with code 137
Sun Oct 25 10:24:27 AEDT 2020: executing enigma2
Sun Oct 25 10:40:40 AEDT 2020: enigma2 terminated with code 137
Sun Oct 25 10:40:42 AEDT 2020: executing enigma2
Sun Oct 25 10:58:05 AEDT 2020: enigma2 terminated with code 137
Sun Oct 25 10:58:06 AEDT 2020: executing enigma2
Sun Oct 25 11:14:13 AEDT 2020: enigma2 terminated with code 137
Sun Oct 25 11:14:14 AEDT 2020: executing enigma2
Sun Oct 25 11:38:01 AEDT 2020: enigma2 terminated with code 137
Sun Oct 25 11:38:02 AEDT 2020: executing enigma2
Sun Oct 25 12:14:58 AEDT 2020: enigma2 terminated with code 137
Sun Oct 25 12:15:01 AEDT 2020: executing enigma2
Sun Oct 25 12:54:55 AEDT 2020: enigma2 terminated with code 137
Sun Oct 25 12:54:58 AEDT 2020: executing enigma2
Sun Oct 25 13:40:33 AEDT 2020: enigma2 terminated with code 137
Sun Oct 25 13:40:37 AEDT 2020: executing enigma2
Sun Oct 25 14:05:44 AEDT 2020: enigma2 terminated with code 137
Sun Oct 25 14:05:45 AEDT 2020: executing enigma2
Sun Oct 25 14:45:01 AEDT 2020: enigma2 terminated with code 137
Sun Oct 25 14:45:05 AEDT 2020: executing enigma2
Sun Oct 25 15:09:19 AEDT 2020: enigma2 terminated with code 137
Sun Oct 25 15:09:22 AEDT 2020: executing enigma2
Sun Oct 25 15:33:04 AEDT 2020: enigma2 terminated with code 137
Sun Oct 25 15:33:08 AEDT 2020: executing enigma2
Sun Oct 25 16:02:49 AEDT 2020: enigma2 terminated with code 137
Sun Oct 25 16:02:53 AEDT 2020: executing enigma2
Sun Oct 25 16:31:18 AEDT 2020: enigma2 terminated with code 137
Sun Oct 25 16:31:23 AEDT 2020: executing enigma2
Sun Oct 25 17:01:46 AEDT 2020: enigma2 terminated with code 137
Sun Oct 25 17:01:48 AEDT 2020: executing enigma2
Mon Oct 26 23:36:19 AEDT 2020: enigma2 terminated with code 137
Mon Oct 26 23:36:22 AEDT 2020: executing enigma2
Tue Oct 27 00:14:58 AEDT 2020: enigma2 terminated with code 137
Tue Oct 27 00:15:01 AEDT 2020: executing enigma2
Tue Oct 27 00:16:45 AEDT 2020: enigma2 terminated with code 137
Tue Oct 27 00:16:47 AEDT 2020: executing enigma2
Tue Oct 27 00:21:06 AEDT 2020: enigma2 terminated with code 137
Tue Oct 27 00:21:08 AEDT 2020: executing enigma2
Tue Oct 27 00:36:34 AEDT 2020: executing enigma2

[Grumpy_Geoff]

Hmm. Can you open that file? It says "not downloaded yet"

Yep

You may as well upload those 4 crash logs.

[prl]

Hmm. Can you open that file? It says "not downloaded yet"

Yep

You may as well upload those 4 crash logs.

From the console log, it doesn't appear that UI crashes caused all the breakups of the recording made late on Mon 26 Oct.

There were 5 recording restarts around 23:26 on Mon 26 Oct, but only a single GUI restart (at Mon Oct 26 23:36:19).

However, it looks like there have been frequent GUI restarts caused by SIGKILL, usually a symptom that the system has run out of memory and the Out-Of-Memory (OOM) killer has been invoked. It happened roughly hourly between 4 am and 5 pm on Sun 25 Oct. The crashes on that day may be because of the problems on the IceTV server on Sunday, because the problem stops at about 5pm when IceTV restarted their servers and fixed the problem (at least for most people).

[Grumpy_Geoff]

All of the 'enigma2 terminated with code 137' entries for Sun 25th will be from IceTV sucking the life out of the T2.
Things got better with the restart of around 5pm.
Then Monday evening 23:36 the enigma2/GUI was killed again (Fatal error signal "9", as far as I know, the linux operating system killed the GUI for some reason, maybe out of memory again?).
Rinse repeat for very early am Tuesday 00:16 and 00:21.
It appears to have a complete driver crash at 00:36, unless that was you turning it off with the rear switch?

[prl]

You may as well upload those 4 crash logs.

They may be worth having a look at of other reasons, but they're all way to early (most recent was Oct 22) to say anything about the broken-up recording on 26 Oct.

[Grumpy_Geoff]

From the console log, it doesn't appear that UI crashes caused all the breakups of the recording made late on Mon 26 Oct.

There were 5 recording restarts around 23:26 on Mon 26 Oct, but only a single GUI restart (at Mon Oct 26 23:36:19).

I beg to differ
Six fragments of the recording. There are six starts of enigma2.
Fragment #1 - starts on schedule, gets abnormally terminated 23:36:19
#2 - starts after GUI restart Mon Oct 26 23:36:22, records for ~37 mins
#3 - " restart Tue Oct 27 00:15:01, records for ~30 secs or so
#4 - " restart Tue Oct 27 00:16:47, records for ~4 mins
#5 - " restart Tue Oct 27 00:21:08, probably records until timer stops
The sixth fragment is "empty" - I can't quite get a handle on that one.

[prl]

You're right. I'd assumed that the restarts were all going to be on the same day.

[csutak40]

OK. here are the crash reports

Enigma2_crash_2020-10-19_20-54-27.log

(30.23 KiB) Downloaded 33 times

Enigma2_crash_2020-10-20_21-09-03.log

(30.14 KiB) Downloaded 32 times

Enigma2_crash_2020-10-22_01-15-57.log

(30.23 KiB) Downloaded 39 times

Enigma2_crash_2020-10-22_17-40-18.log

(30.18 KiB) Downloaded 34 times

Having had a better look, these are earlier in the week, so may be about something entirely different. There was a time (can't remember when) when the T2 ran out of room and I didn't notice
BTW, figured out why I couldn't navigate explorer. For some reason I had the navigator pane turned off

[MrQuade]

Those all seem to have IceTV "RecordWriteError" messages associated with the crash.

Fingers are starting to point...

[Grumpy_Geoff]

Judy, I think you filled up your 120GB SSD, at least on the first two logs I looked at.

There is/was a bug, #734 fixed by prl in March this year, that manifests when the IceTV plugin tries to report the failed timer to the IceTV server. The bug crashes the GUI. The fix for it is in the beta, but being on 20191106 you don't have it.

You should learn how to record to your NAS, given the amount of TV you record.

[csutak40]

This is temporary, will be buying a V2. (I have finally bought an enclosure )
My NAS is to be tested, may not work. I can no longer open the NAS drive except on the laptop (very weird, as they are all Win10) My IT guru friend thinks it is something MS did, as my NAS is no longer supported
BTW, I can't open the T2 either except on the same laptop. I need an expert to have a good look at what's going on.
The lockdown put a bit of a spanner in the works... My friend still can't come here, more than 25km away
I have been looking for a local IT tech, but a bit reluctant to hire someone I don't know

[Grumpy_Geoff]

My NAS is to be tested, may not work. I can no longer open the NAS drive except on the laptop (very weird, as they are all Win10) My IT guru friend thinks it is something MS did, as my NAS is no longer supported
BTW, I can't open the T2 either except on the same laptop. I need an expert to have a good look at what's going on.

My guess, based on nothing much, is that the minimum version of SMB that your recalcitrant PCs are requiring (e.g. SMB2) is too high for your NAS which may be configured for SMB1 (or perhaps not even capable of supporting anything higher).
You can change the SMB support level in Windows, if you can't change the NAS.
As to whether this is affecting the T2, I couldn't say.