Posts by PeteAklNZ

    I am running version 12.0.2 architecture RK3399.aarch64 on a X99 tv box purchased from AliExpress.

    I seeking input on an issue I have: I have set a timezone in Kodi's Settings/Interface to Pacific/Auckland but this does not seem to be reflected in the underlying Linux OS - ie specifically for cron jobs.

    Here is further info:

    Contents of guisettings.xml:
    <setting id="locale.language" default="true">resource.language.en_gb</setting>
    <setting id="locale.charset" default="true">DEFAULT</setting>
    <setting id="locale.keyboardlayouts" default="true">English QWERTY</setting>
    <setting id="locale.activekeyboardlayout" default="true">English QWERTY</setting>
    <setting id="locale.country">Australia (24h)</setting>
    <setting id="locale.timezonecountry">New Zealand</setting>
    <setting id="locale.timezone">Pacific/Auckland</setting>
    <setting id="locale.shortdateformat" default="true">regional</setting>
    <setting id="locale.longdateformat" default="true">regional</setting>
    <setting id="locale.timeformat" default="true">regional</setting>
    <setting id="locale.use24hourclock" default="true">regional</setting>
    <setting id="locale.temperatureunit" default="true">regional</setting>
    <setting id="locale.speedunit" default="true">regional</setting>

    From SSH session:
    X99:~ # date
    Sun Mar 23 21:14:13 UTC 2025

    Local time was 13 hours later than this

    Any help on this issue would be much appreciated - so thanks in advance.

    Peter

    Thanks, using 127.0.0.1 instead of localhost does fix the problem with opening the mariadb on the same system

    However, accessing a mariadb on a remote system is still an issue. I've increased the wait to 60 seconds, and still no database connection at boot time. It is evident that the system is not waiting for the time to elapse before the user interface is shown with no database connected. Irrespective of the parameter, the user interface shows in <10 seconds. When connected via ssh, I repeatedly systemctl restart mariadb and systemctl restart kodi and eventually the database does connect; taking between 15 and 30 attempts. A work around but hardly optimal!

    But as you suggested, I tried again to reboot with advancedsettings.xml pointing to the remote server, then waited for quite some time (like hours, I was interrupted by other things) and then did "systemctl restart kodi", and the remote database is connected properly. So thanks for your solution. I'll experiment with increasing the wait for network setting to achieve a reliable connection when I reboot.

    I have setup LibreELEC 11.03.00 on a Hugsun X99

    I attempted to use the same advancedsettings.xml that I have used from other devices (Raspberry Pi 4 using Pi's OS and Kodi 19.4, and generic Amlogic devices using CoreELEC and Kodo 20.2) to access by back-end MariaDB database. This did not work; an extract of kodi.log is attached, named "kodi log extract remote.txt".

    I then installed the MariaDB sql server addon, modified advancedsettings.xml accordingly and attempted to connect to it. Again, it did notwork; an extract of kodi.log is attached, named "kodi log extract local.txt"

    I would appreciate guidance from anyone who might know what is the problem, and how I might fix it.

    Many thanks, Peter