Kodi Community Forum

Hello,

I'm running Kodi 18.7 on two Shields, one is the 2015 Pro and the other is the 2019 Pro. I use a shared database for the library, running MariaDB 10.5.4 in a docker container (the official docker image - https://hub.docker.com/_/mariadb). The videos in the library reside on a FreeNAS server and are shared via SMB.
I had no issues until recently, I believe it was a recent update to MariaDB. Now on both Shields, the library only shows 0's instead of names for both movies and TV shows, however the resume points and watched statuses are preserved. When I try playing anything, Kodi acts as if it can't find the files (see screenshots below)

A debug log: https://paste.kodi.tv/kagudatuce.kodi
And here are the screenshots:

https://imgur.com/a/JGWJfxo

I'd like to mention that the database and SMB shares are working, and I verified this by trying with Kodi on a Windows PC, which seems to work just fine. Also, I can browse the shares with PC's running Windows and Linux, and I can also connect to the database using normal Windows/Linux clients.

(2020-06-28, 12:39)n3mur1t0r Wrote: [ -> ]A debug log:

2020-06-28 13:15:09.743 T:2952 DEBUG: MYSQL: Unknown field type: 255
2020-06-28 13:15:09.757 T:2909 DEBUG: Previous line repeats 12 times.

I'm not sure what goes on here, something seems off.
Perhaps if you can also enable the database component in the debugging section of Kodi and run a new log file, perhaps we can see some more details.

Thank you for the quick answer! Unfortunately, not much is shown when enabling database debug logging.

https://paste.kodi.tv/bozapayoqi.kodi

What I remember doing some time ago, because I ran into the problem described there, is altering the c06 column in the tvshows table to longtext instead of text. -- https://github.com/xbmc/xbmc/issues/15768
Other than that, I did no modifications.

Others have this reported the '0' values problem, they also are running MariaDB 10.5.4
It's technically not a case of "no longer accessible", but somehow the data resultsets are being warped into zeros.

It's currently being looked into.

After a (rather painless) migration to the latest MySQL, everything seems to be working. So the problem relates to the latest version of MariaDB (possibly even earlier versions as reported in the other thread) and the Android flavor of Kodi.

Perhaps if you can also enable the database component in the debugging section of Kodi and run a new log file, perhaps we can see some more details. or you can the help of professionals-
mod edit: spam removed

The issue, that seems specific to Android builds and MariaDB v10.5.4, is caused by the version of MariaDB connector currently used by Kodi, PR to fix (for v19) https://github.com/xbmc/xbmc/pull/18137 which updates the Connector software.