I had to downgrade from 9.2.4.2 to 9.2.3 because of black screen after the reboot. Fortunately SSH was available. My box is Minix U1 Neo. After digging in logs I discovered the following difference in log files. I was able to connect to my central MariaDB on the correct port so network is not an issue.
CoreELEC-Amlogic.arm-9.2.3 - working
2020-08-23 13:24:31.552 T:4024427392 NOTICE: Running database version Addons27
2020-08-23 13:24:31.566 T:4024427392 NOTICE: Running database version ViewModes6
2020-08-23 13:24:31.594 T:4024427392 NOTICE: Running database version Textures13
2020-08-23 13:24:31.597 T:4024427392 NOTICE: MYSQL: Connected to version 10.5.3-MariaDB-1:10.5.3+maria~bionic
2020-08-23 13:24:31.606 T:4024427392 NOTICE: Running database version MyMusic72
2020-08-23 13:24:31.618 T:4024427392 NOTICE: Running database version MyVideos116
2020-08-23 13:24:31.628 T:4024427392 NOTICE: Running database version TV32
2020-08-23 13:24:32.372 T:4024427392 NOTICE: Running database version Epg12
CoreELEC-Amlogic.arm-9.2.4.2.tar
2020-08-23 15:31:23.174 T:4024427392 NOTICE: Running database version Addons27
2020-08-23 15:31:23.180 T:4024427392 NOTICE: Running database version ViewModes6
2020-08-23 15:31:23.210 T:4024427392 NOTICE: Running database version Textures13
2020-08-23 15:31:23.214 T:4024427392 NOTICE: MYSQL: Connected to version 10.5.3-MariaDB-1:10.5.3+maria~bionic
2020-08-23 15:31:23.223 T:4024427392 ERROR: SQL: [MyMusic72] An unknown error occurred
Query: SELECT idVersion FROM version
2020-08-23 15:31:23.223 T:4024427392 ERROR: Process error processing job
Everything reverted to normal after I downgraded to CoreELEC-Amlogic.arm-9.2.3. Don’t you have any advice where is the problem? I’ve already upgraded my Win10-based Kodi to 18.8 (using the same central MySQL) and it’s working fine. It seems like an isolated problem related to CoreELEC.
Not really. I use MariaDB 10.5.3, not 10.5.5. I didn’t change any compression. And mainly everything works fine after the downgrade to the previous CoreELEC version so I think it’s not possible my databases have been damaged.
Why? Does not the older version 9.2.3 launch the same command?
I’ve already tried to delete both databases and install 9.2.4.2 from the scratch, modify advancedsettings.xml etc. And this version does not create new, empty databases.
9.2.3 created databases immediately after the first reboot once it was installed from the scratch too.
I am afraid there is something wrong with mysql client in CoreELEC 9.2.4.2 for arm. As you can see I am able to query the remote database from non-default mysql client installed on 9.2.4.2.
And as expected I can see the following error in kodi.log (I’ve also tried to configure waitfornetwork with the max. 30 secs):
2020-08-23 18:15:23.211 T:4092341680 NOTICE: WaitForNet: Waiting for a network interface to come up (Timeout: 30 s)
2020-08-23 18:15:23.211 T:4092341680 NOTICE: WaitForNet: A network interface is up after waiting 0 ms
2020-08-23 18:15:23.213 T:4023378816 NOTICE: Running database version Addons27
2020-08-23 18:15:23.218 T:4023378816 NOTICE: Running database version ViewModes6
2020-08-23 18:15:23.247 T:4023378816 NOTICE: Running database version Textures13
2020-08-23 18:15:23.251 T:4023378816 NOTICE: MYSQL: Connected to version 10.5.3-MariaDB-1:10.5.3+maria~bionic
2020-08-23 18:15:23.260 T:4023378816 ERROR: SQL: [MyMusic72] An unknown error occurred
Query: SELECT idVersion FROM version
2020-08-23 18:15:23.260 T:4023378816 ERROR: Process error processing job
I can confirm CoreELEC-Amlogic.arm-9.2-nightly_20200823.tar solved the issue with unaccessible MariaDB databases. All working fine now.
2020-08-24 20:17:29.324 T:4090851312 NOTICE: WaitForNet: Waiting for a network interface to come up (Timeout: 30 s)
2020-08-24 20:17:29.324 T:4090851312 NOTICE: WaitForNet: A network interface is up after waiting 0 ms
2020-08-24 20:17:29.327 T:4022330240 NOTICE: Running database version Addons27
2020-08-24 20:17:29.333 T:4022330240 NOTICE: Running database version ViewModes6
2020-08-24 20:17:29.365 T:4022330240 NOTICE: Running database version Textures13
2020-08-24 20:17:29.369 T:4022330240 NOTICE: MYSQL: Connected to version 10.5.3-MariaDB-1:10.5.3+maria~bionic
2020-08-24 20:17:29.379 T:4022330240 NOTICE: Running database version MyMusic72
2020-08-24 20:17:29.390 T:4022330240 NOTICE: Running database version MyVideos116
2020-08-24 20:17:29.399 T:4022330240 NOTICE: Running database version TV32
2020-08-24 20:17:30.223 T:4022330240 NOTICE: Running database version Epg12
Fix confirmed too. I had the same problem too (kodi throwing error in that SELECT idVersion). Server is MariaDB 10.5.5 on Win 10, which I just migrated from MySQL 5.7