How to proceed after failed update?

Help and Support
1

When I updated to the latest kodi version (September?) on Monday 23rd of September 2024, Kodi ended up in a restart loop because the OOM killer killed kodi.bin :confused:

I needed a quick remedy and installed my last backup which, unfortunately, was one year ago…

That works quite well, but (at least) the youtube plugin doesn’t work anymore and anyhow, I’d like to have a newer version.

So what are my options?

  1. Is it possible to update to the August (or another version from this year) version of OSMC?
  2. Update to the current version and fight with the restart loop
  3. ???

I’d like 1. best, if that would be possible, since I’d have a working, almost current version. From there I’d create a backup and then maybe do 2.

Any suggestions?

2

I’d install an image with Kodi v20 and restore your backup; then upgrade to Kodi v21 via My OSMC.

3

That’s a bit difficult: my backup is an image of the sd-card. Easy to install with dd, but it would overwrite the the Kodi v20 image…

4

But if you took the backup of the whole SD card a year ago, it will be based on Kodi v20, so you should be able to upgrade from that, unless I didn’t understand you correctly.

5

Stupid question: I have a another raspberry with the same version that worked before the mentioned upgrade. So if I could use that one, my problem would be solved.
But: the messed up raspberry is a Pi4, the working one a Pi3 … I guess I can’t just use the image of the Pi3?

6

Yes, It’s a kodi 20.1
But if I upgrade via My OSMC now, I’ll get the version that caused the restart loop, won’t I?

7

They are different images.

8

Well – it depends what is causing the reboot loop.
If it’s an OOM issue, you could try disabling some add-ons before upgrading; if that is causing your issue. Hopefully it’s not being caused by the database upgrade process.

9

Ok, I’ll try that. After all, I still have last year’s backup :grin:
Thanks for your help!

10

Yes, it doesn’t hurt to try again.
If you are running additional services on the box you could also disable them temporarily to give Kodi more headroom.

11

I updated (via My OSMC) again, without disabling any addons, and went into the reboot loop again. So I stopped the mediacenter, added a 4GiB swapfile and started the mediacenter again. Memory consumption of kodi.bin went to ~3GiB (!) and the start took forever, but finally, it released most of the memory again (~0.7GiB).

Great, I thought, some conversion needed a lot of memory, but that’s done now - isn’t it?

After I restarted mediacenter again, it again used ~3GiB of memory :confused:

Next thing I tried: I moved the ~/.kodi/addons to ~/.kodi/addons-suspicious and created a new and empty ~/.kodi/addons, hoping that some add-on is the culprit. Unfortunately, even without any add-on, memory consumption went to ~3GiB again :frowning:

I’ve added a debug log of a startup here: https://the-grue.de/~markus/kodi.log.xz
I wasn’t able to detect anything iffy.

I can’t keep it like this: The startup takes ages and the swap file slowly breaks the SD-Card… I really hope you can help me.

Update: My video (and everything else) library is mounted via NFS. I unmounted it and restarted mediacenter: Tadaaa, normal memory consumption. Is something with the library update broken?
As soon as I mount it again and start a movie, memory consumption rises to ~3GiB again.