search

matthuisman / docker-kodi-headless

A headless install of kodi in a docker container
GNU General Public License v3.0
124 stars 11 forks source link

kodi errors out when looking for mysql databases: "ERROR <general>: Unable to open database:" #16

Closed littlejeem closed 1 year ago

littlejeem commented 1 year ago

This docker container has been working amazingly, can't thank you enough for the use if it.

Been happily running for a number of weeks until a recent system update. Post update kodi complains in its logs of not being able to locate databases.

Snippet is below but the lines repeat for all MyMusic & MyVideos locations searched for by kodi in the log.

ERROR <general>: Unable to open database: MyMusic82 [2003](Can't connect to MySQL server on '192.168.0.9' (111))
2022-09-06 21:31:39.359 T:328     DEBUG <general>: connect replacing configured host 192.168.0.9 with resolved host 192.168.0.9
2022-09-06 21:31:39.359 T:328     ERROR <general>: Unable to open database: MyMusic81 [2003](Can't connect to MySQL server on '192.168.0.9' (111))
2022-09-06 21:31:39.359 T:328     DEBUG <general>: connect replacing configured host 192.168.0.9 with resolved host 192.168.0.9
2022-09-06 21:31:39.359 T:328     ERROR <general>: Unable to open database: MyMusic80 [2003](Can't connect to MySQL server on '192.168.0.9' (111))
2022-09-06 21:31:39.359 T:328     DEBUG <general>: connect replacing configured host 192.168.0.9 with resolved host 192.168.0.9
2022-09-06 21:31:39.360 T:328     ERROR <general>: Unable to open database: MyMusic79 [2003](Can't connect to MySQL server on '192.168.0.9' (111))
2022-09-06 21:31:39.360 T:328     DEBUG <general>: connect replacing configured host 192.168.0.9 with resolved host 192.168.0.9
2022-09-06 21:31:39.360 T:328     ERROR <general>: Unable to open database: MyMusic78 [2003](Can't connect to MySQL server on '192.168.0.9' (111))
2022-09-06 21:31:39.360 T:328     DEBUG <general>: connect replacing configured host 192.168.0.9 with resolved host 192.168.0.9
2022-09-06 21:31:39.360 T:328     ERROR <general>: Unable to open database: MyMusic77 [2003](Can't connect to MySQL server on '192.168.0.9' (111))
2022-09-06 21:31:39.360 T:328     DEBUG <general>: connect replacing configured host 192.168.0.9 with resolved host 192.168.0.9
2022-09-06 21:31:39.360 T:328     ERROR <general>: Unable to open database: MyMusic76 [2003](Can't connect to MySQL server on '192.168.0.9' (111))

I've stopped, deleted and recreated the docker with the same result as above. This feels like a permissions issue but can't trace where in the docker container i'd need to trace it down to.

Thinking of the sequence of events, I looked at the logs of the host machine and can see this snippet:

The following packages will be REMOVED:
  galera-3 libaio1 libcgi-fast-perl libcgi-pm-perl libconfig-inifiles-perl
  libdbd-mysql-perl libdbi-perl libencode-locale-perl libfcgi-perl
  libhtml-parser-perl libhtml-tagset-perl libhtml-template-perl
  libhttp-date-perl libhttp-message-perl libio-html-perl
  liblwp-mediatypes-perl libreadline5 libterm-readkey-perl libtimedate-perl
  liburi-perl mariadb-client-10.3 mariadb-client-core-10.3 mariadb-server-10.3
  mariadb-server-core-10.3 socat
0 upgraded, 0 newly installed, 25 to remove and 0 not upgraded.

So it does look like mariadb has been removed. If this was the issue I had assumed that the mysql engine being used would be inside the docker container or does it need access to a host machine instance of a mysql server.

Any thoughts much appreciated

matthuisman commented 1 year ago

this container doesnt run a mysql database. this is a client. it needs to connect to a db elsewhere. nothing has changed in the docker container so it'll be something outside of it.

try connecting to your sql database from something else - should give you a good idea of what is happening