[SOLVED] Kodi random restarts every 12 hours or so.

[Exnor]

Edit: Not really solved but it appears to be specific to this unit so i'm marking it as solved.

Ok so this is a new one.

I'm on the latest stable version and did a apt update + upgrade 2 days ago... There were about 5 things that were upgraded one of them a "firmware" package (?). All went fine, no problems etc etc... and i did a reboot (was not necessary but i just like to do it every time i update since i don't do it often).
OS boots up fine, Kodi start and everything appears fine....

But a few hour later, i noticed Kodi restarted (just Kodi, not the OS)... No big deal right? Noup, now Kodi restarts about every 12 hour or so :/. Either during idle time (this Pi runs 24/7 just for Xbian with Kodi, nothing else) or just in the middle of playing a movie, music, etc.

This new issue is just annoying because of the random crash during play. And it was not there before the last APT upgrade.

In the Log i noticed this that is repeating non stop (it was not there before and i have no idea what is causing it):

Terminal

2020-10-14 18:55:40.328 T:2657087712 ERROR: CCurlFile::Open failed with code 0 for http://127.0.0.1:80/web/currenttime:

(Google it but only found another uploaded log... no answers :/ )

Also i did not install any new Addons and there aren't any updates for the ones i have.

Terminal

@xbian / # cat /etc/os-release
PRETTY_NAME="XBian 1.0 (knockout)"
NAME=XBian
VERSION_ID=1.0
VERSION="1.0 (knockout)"
ID=raspbian
ID_LIKE=debian
ANSI_COLOR="1;31"
HOME_URL="http://www.xbian.org/"
SUPPORT_URL="http://forum.xbian.org/"
BUG_REPORT_URL="https://github.com/xbianonpi/xbian/issues"

lsb_release -da
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 10 (buster)
Release: 10
Codename: buster

Kodi log is on the link »» Kodi Log

APT upgrade Log »» term.log

APT History log »» history.log

Any ideias?
Thank you all.

[Exnor]

Update;

The error in the Kodi.log

Terminal

2020-10-14 18:55:40.328 T:2657087712 ERROR: CCurlFile::Open failed with code 0 for http://127.0.0.1:80/web/currenttime:~

was caused by a PVR addon that somehow became active (???)... I suspect an update?
Anyway i disabled it last night and so far that error as not appeared in the Log file.

Meanwhile i'm waiting to see of Kodi restarts again... I will update this thread.

[/term]

[Exnor]

Update 2:

So Kodi still random re-starts about every 12 hours or so... new Kodi log does not show any error this time :/

Any ideas ?

Thanks

[Nachteule]

Absolutely no idea

It can only be one of the packages that have been updated, and since it is not known which packages have been updated from which version to the current one, debugging is very difficult

[Exnor]

(19th Oct, 2020 10:52 PM)Nachteule Wrote:  Absolutely no idea

It can only be one of the packages that have been updated, and since it is not known which packages have been updated from which version to the current one, debugging is very difficult

so in the future avoid apt-get update + upgrade?

btw i have nothing else installed. vanilla image since the beginning and i only do updates when i remember .

PS: Is there any log that i can check? Anyway too see if and exit error message was logged in the OS logs?

[Nachteule]

(20th Oct, 2020 02:32 AM)Exnor Wrote:  

(19th Oct, 2020 10:52 PM)Nachteule Wrote:  Absolutely no idea

It can only be one of the packages that have been updated, and since it is not known which packages have been updated from which version to the current one, debugging is very difficult

so in the future avoid apt-get update + upgrade?

btw i have nothing else installed. vanilla image since the beginning and i only do updates when i remember .

PS: Is there any log that i can check? Anyway too see if and exit error message was logged in the OS logs?

You can run cat /var/log/dpkg.log | grep installed to see which packages has been installed

[Exnor]

(20th Oct, 2020 06:59 AM)Nachteule Wrote:  You can run cat /var/log/dpkg.log | grep installed to see which packages has been installed

Only saw your reply today...

The output give me this:

Terminal

utter@xbian / # cat /var/log/dpkg.log | grep installed
2020-11-01 17:32:08 status half-installed linux-image-bcm2836:armhf 5.4.70+-1602335159
2020-11-01 17:32:22 status installed linux-image-bcm2836:armhf 5.4.72+-1603847162
2020-11-01 17:32:23 status half-installed xbian-package-xbmc:armhf 18.8-1596947592
2020-11-01 17:33:01 status installed xbian-package-config-xbmc:armhf 20190622-0
2020-11-01 17:33:15 status installed xbian-package-initramfs-tools:armhf 20200507-0
2020-11-01 17:33:15 status installed xbian-package-xbmc:armhf 18.9-1603843570

I have an "half installed" inux-image-bcm2836 ? I Google it but did not found anything relevant about this package.
The OS runs perfectly AFAIK. Its only KODI that random restarts (last time was running for 4 days then restarted in the middle of playing a file.... totally random and yes it also happened during playback of mp3 and IPTV streams.)

Also when i run apt-get -f :

Terminal

sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

No errors (?).

Any ideas?

Thanks you.

[Nachteule]

Perhaps power issues?

[Exnor]

(6th Nov, 2020 08:41 AM)Nachteule Wrote:  Perhaps power issues?

If it was a power issue wouldn't that also "crash" the OS?

I use a 3.5A psu, and i did not notice any crashes or errors besides this Kodi behaviour... I can test with another psu.

Isn't there any way to log Kodi behaviour like a crash report?

Thanks.

[Nachteule]

(6th Nov, 2020 10:22 AM)Exnor Wrote:  

(6th Nov, 2020 08:41 AM)Nachteule Wrote:  Perhaps power issues?

If it was a power issue wouldn't that also "crash" the OS?

I use a 3.5A psu, and i did not notice any crashes or errors besides this Kodi behaviour... I can test with another psu.

Isn't there any way to log Kodi behaviour like a crash report?

Thanks.

1) You can also look into file /var/log/upstart/xbmc.log if there is a segfault or whatever
2) you can start Kodi with fresh profile to see if there are any settings/addons that causing the issue

[Exnor]

(7th Nov, 2020 01:57 AM)Nachteule Wrote:  1) You can also look into file /var/log/upstart/xbmc.log if there is a segfault or whatever
2) you can start Kodi with fresh profile to see if there are any settings/addons that causing the issue

Ok so i checked the xbmc.log file and the last lines do not show segfaults, BUT in the middle of the last log i have this:

Terminal

Nov 06 03:56:15: smbc_read(0xb0a3c698, 65536)
Nov 06 03:56:15: --> 65536
Nov 06 03:56:15: smbc_read(0xb0a3c698, 65536)
Nov 06 03:56:15: --> 65536
Nov 06 03:56:15: smbc_read(0xb0a3c698, 65536)
Nov 06 03:56:15: --> 65536
Nov 06 03:56:15: smbc_read(0xb0a3c698, 65536)
Nov 06 03:56:15: --> 65536
Nov 06 03:56:15: smbc_read(0xb0a3c698, 65536)
Nov 06 03:56:15: --> 65536
Nov 06 03:56:15: smbc_read(0xb0a3c698, 65536)
Nov 06 03:56:15: --> 65536
Nov 06 03:56:15: smbc_read(0xb0a3c698, 65536)
Nov 06 03:56:15: --> 65536
Nov 06 03:56:15: gpuserv: vc_gpuserv_init: starting initialisation
Segmentation fault
Nov 06 03:58:59: INFO: Current debug levels:
Nov 06 03:58:59: all: 10
Nov 06 03:58:59: tdb: 10

The very last lines of that log are:

Terminal

Nov 06 06:25:09: smbc_read(0xb0156500, 65536)
Nov 06 06:25:09: --> 65536
Nov 06 06:25:09: smbc_read(0xb0156500, 65536)
Nov 06 06:25:09: --> 65536
Nov 06 06:26:43: Performing aggressive shutdown.
Nov 06 06:26:43: smbc_remove_usused_server: 0x3833168 removed.
Nov 06 06:26:43: Context 0x3765360 successfully freed
Nov 06 06:26:43: Freeing parametrics:

Logs end at that line at 06:26:43.


Still have to test with a new profile... since the restarts are so random it might take a while :/

Thank you for the help
.

[Nachteule]

Do you use Samba shares?

For me it looks like this is causing the issue (smbc_read ....)

[Exnor]

(7th Nov, 2020 04:08 AM)Nachteule Wrote:  Do you use Samba shares?

For me it looks like this is causing the issue (smbc_read ....)

Sorry, once again i only read you reply today.

Yes i do have several shares in my LAN, but i did not change any configuration before this started to happen.

Is there a way to debug if this is related to Samba shares?

This random restart also occurs during iptv streaming and when the Kodi is just idle....

[Nachteule]

(20th Nov, 2020 11:30 AM)Exnor Wrote:  

(7th Nov, 2020 04:08 AM)Nachteule Wrote:  Do you use Samba shares?

For me it looks like this is causing the issue (smbc_read ....)

Sorry, once again i only read you reply today.

Yes i do have several shares in my LAN, but i did not change any configuration before this started to happen.

You will not believe how many times I have heard that in my life

Quote:Is there a way to debug if this is related to Samba shares?

This random restart also occurs during iptv streaming and when the Kodi is just idle....

Sorry, I have no idea how to debug this, in any case, the smb errors really don't look good though

[Exnor]

(22nd Nov, 2020 03:53 AM)Nachteule Wrote:  

(20th Nov, 2020 11:30 AM)Exnor Wrote:  

(7th Nov, 2020 04:08 AM)Nachteule Wrote:  Do you use Samba shares?

For me it looks like this is causing the issue (smbc_read ....)

Sorry, once again i only read you reply today.

Yes i do have several shares in my LAN, but i did not change any configuration before this started to happen.

You will not believe how many times I have heard that in my life

Quote:Is there a way to debug if this is related to Samba shares?

This random restart also occurs during iptv streaming and when the Kodi is just idle....

Sorry, I have no idea how to debug this, in any case, the smb errors really don't look good though

I believe you. Sometimes things break without any intervention...

But no other machine in my LAN had any problems with the shares, and since it occurred after that apt upgrade i guess it is a problem on the Pi (smb client maybe?).
I will Google how to debug samba shares problems.

I will post updates here.

Thanks anyway .