Random re-boot

[Twizzle]

I have not updated my U4 for a few years now.

As most of my requirements are fulfilled by downloading programmes straight to the U4 (I would only record ABC 7pm news and one or 2 other programmes per week) I find that everything works fine and on the theory of “If it aint broke don’t fix it” I have not updated it because often there are issues after an update.

The only problem I have with the U4 is that it randomly re-boots (strangely between approx 5 pm & 7.30pm) if one is using after that it remains stable and doesn’t re-boot.

My question is this, is there any chance that an Update could possibly fix the random re-booting, my gut feeling is no but you guys are the experts.

[MrQuade]

The only problem I have with the U4 is that it randomly re-boots (strangely between approx 5 pm & 7.30pm) if one is using after that it remains stable and doesn’t re-boot.

My question is this, is there any chance that an Update could possibly fix the random re-booting, my gut feeling is no but you guys are the experts.

We'd have to know why it was rebooting in order to answer that question.

You say it is random between those hours? Does it happen multiple times, or only ever once on those hours?

Does it happen right after you press any buttons, or just happens when simply watching TV, or a recording?

How does it reboot? Just goes blank and reboots, or does it produce a bunch of text on screen and restart?
If the latter, then it would help if you can post the resulting crashlog file to the forum, and that will generally pinpoint the issue.

I find that everything works fine and on the theory of “If it aint broke don’t fix it” I have not updated it because often there are issues after an update.

As older versions of firmware aren't "supported" any more as-such, then there is not much that can be done to help if there is an issue unless you do update.

I would recommend an update regardless.

[Twizzle]

The only problem I have with the U4 is that it randomly re-boots (strangely between approx 5 pm & 7.30pm) if one is using after that it remains stable and doesn’t re-boot.

My question is this, is there any chance that an Update could possibly fix the random re-booting, my gut feeling is no but you guys are the experts.

We'd have to know why it was rebooting in order to answer that question.

You say it is random between those hours? Does it happen multiple times, or only ever once on those hours?

Usually 3 or 4 times during that period

Does it happen right after you press any buttons, or just happens when simply watching TV, or a recording?

Just watching a recording & it re-boots no buttons touched.

How does it reboot? Just goes blank and reboots, or does it produce a bunch of text on screen and restart?
If the latter, then it would help if you can post the resulting crashlog file to the forum, and that will generally pinpoint the issue.

It goes straight to the blue screen no text and then goes through the re-booting process.

I find that everything works fine and on the theory of “If it aint broke don’t fix it” I have not updated it because often there are issues after an update.

As older versions of firmware aren't "supported" any more as-such, then there is not much that can be done to help if there is an issue unless you do update.

I would recommend an update regardless.

I am quite wary of doing an update. Do I need to back up settings? I have very good NBN speed, is there any reason not to update over the net?

[Paul_oz53]

Take a backup and give it a try over the Internet but if the problem persists do the USB update and don't restore settings.

The USB update restores to a clean, known state whereas the Internet update retains plugins and customisations that could be a source of the problem.

But are you sure the U4 isn't overheating? Menu>>Information>>About. Mine is running at 59-60°C. Your symptoms may be heat related. The SOC fan can be a problem for older U4s.

[MrQuade]

I am quite wary of doing an update. Do I need to back up settings? I have very good NBN speed, is there any reason not to update over the net?

Yes, you should always backup your settings.

If the firmware is as old as you say, then it is likely to be old enough that you will need to perform a USB update.

Check the firmware revision shown in the "MENU->Information->About" screen.

There is a "Release" field, which should have a number like "16.1", "17.5" or "19.3" (That's the <year>.<month> of that major release).

There is then a "Build" field which shows the datestamp from the last online update version.

Online updates only update the "Build", but will never update the "Release", as those are too big of a change to allow for smooth patching.


A USB update formats the Wiz's onboard flash memory, and installs a brand new set of software from scratch, so you know that everything will be in a known good state.

If you are coming from the 17.5 version firmware, then you can restore your settings and you should be back to normal.
If you are coming from the 16.1 firmware, then I don't think the settings will be compatible, so you would need to set up from scratch.

Since you don't have many recordings, then it won't be too much hardship to do everything from scratch again though.

A USB update won't affect any of the recordings that are on the Wiz's harddisk.

[Twizzle]

It is running at 51 degrees.

[MrQuade]

It is running at 51 degrees.

Sorry, I didn't spot your other answers in there in bold. You can split the quotes up to separate your responses from our questions to make it easier to read.

Random reboots like that with no crashlog would suggest that there is a hardware fault.
Odd that it would occur at a particular time of day though.
Are more tuners in use at that time? (ie. recordings on channels other than what you are watching)?

You could post a copy of the /var/log/messages file here. That may contain some errors leading up to eventual crashes.

[Twizzle]

Thanks for replying Mr. Quade and everyone else. Where do I find the \var\log\messages ?

Please. If it's not too much trouble could you tell me where I could find the link to download the zip file preparatory to updating.

I have attached Beyonwiz details.

[Grumpy_Geoff]

There was an issue with U4s randomly rebooting on older firmware (due to a memory leak I think).
The enigma2 exit codes from file "enigma2_execution.log" in /home/root/logs may give a clue, particularly if the exit code is 137 (from memory).

[Twizzle]

There was an issue with U4s randomly rebooting on older firmware (due to a memory leak I think).
The enigma2 exit codes from file "enigma2_execution.log" in /home/root/logs may give a clue, particularly if the exit code is 137 (from memory).

Thank you Grumpy Geoff. In my Information attachment above I can see Enigma2 but how do I access the file?

Also it is good to know that U4s have had this rebooting problem on older firmware. Thank you

[Grumpy_Geoff]

There was an issue with U4s randomly rebooting on older firmware (due to a memory leak I think).
The enigma2 exit codes from file "enigma2_execution.log" in /home/root/logs may give a clue, particularly if the exit code is 137 (from memory).

Thank you Grumpy Geoff. In my Information attachment above I can see Enigma2 but how do I access the file?

Also it is good to know that U4s have had this rebooting problem on older firmware. Thank you

You can use File Commander (MENU>>Sources / Files) to copy off the /home/root/logs/enigma2_execution.log file to a USB thumb drive. To do that:
Insert a USB thumb drive into the U4.
Open the File Commander plugin -

• Navigate the left panel to the thumb drive entry and press OK to open it
  This is the "target" panel
• Press NEXT to swap to the right panel
  This will be the "source" panel
• Navigate through "Internal flash", then "home", then "root", then "log" (to directory /home/root/logs/).
• Select the file "enigma2_execution.log" (have the cursor on it)
• Press YELLOW to copy the selected file to the target panel's location
  Reply yes to the copy prompt
• EXIT back to the main menu.

Note - instead of copying to USB, you can copy the file to any network location, or even to the U4's recordings directory (/media/hdd/movie/), and fetch it from there using Windows Explorer.

If you copied it to USB, go to the "Plugins" column and scroll towards the bottom and select the "SimpleUmount" entry and open it (alternatively, select and open it from the Plugin browser).
Select the thumb drive if it's not already selected, and press OK. Reply yes to the "really umount..." prompt.

[Twizzle]

Thanks I'll give that a go tomorrow & get back.

[sub3R]

Mine is running at 59-60°C.

I don’t want to de-rail this topic, but those are fairly high temperatures Paul. The SoC temps in both our U4s don’t get over 53ºC. Is the fan working ok?

[MrQuade]

I don’t want to de-rail this topic, but those are fairly high temperatures Paul. The SoC temps in both our U4s don’t get over 53ºC. Is the fan working ok?

That's still quite a normal operating temperature for a SoC.
Worry if it starts getting near 70 degrees.

Venting the heat and keeping the rest of the components cooler is enough.

[Paul_oz53]

I don’t want to de-rail this topic, but those are fairly high temperatures Paul. The SoC temps in both our U4s don’t get over 53ºC. Is the fan working ok?

That's still quite a normal operating temperature for a SoC.
Worry if it starts getting near 70 degrees.

Venting the heat and keeping the rest of the components cooler is enough.

Hi guys, I suspect the fan is aging so a pre-emptive replacement is now high on my agenda. The other unit is running 50ºC. With the 120mm external USB fan sitting on the case it dropped to 38ºC. It has passable space around it in the TV stand.

[Twizzle]

There was an issue with U4s randomly rebooting on older firmware (due to a memory leak I think).
The enigma2 exit codes from file "enigma2_execution.log" in /home/root/logs may give a clue, particularly if the exit code is 137 (from memory).

Thanks to your wonderful instructions Grumpy Geoff, I was able to copy the Enigma log to a drive and when opened it does indeed show Terminating with code 137.

I will be updating today could someone please tell me where i can find the correct link for the Update. I've seen one at the top of this overall subject but has it been amended?

Thanks everyone once again for all the help. I doubt that many of us would have persevered with Beyonwiz if it wasn't for this terrific Forum.

[Grumpy_Geoff]

Thanks to your wonderful instructions Grumpy Geoff, I was able to copy the Enigma log to a drive and when opened it does indeed show Terminating with code 137.

How many "enigma2 terminated with code 137" entries were present?

I will be updating today could someone please tell me where i can find the correct link for the Update. I've seen one at the top of this overall subject but has it been amended?

Yeah that's it - the one pinned in "Announcements", thread title "Current firmware - 19.3_20211010".

[Twizzle]

Thanks Grumpy Geoff. Below is the Log.

Thu Apr 14 07:54:02 AEST 2022: executing enigma2
Thu Apr 14 07:54:40 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 07:54:41 AEST 2022: executing enigma2
Thu Apr 14 07:55:28 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 07:55:28 AEST 2022: executing enigma2
Thu Apr 14 07:56:03 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 07:56:04 AEST 2022: executing enigma2
Thu Apr 14 08:01:01 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:01:02 AEST 2022: executing enigma2
Thu Apr 14 08:01:05 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:01:05 AEST 2022: executing enigma2
Thu Apr 14 08:01:08 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:01:09 AEST 2022: executing enigma2
Thu Apr 14 08:01:27 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:01:27 AEST 2022: executing enigma2
Thu Apr 14 08:01:31 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:01:31 AEST 2022: executing enigma2
Thu Apr 14 08:01:41 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:01:41 AEST 2022: executing enigma2
Thu Apr 14 08:01:44 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:01:44 AEST 2022: executing enigma2
Thu Apr 14 08:01:48 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:01:48 AEST 2022: executing enigma2
Thu Apr 14 08:01:51 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:01:51 AEST 2022: executing enigma2
Thu Apr 14 08:01:54 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:01:54 AEST 2022: executing enigma2
Thu Apr 14 08:01:57 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:06:59 AEST 2022: executing enigma2
Thu Apr 14 08:07:02 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:07:03 AEST 2022: executing enigma2
Thu Apr 14 08:07:06 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:07:06 AEST 2022: executing enigma2
Thu Apr 14 08:07:17 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:07:18 AEST 2022: executing enigma2
Thu Apr 14 08:07:21 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:07:21 AEST 2022: executing enigma2
Thu Apr 14 08:07:25 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:07:25 AEST 2022: executing enigma2
Thu Apr 14 08:07:29 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:07:29 AEST 2022: executing enigma2
Thu Apr 14 08:07:47 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:07:48 AEST 2022: executing enigma2
Thu Apr 14 08:07:53 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:07:53 AEST 2022: executing enigma2
Thu Apr 14 08:07:58 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:07:58 AEST 2022: executing enigma2
Thu Apr 14 08:08:01 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:13:05 AEST 2022: executing enigma2
Thu Apr 14 08:18:45 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:18:45 AEST 2022: executing enigma2
Thu Apr 14 08:18:50 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:18:51 AEST 2022: executing enigma2
Thu Apr 14 08:19:14 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:19:14 AEST 2022: executing enigma2
Thu Apr 14 08:19:17 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:19:17 AEST 2022: executing enigma2
Thu Apr 14 08:19:27 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:19:28 AEST 2022: executing enigma2
Thu Apr 14 08:34:52 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 08:34:53 AEST 2022: executing enigma2
Thu Apr 14 08:46:20 AEST 2022: enigma2 terminated with code 2
Thu Apr 14 08:47:10 AEST 2022: executing enigma2
Thu Apr 14 18:10:54 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 18:10:54 AEST 2022: executing enigma2
Thu Apr 14 18:16:26 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 18:16:26 AEST 2022: executing enigma2
Thu Apr 14 18:16:29 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 18:16:29 AEST 2022: executing enigma2
Thu Apr 14 18:16:35 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 18:16:36 AEST 2022: executing enigma2
Thu Apr 14 18:16:40 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 18:16:40 AEST 2022: executing enigma2
Thu Apr 14 18:16:45 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 18:16:45 AEST 2022: executing enigma2
Thu Apr 14 18:16:47 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 18:16:48 AEST 2022: executing enigma2
Thu Apr 14 18:17:08 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 18:17:08 AEST 2022: executing enigma2
Thu Apr 14 18:17:10 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 18:17:11 AEST 2022: executing enigma2
Thu Apr 14 18:17:13 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 18:17:14 AEST 2022: executing enigma2
Thu Apr 14 18:17:16 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 18:17:16 AEST 2022: executing enigma2
Thu Apr 14 18:17:19 AEST 2022: enigma2 terminated with code 137
Thu Apr 14 18:18:51 AEST 2022: executing enigma2
Fri Apr 15 14:46:54 AEST 2022: enigma2 terminated with code 137
Fri Apr 15 14:46:54 AEST 2022: executing enigma2
Fri Apr 15 14:59:01 AEST 2022: enigma2 terminated with code 137
Fri Apr 15 14:59:01 AEST 2022: executing enigma2
Fri Apr 15 15:00:14 AEST 2022: enigma2 terminated with code 137
Fri Apr 15 15:00:15 AEST 2022: executing enigma2
Fri Apr 15 15:00:19 AEST 2022: enigma2 terminated with code 137
Fri Apr 15 15:00:20 AEST 2022: executing enigma2
Fri Apr 15 15:00:23 AEST 2022: enigma2 terminated with code 137
Fri Apr 15 15:00:23 AEST 2022: executing enigma2
Fri Apr 15 15:00:26 AEST 2022: enigma2 terminated with code 137
Fri Apr 15 15:00:27 AEST 2022: executing enigma2
Fri Apr 15 15:00:29 AEST 2022: enigma2 terminated with code 137
Fri Apr 15 15:00:30 AEST 2022: executing enigma2
Fri Apr 15 15:00:43 AEST 2022: enigma2 terminated with code 137
Fri Apr 15 15:00:44 AEST 2022: executing enigma2
Fri Apr 15 15:01:41 AEST 2022: enigma2 terminated with code 137
Fri Apr 15 15:01:42 AEST 2022: executing enigma2
Fri Apr 15 15:01:44 AEST 2022: enigma2 terminated with code 137
Fri Apr 15 15:01:45 AEST 2022: executing enigma2
Fri Apr 15 15:02:01 AEST 2022: enigma2 terminated with code 137
Fri Apr 15 15:02:01 AEST 2022: executing enigma2
Fri Apr 15 15:02:21 AEST 2022: enigma2 terminated with code 137
Fri Apr 15 15:02:21 AEST 2022: executing enigma2
Thu Jan 1 10:01:10 AEST 1970: executing enigma2
Sat Apr 16 01:10:55 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 01:10:55 AEST 2022: executing enigma2
Sat Apr 16 02:48:26 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 02:48:26 AEST 2022: executing enigma2
Sat Apr 16 03:04:01 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:04:02 AEST 2022: executing enigma2
Sat Apr 16 03:13:26 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:13:26 AEST 2022: executing enigma2
Sat Apr 16 03:13:51 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:13:52 AEST 2022: executing enigma2
Sat Apr 16 03:13:56 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:13:57 AEST 2022: executing enigma2
Sat Apr 16 03:13:59 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:13:59 AEST 2022: executing enigma2
Sat Apr 16 03:14:06 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:14:06 AEST 2022: executing enigma2
Sat Apr 16 03:14:08 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:14:08 AEST 2022: executing enigma2
Sat Apr 16 03:14:18 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:14:18 AEST 2022: executing enigma2
Sat Apr 16 03:14:21 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:14:21 AEST 2022: executing enigma2
Sat Apr 16 03:14:31 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:14:31 AEST 2022: executing enigma2
Sat Apr 16 03:14:39 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:14:40 AEST 2022: executing enigma2
Sat Apr 16 03:14:42 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:19:43 AEST 2022: executing enigma2
Sat Apr 16 03:19:45 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:19:46 AEST 2022: executing enigma2
Sat Apr 16 03:19:48 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:19:49 AEST 2022: executing enigma2
Sat Apr 16 03:19:52 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:19:53 AEST 2022: executing enigma2
Sat Apr 16 03:19:56 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:19:57 AEST 2022: executing enigma2
Sat Apr 16 03:20:00 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:20:00 AEST 2022: executing enigma2
Sat Apr 16 03:20:07 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:20:09 AEST 2022: executing enigma2
Sat Apr 16 03:20:31 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:20:31 AEST 2022: executing enigma2
Sat Apr 16 03:20:41 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:20:41 AEST 2022: executing enigma2
Sat Apr 16 03:20:47 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:20:47 AEST 2022: executing enigma2
Sat Apr 16 03:28:25 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:28:26 AEST 2022: executing enigma2
Sat Apr 16 03:31:36 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:31:36 AEST 2022: executing enigma2
Sat Apr 16 03:31:38 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:31:38 AEST 2022: executing enigma2
Sat Apr 16 03:31:41 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:31:41 AEST 2022: executing enigma2
Sat Apr 16 03:31:47 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:31:48 AEST 2022: executing enigma2
Sat Apr 16 03:31:54 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:31:54 AEST 2022: executing enigma2
Sat Apr 16 03:31:56 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:31:57 AEST 2022: executing enigma2
Sat Apr 16 03:32:07 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:32:07 AEST 2022: executing enigma2
Sat Apr 16 03:33:30 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:33:30 AEST 2022: executing enigma2
Sat Apr 16 03:33:32 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:33:33 AEST 2022: executing enigma2
Sat Apr 16 03:41:01 AEST 2022: executing enigma2
Sat Apr 16 03:41:09 AEST 2022: enigma2 terminated with code 137
: executing enigma2
: enigma2 terminated with code 137
Sat Apr 16 03:41:13 AEST 2022: executing enigma2
Sat Apr 16 03:41:13 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:41:13 AEST 2022: executing enigma2
Sat Apr 16 03:41:16 AEST 2022: executing enigma2
Sat Apr 16 03:41:23 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:41:23 AEST 2022: executing enigma2
: enigma2 terminated with code 137
Sat Apr 16 03:41:33 AEST 2022: executing enigma2
Sat Apr 16 03:41:53 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:41:54 AEST 2022: executing enigma2
Sat Apr 16 03:41:56 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:41:56 AEST 2022: executing enigma2
Sat Apr 16 03:42:03 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:42:03 AEST 2022: executing enigma2
Sat Apr 16 03:42:05 AEST 2022: enigma2 terminated with code 137
Sat Apr 16 03:47:06 AEST 2022: executing enigma2
Sat Apr 16 07:22:35 AEST 2022: enigma2 terminated with code 2
Sat Apr 16 07:23:22 AEST 2022: executing enigma2
Sun Apr 17 07:31:26 AEST 2022: enigma2 terminated with code 2
Thu Jan 1 10:01:05 AEST 1970: executing enigma2
Sun Apr 17 15:30:39 AEST 2022: enigma2 terminated with code 137
Sun Apr 17 15:30:40 AEST 2022: executing enigma2
Sun Apr 17 17:28:19 AEST 2022: enigma2 terminated with code 137
Sun Apr 17 17:28:20 AEST 2022: executing enigma2
Sun Apr 17 17:39:29 AEST 2022: enigma2 terminated with code 137
Sun Apr 17 17:39:30 AEST 2022: executing enigma2
Sun Apr 17 17:49:19 AEST 2022: enigma2 terminated with code 137
Sun Apr 17 17:49:20 AEST 2022: executing enigma2
Sun Apr 17 17:53:17 AEST 2022: executing enigma2
Sun Apr 17 17:58:17 AEST 2022: enigma2 terminated with code 137
Sun Apr 17 17:58:18 AEST 2022: executing enigma2
Sun Apr 17 18:03:25 AEST 2022: enigma2 terminated with code 137
Sun Apr 17 18:03:25 AEST 2022: executing enigma2
Sun Apr 17 19:03:02 AEST 2022: enigma2 terminated with code 137
Sun Apr 17 19:03:02 AEST 2022: executing enigma2
Sun Apr 17 19:14:25 AEST 2022: enigma2 terminated with code 137
Sun Apr 17 19:14:25 AEST 2022: executing enigma2
Sun Apr 17 19:20:11 AEST 2022: enigma2 terminated with code 137
Sun Apr 17 19:20:11 AEST 2022: executing enigma2
Sun Apr 17 19:26:08 AEST 2022: enigma2 terminated with code 137
Sun Apr 17 19:26:08 AEST 2022: executing enigma2
Sun Apr 17 19:40:03 AEST 2022: enigma2 terminated with code 137
Sun Apr 17 19:40:04 AEST 2022: executing enigma2
Sun Apr 17 20:57:27 AEST 2022: enigma2 terminated with code 137
Sun Apr 17 20:57:27 AEST 2022: executing enigma2
Sun Apr 17 20:58:50 AEST 2022: executing enigma2
Mon Apr 18 07:13:38 AEST 2022: enigma2 terminated with code 1
Mon Apr 18 07:59:23 AEST 2022: executing enigma2
Mon Apr 18 16:30:32 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 16:30:32 AEST 2022: executing enigma2
Mon Apr 18 18:34:51 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:34:51 AEST 2022: executing enigma2
Mon Apr 18 18:37:01 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:37:02 AEST 2022: executing enigma2
Mon Apr 18 18:37:27 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:37:27 AEST 2022: executing enigma2
Mon Apr 18 18:41:06 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:41:07 AEST 2022: executing enigma2
Mon Apr 18 18:41:10 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:41:11 AEST 2022: executing enigma2
Mon Apr 18 18:41:12 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:41:12 AEST 2022: executing enigma2
Mon Apr 18 18:41:16 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:41:16 AEST 2022: executing enigma2
Mon Apr 18 18:41:28 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:41:29 AEST 2022: executing enigma2
Mon Apr 18 18:41:33 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:41:33 AEST 2022: executing enigma2
Mon Apr 18 18:41:35 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:41:35 AEST 2022: executing enigma2
Mon Apr 18 18:42:15 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:42:16 AEST 2022: executing enigma2
Mon Apr 18 18:43:43 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:43:44 AEST 2022: executing enigma2
Mon Apr 18 18:43:50 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:43:50 AEST 2022: executing enigma2
Mon Apr 18 18:43:54 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:43:54 AEST 2022: executing enigma2
Mon Apr 18 18:43:58 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:43:58 AEST 2022: executing enigma2
Mon Apr 18 18:44:06 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:44:06 AEST 2022: executing enigma2
Mon Apr 18 18:44:09 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:44:09 AEST 2022: executing enigma2
Mon Apr 18 18:44:14 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:44:17 AEST 2022: executing enigma2
Mon Apr 18 18:44:19 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:44:23 AEST 2022: executing enigma2
Mon Apr 18 18:45:45 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:45:45 AEST 2022: executing enigma2
Mon Apr 18 18:45:55 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:45:55 AEST 2022: executing enigma2
Mon Apr 18 18:46:23 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:46:24 AEST 2022: executing enigma2
Mon Apr 18 18:46:26 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:46:26 AEST 2022: executing enigma2
Mon Apr 18 18:46:28 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:46:29 AEST 2022: executing enigma2
Mon Apr 18 18:46:31 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:46:31 AEST 2022: executing enigma2
Mon Apr 18 18:46:48 AEST 2022: enigma2 terminated with code 137
Mon Apr 18 18:46:48 AEST 2022: executing enigma2
Mon Apr 18 18:46:51 AEST 2022: executing enigma2
Mon Apr 18 18:48:09 AEST 2022: enigma2 terminated with code 1
Mon Apr 18 18:49:24 AEST 2022: executing enigma2

[prl]

Enigma2 terminating with error code 137 most often means that the system has run out of available memory.

Do you use AutoTimers?

[Twizzle]

Enigma2 terminating with error code 137 most often means that the system has run out of available memory.

Do you use AutoTimers?

Well I've got only got 6. However given that Grumpy Geoff has said rebooting with Error Code 137 was a known problem with older Firmware and now that I've updated, I'm hoping that's an end to it. I'll report back if any random rebooting occurs.

[Grumpy_Geoff]

Do you use AutoTimers?

I doubt it's the AutoTimer plugin given the timing between OOM kills. The AutoTimer plugin has an initial startup delay before its first poll. These kills appear to come quickly.
Take the last 5 as an example -
Mon Apr 18 18:45:55 AEST 2022: executing enigma2
Mon Apr 18 18:46:23 AEST 2022: enigma2 terminated with code 137
- Killed after 28 seconds
Mon Apr 18 18:46:24 AEST 2022: executing enigma2
Mon Apr 18 18:46:26 AEST 2022: enigma2 terminated with code 137
- Killed after 2 seconds
Mon Apr 18 18:46:26 AEST 2022: executing enigma2
Mon Apr 18 18:46:28 AEST 2022: enigma2 terminated with code 137
- Killed after 2 seconds
Mon Apr 18 18:46:29 AEST 2022: executing enigma2
Mon Apr 18 18:46:31 AEST 2022: enigma2 terminated with code 137
- Killed after 2 seconds
Mon Apr 18 18:46:31 AEST 2022: executing enigma2
Mon Apr 18 18:46:48 AEST 2022: enigma2 terminated with code 137
- Killed after 17 seconds

I'd be suspecting something else, like DLNA (server or client).

[prl]

I doubt it's the AutoTimer plugin given the timing between OOM kills. The AutoTimer plugin has an initial startup delay before its first poll.

You're probably right.

[Grumpy_Geoff]

I doubt it's the AutoTimer plugin given the timing between OOM kills. The AutoTimer plugin has an initial startup delay before its first poll.

You're probably right.

Too long ago to remember now, and I can't be bothered searching it up, but my money for OOM is either the DLNA client, the miniDLNA server, or SMB.

[MrQuade]

I wonder why during that time of day though.

Some device on the network is scheduled to switch on around those hours of the day?

[Twizzle]

Thanks everyone. The problem would appear to be solved after the update. No reboots at all yesterday at any time after the update. Very happy.

[Grumpy_Geoff]

Thanks everyone. The problem would appear to be solved after the update.

Good.

No reboots at all yesterday at any time after the update. Very happy.

Note that they weren't reboots, as it wasn't a complete restart of the Wiz, they were restarts of enigma2/GUI.

[Twizzle]

If I were to delete the Enigma log file to start afresh would the U4 automatically create a new one? I'd imagine it would but just want to be sure.

By the way still no reboots and all is well.

[Grumpy_Geoff]

If I were to delete the Enigma log file to start afresh would the U4 automatically create a new one? I'd imagine it would but just want to be sure.

If you mean the "enigma2_execution.log" file, then no need as it'll be trimmed automatically.

[Twizzle]

Thanks that's great, I'll leave it as it is.

[prl]

But the answer to your original question is that there's no issue if you delete the enigma2_execution.log. It will be re-created the next time something is written to it.

[Grumpy_Geoff]

But the answer to your original question is that there's no issue if you delete the enigma2_execution.log. It will be re-created the next time something is written to it.

... which is when the GUI starts up, or stops (or is killed), and the same for the "GUI pre-start" script if it exists.

[Twizzle]

Thanks