19 replies to this topic

[Raybobo]

Hi,

 

In 7.2, v, 31,12,2019 on my Vu+Duo2.

 

As already said, for a few weeks, I have at least 2 times a day a crash, and as I have to switch on/off manually, I cannot find always a log. But there's another problem.

 

As I have to power off with the switch when crash, each time, I have to mount again in System/Network to have my NAS back.

 

With 7.1 that was not making like this.

 

Thanks for the attention.

[WanWizard]

Nothing has been changed to mounting logic between 7.1 and 7.2. It has been the same for many years.

 

Automounts are processed by Enigma when it starts, and they can fail if the box starts quickly, is configured for DHCP, and the DHCP server is not fast enough. Does the same happen if you give the box a fixed IP?

[Raybobo]

 

 

Does the same happen if you give the box a fixed IP?

Yes, all my devices are in fixed IP.

[WanWizard]

It could be that because the connection to your NAS isn't closed, the NAS refuses the new connection attempt (already connected error), I've seen that before.

 

So the focus should be on fixing the crashes...

[Raybobo]

 

 

So the focus should be on fixing the crashes...

Oh, yes, please, I'm dreaming about this.

 

But I have no new log to send, because each time a crash succeed, as I have to power off/ power on, I have no log. The last one is on Jan. 15  and today, already 4 times...

[WanWizard]

How often  does it crash?

 

If often enough, you can restart Enigma in debug mode in the menu. It will create a debuglog file in /home/root, but as that is in flash, it can't get too big.

The log will not be wiped when you have to power off, so you can download that log from the box and attach it here after the restart.

[Raybobo]

 

 

How often  does it crash?

At least 2 times a day.

I will do it in debug mode and send the logs. Thanks

 

 

 

The log will not be wiped when you have to power off, so you can download that log from the box and attach it here after the restart.

But the last I can find is from Jan. 15, in hdd, so...

Edited by Raybobo, 31 January 2020 - 05:52.

[WanWizard]

This one isn't on the hdd, it is in /home/root, and is not called .log, but .debuglog.

 

p.s. When you post it, you need to zip it, otherwise it won't be accepted as a valid file.

[Raybobo]

For 3 days, after having done some things on my NAS, mount again ok.

 

But, right now, a crash, when moving 2 channels in my favourites, crash log joined.

 

Other crashes not succeeded since I am in debug mode, nope, strange!

Attached Files

•  enigma2_crash_1580655642.rar   1.57KB   2 downloads

Edited by Raybobo, 2 February 2020 - 16:07.

[WanWizard]

PC: 7687f850
    00000000 ffffffff 00000000 7fad1678
    00000003 7fad1678 00000000 00000000
    00087f40 00000062 00000001 ffffffff
    00000024 00000000 76b87c60 76a1f428
    00000000 7fad1678 769cf000 7fad17a8
    00f09c28 7fad1970 7fad1988 7fad19bc
    00000000 7687f780 00000010 00000000
    769d6e00 7fad15f0 7fad19a4 768811c4
Backtrace:
/usr/bin/enigma2(_Z17handleFatalSignaliP9siginfo_tPv) [0x46068C]
/lib/libc.so.6(gsignal) [0x7687F852]
-------FATAL SIGNAL

We see this more on a VU+, but as it doesn't contain any info, we have no clue where to start looking...

[Pr2]

You have crash when in move mode you try to delete something. I experience it too. So enable move mode, move your userbouquets or channels disable the move mode and then delete entries and it won't crash.

[WanWizard]

That would suggest a bug in the C code.

[Raybobo]

 

 

You have crash when in move mode you try to delete something. I experience it too. So enable move mode, move your userbouquets or channels disable the move mode and then delete entries and it won't crash.

Crash succeed when I disable move mode, right at this moment, 2 times, and then, after restart, channels are not moved, at the same position as prior trying to move...

Edited by Raybobo, 4 February 2020 - 05:29.

[Pr2]

I think it will better to create a zip containing the following files located into /etc/enigma2/

 

lamedb*

*.tv

*.radio

 

In telnet you can issue those commands:

 

cd /etc/enigma2/
tar -cvzf raybobo.tgz lamedb* *.tv *.radio

 

You will have a file /etc/enigma2/raybobo.tgz  retrieve it on your PC (by FTP for exemple) and post it here.

 

I am convinced that you have some special characters in one of your favorite that generate this crash when saving.

 

Pr2

[Pr2]

Another idea before creating the zip package.

 

Connect with telnet to your box and type:

init 4
cd /etc/enigma2/
dos2unix *.tv
dos2unix *.radio
dos2unix lamedb*
reboot

Pr2

Edited by Pr2, 4 February 2020 - 21:05.

[Raybobo]

Ok, done, 1st dos2unix and then the zip, here joined.
Thanks.
 

Edited by Frenske, 5 February 2020 - 22:36.
Removed the zip due to a request of another user. There seems to be illegal data in this zip.

[Pr2]

After the dos2unix are you still experience crashes?

[Raybobo]

Yes, 1 this morning just after having done the command.

[Pr2]

While moving channels?

[Raybobo]

No, I think if I remember that I was only browsing channels, as often, succeed at this moment