[matthuisman]

@bossanova808
how did you get on?

[bossanova808]

I think maybe you mean @denogginizer ?

[denogginizer]

@bossanova808
how did you get on?

Apologies for the delayed response. It's been a busy week here.
kodi.log can be found here: https://paste.kodi.tv/itudofodig.kodi

I disabled all addons by renaming the folder (after stopping the headless docker container), and one of the "info" tags in the log says: "Essential mysql database information is missing. Require at least host, user and pass defined." so, I added that to the "advancedsettings.xml" (as you can see in the log). I was able to start Kodi Headless and it did create the MyMusic83 database, but when I click on Music in Kodi it just crashes.
Here is the kodi.log from the Nvidia Shield that crashed: https://paste.kodi.tv/gupamapoxi.kodi

I'm ok with just dumping the music database and starting over if that is a good option. What is the best way to do that?

Thank you for all the help so far!

[matthuisman]

2024-05-11 16:26:21.051 T:32624 error <general>: Can't open the database MyMusic83 as it is a NEWER version than what we were expecting?
2024-05-11 16:26:21.057 T:32624 info <general>: Old database found - updating from version 82 to 83
2024-05-11 16:26:21.059 T:32624 error <general>: SQL: Can't create database for copy: 'MyMusic82' (1007)
2024-05-11 16:26:21.061 T:32624 error <general>: Unable to copy old database MyMusic82 to new version MyMusic83

Your getting that in both headless and client.
1007 seems to say that DB already exists
So maybe it created and failed and now cant try again.

If I was you, I'd login to mysql db and delete the MyMusic83 db
then restart and let it try to migrate 82 -> 83 again

[denogginizer]

2024-05-11 16:26:21.051 T:32624 error <general>: Can't open the database MyMusic83 as it is a NEWER version than what we were expecting?
2024-05-11 16:26:21.057 T:32624 info <general>: Old database found - updating from version 82 to 83
2024-05-11 16:26:21.059 T:32624 error <general>: SQL: Can't create database for copy: 'MyMusic82' (1007)
2024-05-11 16:26:21.061 T:32624 error <general>: Unable to copy old database MyMusic82 to new version MyMusic83

Your getting that in both headless and client.
1007 seems to say that DB already exists
So maybe it created and failed and now cant try again.

If I was you, I'd login to mysql db and delete the MyMusic83 db
then restart and let it try to migrate 82 -> 83 again

Thank you so much for all your help. I think at this point, I'm just going to start fresh. Maybe my db was bad before the upgrade?

These were my last steps:

- Stopped kodi-headless container
- renamed "addons" folder to "addons-bak"
- Via phpMyAdmin deleted the MyMusic83 database
- Started kodi-headless container
- MyMusic83 reappears and is filled with music data
- Kodi (on Nvidia Shield) crashes when attempting to access music library and Yatse shows it as empty.

So, I think it's probably time to start over on the database. Thank you again for the help

[matthuisman]

I suspect something isn't migrating correctly.
Starting fresh with latest db and scanning in is probably the best way.

[philamp]

Hello,

Thanks for your docker image.

Do you have the corresponding Dockerfile ?

Did you have to modify the Leia headless.patch to make it work on Omega ? if so can you provide it as well

I would like to integrate Kodi-headless in another docker image that I'm building

Thanks for your help

[matthuisman]

its all on the github. change the branch to whatever kodi version to see all the files

[philamp]

Thanks a lot 🙏 I overlooked the branch change, thanks for the clarification and your work on that docker image 🙂

[philamp]

It seems that most of what I want to configure is possible through xml or web interface. But for some odd reason, the scrapper configuration is only customizable through the conventionnal UI. Anyway I think that a simple mysql INSERT INTO in the path table (with right values) will do the trick.... is it the right or only way to do it ? thanks for your help, btw your "recently added refresh" add-on is awesome !

[matthuisman]

youd need to ask the kodi guys. I believe set content only possible on a full client

[philamp]

Ok I see. The workaround is to set the SQL DB with a remote full kodi client first. this is what I want to avoid to have an automatized "devops style" deployment for home

[matthuisman]

again, its Kodi. If they havnt added "set content" to web gui / JSON API - there isn't much I can do.
You could find the rows it creates and have your own query to insert them. But youd need to keep the DB table name upto date etc.
Its still possible - but youll need to figure out the mucking around

[john_matrix]

Hello,
Thanks for your Kodi headless docker image.

Can I use it for a shared Kodi library location?
Indeed, I am thinking about a Kodi "master" with external library installed that "push" the library to your Docker container and other Kodi gets the DB from the Docker container.
But maybe I am wrong and this is not the goal of it?

I have deployed a docker-compose version with MariaDB container and the issue I encounter is there are some missing settings: http control are not where they are in a regular Kodi installation
Kodi-Headless:


Regular Kodi (on Windows):


In this situation, I cannot connect from the regular Kodi to the Docker container.

Is this normal?

Many thanks in advance!

[matthuisman]

I don't understand sorry. It's just standard Linux Kodi running without a GUI. Nothing more, nothing less.