OpenVix 5.2 , hangs trying to shut down!

[tvtv]

If box tries to reboot I get message stuck on screen and box doesn’t complete a reboot

Your vu+ is shutting down...

I left on an hour but still some message

[tvtv]

VU+ Duo2
Chipset: BCM7424
CPU: Mipsel 1.3ghz Dual Core
Drivers: 2018-03-19
Kernel: 3.13.5
Gstreamer: 1.14.3
Python: 2.7.13
E2 (re)starts: 431
Skin: Magic-HD-Noire (1280 x 720)
system temp: 32c

[abu baniaz]

Is Enigma2 restart OK?

[abu baniaz]

I have tried this on another receiver, there was no problem.

Enable debug logs. Restart to take effect. Reboot so problem takes effect. Obtain log and attach it here.

[tvtv]

I have tried this on another receiver, there was no problem.

Enable debug logs. Restart to take effect. Reboot so problem takes effect. Obtain log and attach it here.

Ok, rebooted, but that worked, and give a different message on screen, my message that was stuck on screen previously was. ‘You vu+ is shutting down”. I don’t remember now what I last told it to do, if it wasn’t reboot, I have however sent the latest log using the interface. I did that before reading your message, and have since deleted it, so the build team will,have my log , I forgot to send myself a copy.

Hope that helps, definitely something is wrong if the message was stuck on screen.

Other than that, build is working well for me, except openwebif stops working sometimes (will monitor that and raise separate thread if it happens again.)

[tvtv]

Annoyingly the email I get back 2018-10-01 23:28 after sending low via the vu interface, doesn’t contain the log reference number, I have updated the box so I will get a copy in future, but why no ref num?

The email says the following, but it would be useful if you included the reference number to quote and referred to in a consistent way - just an idea, I know it pops up,on the box like “please quote 1538439554.9 when asking about this log” ,

“This is an automatic response....

Your e-mail is unlikely to be read. Please start a thread on the forum quoting the reference number of your log.

Your thread should specify what actions were done to cause the crash. Provide as much detail as possible.

See this thread for requirements on how to start a thread
http://www.world-of-satellite.com/sh...upport-Section
“