No MySQL data being written or read?

I’ve not come across this before. I noticed tonight that the MySQL data that’s being shared with my RPis isn’t being shown or updated on my Vero. The same advancedsettings.xml file I’ve always dumped onto a clean install remains the same unchanged file, so it’s not that. That’s been working fine for the past number of years. In fact, last time I reinstalled the Vero when I downgraded everything to the latest v18 image it was definitely working fine then, I always check.

Reinstalled the Vero from scratch completely again just now as I had also noticed juddering on MKV and HEVC files and thought that might fix it, it didn’t unfortunately. And still no MySQL info showing.

All of the devices are on v18.

I’ve checked this is working correctly on a couple of the RPis and it is.

Thanks for reading.

To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.

Depending on the used skin you have to set the settings-level to standard or higher, in summary:

  • enable debug logging at settings->system->logging

  • reboot the OSMC device twice(!)

  • reproduce the issue

  • upload the log set (all configs and logs!) either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A

  • publish the provided URL from the log set upload, here

Thanks for your understanding. We hope that we can help you get up and running again shortly.

OSMC skin screenshot:

You want me to reproduce the issue of there being no MySQL DB action?

Well, I suppose I can try.

https://paste.osmc.tv/udoquhogiw

Immediately I can see:

2021-09-09 21:48:16.094 T:3960647904   ERROR: Unable to open database: xbmc_music72 [2002](Can't connect to MySQL server on '192.168.0.151' (101))

Why would that have started happening recently when it’s working on all the other RPis do you think?

Verify your mysql configuration. Maybe just restart mysql.

Are you using a static (or at least a fixed DHCP) IP for your MySQL server?

It’s working correctly for 3 other devices. I can restart the NAS and see if it suddenly starts working.

Fixed. This QNAP NAS lives outside the DHCP range, always has.

I’m giving it a reboot now, would be annoying if that’s all it was :slight_smile:

Suggest to check from the Vero the connectivity with mysql -h 192.168.0.151
Might have to install sudo apt-get install mysql-common

This is probably me being thick, but:

osmc@MediaRoom:~$ sudo apt-get update
Hit:1 http://security.debian.org buster/updates InRelease
Hit:2 http://ftp.debian.org/debian buster InRelease 
Hit:3 http://ftp.debian.org/debian buster-updates InRelease
Hit:4 http://ftp.fau.de/osmc/osmc/apt buster InRelease
Reading package lists... Done
osmc@MediaRoom:~$ sudo apt-get install mysql-common
Reading package lists... Done
Building dependency tree       
Reading state information... Done
mysql-common is already the newest version (5.8+1.0.5).
0 upgraded, 0 newly installed, 0 to remove and 84 not upgraded.
osmc@MediaRoom:~$ mysql -h 192.168.0.151
-bash: mysql: command not found

Nope it was me this time :wink:
Try

sudo apt-get install mariadb-client

1 Like

What’s the command to add a specific username and password? It’s always been xbmc

osmc@MediaRoom:~$ mysql -h 192.168.0.151
ERROR 1045 (28000): Access denied for user 'osmc'@'192.168.0.158' (using password: NO)

-u username -p password

Sorry, I’d already googled.

osmc@MediaRoom:~$ mysql --user=xbmc --password=xbmc -h 192.168.0.151 
Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MySQL connection id is 2
Server version: 5.1.73-log Source distribution

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MySQL [(none)]> 

type use xbmc_music72;
show tables;

Which is the videoDB for v18? I know I would have a newer one that’s no longer required after the downgrade.

MySQL [(none)]> use xbmc_music72;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
MySQL [xbmc_music72]> show tables;
+------------------------+
| Tables_in_xbmc_music72 |
+------------------------+
| album                  |
| album_artist           |
| album_source           |
| albumartistview        |
| albumview              |
| art                    |
| artist                 |
| artistview             |
| audiobook              |
| discography            |
| genre                  |
| infosetting            |
| path                   |
| role                   |
| song                   |
| song_artist            |
| song_genre             |
| songartistview         |
| songview               |
| source                 |
| source_path            |
| version                |
| versiontagscan         |
+------------------------+
23 rows in set (0.002 sec)

116 is the video DB for V18.

Makes sense as these were the last things viewed on a RPi.

So, we’re no further then :slight_smile:

You did the mysql command that you shared the output of from the Vero?
Did you upgrade the Vero to Kodi V19, and then try to downgrade it back to V18?