That would point to a addon giving issues.
Suggest to:
- Upload current debug enabled logs
- Switch to OSMC Skin (if you currently use a different one)
- Disable some addons to check if CPU goes down.
1 Like
OK,
i’ll wait for the next crash and then do that.
OK i’ve tried the log uplaoder on 2 veros that crashed today and noth come back with “Failed to retreive the uRL”… both times i’ve told it to copy them to the SD card so i can do it manually but i can’t find them anywhere on the vero…
Any ideas?
They should be in /boot/
The OOM crash was on Jan 19 22:10:14 but there is no corresponding Kodi log. So if you had a crash after the 19th at 22:10 the cause must be different than OOM.
Eurgh… Ok… i need to get the actual log uploader working… is there a log for that somewhere so i can figure out why it’s not working?
These crashes are getting to the point where the WAF is plummeting and if it doesn’t improve i may have to switch to shudder something else 
These devices are stock, there’s no shady addons, i’ve tried multiple skins… the only commonality is the MYSQL database.
All the devices that are having issues are using the same MySQL database? That would make me suspect the database. What type of system is the database hosted on? One of the Veros?
You could try creating a new MySQL database (you don’t have to delete the old one, just change your advancedsettings.xml to use a new database) and rescan your content.
If that doesn’t help you could also try just using the default SQLite style database.
For the record: I use a MySQL database and have had no problems. It’s hosted on a desktop running Linux Mint. And I have a fair amount of content and have no problems at all browsing the library on 2 different Veros.
Active Profile: Master user
Library Statistics:
Albums: 4708
Artists: 5451
Songs: 57850
Movies: 1333
Moviesets: 266
Tvshows: 446
Episodes: 21616
Musicvideos: 732
I’m highly dubious it is actually the database…
I recreate it once a year or so just to clean out the cruft.
It’s running on an Ubuntu LXC and is the latest stable MariaDB…
I’m seeing messages like this in the kodi log though which make no sense to me :
2022-01-22 21:45:06.066 T:12580 DEBUG : connect replacing configured host 192.168.2.74 with resolved host 192.168.2.74
Edit : that’s the LXC IP.
I have considered switching from mysql to soemthing like plex / emby with an addon… but it feels dirty and almost hacky to do that… i don’t need a thirdparty server running to access my library… it’s just aw waste of resources.
2022-01-22 21:45:06.066 T:12580 DEBUG : connect replacing configured host 192.168.2.74 with resolved host 192.168.2.74
It looks like .2.74 is the MySQL database. That’s a very odd message and I don’t see it in my logs.
Possibly you have a network issue? Your logs were truncated so the ifconfig part is missing.
Just how large is your library (roughly)?
MySQL database should work fine. Like I said, no issues for me and I’ve been using it for years. Never re-created the database. It’s lived through 4 or 5 Kodi version updates.
if i do have a network issue, it’s the first i’ve noticed…
My library is 250 tv shows and 2964 movies…
All content has local nfo and artwork… there’s literally no work for kodi to be doing other than caching the metadata and artwork.
i use a headless docker install to do my library scans and ember media manager to create the nfo’s and artwork…
the crashes always happen when scrolling through shows or movies… i can see it coming because i’ll scroll down and then artwork wont load and things will freeze but still respond slowly… then it’ll eventually die… sometimes i have to pull the power to get it back. other times it’ll sad face on me.
Well, the nfo files don’t matter once you’ve scanned it to the library. Once it’s in the MySQL library that’s where Kodi reads the info from.
That sounds like you are having the problem that was mentioned in #74 on this thread. An issue with the thumbs.
#74 seems to indicate this is a kodi issue and maybe 19.4 might fix it?
Possibly. I didn’t read the complete thread. But 19.4 is coming soon, so I guess you can hope it will fix the problem.
I do still wonder about the strange error in the Kodi logs about the MySQL server IP. And your problems uploading logs. I suspect there is still something else going on here.
Can you try rebooting twice and then share logs?
i am wondering if the uploading logs problem is caused by my adguard home install… i’ll switch the DNS on my clients tomorrow and see if that helps.
We’re “catching up” (joy of joys) on celebs go dating at the moment so the reboots will have to wait until tomorrow
Could that be also causing the error in the Kodi logs??? I don’t use adguard myself. Is it a network wide service?
it is network wide but only for DNS queries so an IP wouldn’t be affected.
That’s the theory. But I’m wondering. The strange error in the Kodi log looks almost like it’s seeing the IP as hostname. As a test I’d say to completely turn off adguard and see what happens.
ill set a static dns on the vero’s and see how it goes.