2013-12-01, 00:57
A workaround for the SQL issue, a common issue it turns out, is to place a sleep command in the autostart.sh file. This isn't optimal and this doesn't get run on a restart but it DOES solve the problem for me and hopefully others. Looking at journalctl it looks like I might even be able to cut the sleep down further but for now 10 seconds isn't bad. XBMC logs show no problems connecting to my SQL server now. I strongly suspect any i3 NUC user (and likely i5) who wishes to use an SQL server as I am will run into this. there may be a more elegant solution but for now this is working for me and mirrors what others have done.
I've simply added the following to my autostart.sh:
Update: Well I'm learning more about Openelec! If you go into system, Openelec, Network, then scroll that dialog DOWN to unhide an Advanced Network Setting named "Start XBMC after network" or somesuch you will have found the secret to solving this. You can set the max wait time too! I guess this was common enough to get built into the Openelec software
I've simply added the following to my autostart.sh:
Code:
#attempt to fix SQL connection issue
sleep 10
Update: Well I'm learning more about Openelec! If you go into system, Openelec, Network, then scroll that dialog DOWN to unhide an Advanced Network Setting named "Start XBMC after network" or somesuch you will have found the secret to solving this. You can set the max wait time too! I guess this was common enough to get built into the Openelec software