This looks like a hardware related issue to me.
Try it with a new SD card and see if it still occurs.
Try it with a known good power supply.
If it still restarts, your N2+ probably has a problem.
Edit: A team member mentioned that it could be related to buggy UPnP code in Kodi itself.
I have exchanged the power supply (transformer power supply of an old WRT54G 12V 1A) against a switching power supply with 9V 0.6A.
I have also turned off UPnP.
Since yesterday I have no more crashes. The power supply (although somewhat undersized) does not seem to have been the problem in my opinion. A CPU stress test with “stress-ng” ran for about 4h while a stream was running.
I I remember correctly, the N2+ typically utilises a 12v/1.5a or 12v/2a ac adapter,by default so seeing 12v/1a would seem underpowered if the manufacturer themselves are not supplying it.
Could nail down the problem a bit.
Seems a problem around the SAMBA shares. If a foreign computer is booted and tries to access the SMB shares, this crash occurs.
Will try to investigate further.
IMHO, SMB has absolute nothing to do in an application. It is and must stay standalone.
sorry to hear that there are still crashes on your side.
I have not expierenced any crashes since i disabled uPnP. I also upgraded to the latest CE19.2 and seems to run pretty stable now.
Which SMB protocols do you use?
I only use the Odroid as client to access SMB shares from a NAS. Since this NAS only supports SMB1 i enabled this protocol somewhere in the options of CoreELEC. Maybe its worth to try this out?
Hi all,
at least I found the cause of my crash.
It was ./config/samba.conf → logfiles → root preexec = createlog
Commenting this off
# root preexec = createlog
and no more crashes.
The crashes do occur only if you try to access ‘logfiles’ via SAMBA from a foreign computer.
It appeared only on ever new access which might seem to make it random.
‘usr/bin/createlog’ is a script. No idea what is behind it.