[ArieS]

Hello all, 

I had to replace my router and since then I cannot start Kodi.
I have a NUC running Windows 10 and a brand new ODroid N2+ with CoreELEC.
Neither can boot. I found out the issue.
If I start with this advancedsettings.xml:

xml:
<?xml version="1.0" encoding="utf-8"?>

<advancedsettings>

    <cache>

        <buffermode>1</buffermode>

        <memorysize>139460608</memorysize>

        <readfactor>20</readfactor>

    </cache>

    <videodatabase>

        <name>MyVideos</name>

        <host>192.168.1.127</host>

        <user>kodi</user>

        <pass>kodi</pass>

        <type>mysql</type>

        <port>3306</port>

    </videodatabase>

    <video></video>

    <videolibrary>

        <importwatchedstate>true</importwatchedstate>

        <importresumepoint>true</importresumepoint>

    </videolibrary>

    <sorttokens>

        <token>Le</token>

        <token>La</token>

        <token>Les</token>

        <token>L'</token>

        <token>Un</token>

        <token>Une</token>

    </sorttokens>

</advancedsettings>

It won't start but if I remove:

xml:
<videodatabase>

    <name>MyVideos</name>

    <host>192.168.1.127</host>

    <user>kodi</user>

    <pass>kodi</pass>

    <type>mysql</type>

    <port>3306</port>

</videodatabase>

It starts with no problem but of course an empty library.

I am tech challenged so I have no idea if I need to change something in the router's config or somewhere else.
The router is a Synology RT2600ac if that helps.

Any help would be MUCH appreciated!

[Klojum]

I think <video></video> is a bit obsolete.
And <name>MyVideos</name> is also unnecessary.

The debug log (wiki) should tell us a bit more about how the mysql connection goes.

[ArieS]

Here are the last 2 lines of the log:

2020-12-08 23:01:38.184 T:3923743616   ERROR: Unable to open database: MyVideos116 [2002](Can't connect to MySQL server on '192.168.1.127' (115))
2020-12-08 23:03:49.255 T:3923743616   ERROR: Unable to open database: MyVideos115 [2002](Can't connect to MySQL server on '192.168.1.127' (115))

Full log is here: https://paste.kodi.tv/qosekuzeke.kodi

Thanks!

[DaveBlake]

The obvious question, is MySQL actually running on your server?

[Klojum]

Second question: on what device/OS is MySQL actually running?

[Jogee]

Check the basics.

Specifically that the MySQL server is reachable.  Did you try to ping it from a command prompt on your Win10 NUC?

Not all routers use the same DHCP scope.  See if the IP settings on all devices are correct.

Is your MySQL server setup for DHCP or static IP?  192.168.1.x is a usually a DHCP scope.  Unless you've set a DHCP reservation on the router for the MySQL server, it might have changed.

[ArieS]

I checked and MySQL is running.
It is installed on my main PC which is running Win7

192.168.1.127 is a Static IP 

I was also able to ping 192.168.1.127 from the NUC.

I called Synology but they just told me to start a ticket.
Here's what I did though. I created a reservation for the main PC

https://imgur.com/Vx7pESF

When I look at the DHCP Clients, I don't see ARIES-PC (192.168.1.127)
Should it be there? There doesn't seem to be an option to add it though.
I seriously don't know what I should be doing now.

[Jogee]

Are all the other IP addresses in the pic from the same 192.168.1.1xx range?

When you said the IP is static, did you mean you have it hard coded on the main PC adapter settings?

Just asking for clarity: is your main PC getting that .127 IP address?  If not, you'll have to release/renew, assuming your main PC is set to DHCP grab IP.

If you have input that .127 IP manually in the adapter settings on the main PC, I'd say set it back to DHCP, reboot, and test that DHCP reservation is working.  With the IP reservation set on the router (Synology??) there is no reason to hard code it on the main PC as the router will force it to the reserved address you created.  And depending on the router, will list it in the dhcp clients.

All that is to sort out the basics and get a good place to start from to test further.  May not necessarily fix the issue.  It does seem not Kodi related right now. 

If you didn't want to mess around with DHCP reservations, you could use an IP address from the range where DHCP isn't using.  But that would mean updating your Kodi config for the new IP and setting a static address on the network adapter in your main PC, nevermind setting all the other settings (DNS, subnet mask, gateway...) correctly.  I do this for my NAS and my network printer.

[ArieS]

Jogee, 

Thank you!
I did what you said and set back the IP to DHCP, created a reservation and after a couple of reboots, it worked!
Thank you so much for taking the time, very much appreciated! 
Repped!

[Klojum]

Thread marked solved.

[Jogee]

Glad it worked!  Enjoy!