(2015-05-14, 09:58)MuzzleAU Wrote: (2015-05-13, 03:26)Richie Wrote: So I've been monitoring the headless Kodi client development for sometime, as it's exactly what I want. I've got a Synology NAS which, just yesterday, has now had it's firmware updated to DSM 5.2. Nothing huge, other than the fact it now supports docker.
Loaded up Kodi headless Helix (sparklyballz version) and it seemed to load in, create the image and container, but can't for the love of me how to access the web gui.
Does anyone have any advice they can give me to get this working?
I've got it working on my Synology DS1511 using that version (BTW nice job Sparklyballz).
There's a few things you need to set up on the Synology Docker UI. Click the 'Edit' button on the 'Container' tab and...
1. On the 'Basic Options' tab, click '+' to add a port mapping. The default web port is 8080, so I made a mapping from local port 8008 to container port 8080 to avoid any conflicts with my NAS.
2. On the 'Environment Variables' tab, add the login settings for your MySQL database; these variables are named 'MYSQLip', 'MYSQLport', 'MYSQLuser', 'MYSQLpass'.
3. On the 'Volume' tab, you might want to add a mount for the Thumbnails if you're using a shared folder across all your PCs.
Incidentally, the default login / pass to the web interface is 'xbmc'/'xbmc'.
This is likely enough if you're using the default database names (eg. MyVideo##). Unfortunately in my case, I have non-standard names as a result of following this guide, and had to SSH into the container and make manual adjustments.
What kind of manual adjustments did you make? I just finished adding docker to synology. I followed your steps, and I believe when I set my config up, I used that same exact guide.
I have local port set to 8116, and the container port to 8080 (since that what you said the default was) and configured the mySQL enviornment variables. I then ran it, and it seems to be running just fine.
When I go to
http://192.168.1.100:8116/ in a browser I see connection refused. But I can SSH in just fine. I don't know why the web interface isn't working? seems like there should be one.
I went through and found the full directory using find, and copied the sources.xml and passwords.xml in through SSH in to the /opt/kodi-server/share/kodi/portable_data/userdata (there was already advancedsettings.xml) I chowned them and gave it the same permissions as the file there.
When I go to sickbeard > notifications > kodi and try to test the server using xbmc/xbmc or kodi/kodi as passwords and 192.168.1.100:8116 I get "Test KODI notice failed to 192.168.1.150:8116"
Really looking for help, I'm very interested in getting this up and running.
Thanks, all. So far this is the work of dreams
Edit: Further it occurred me that I had installed lighthttpd a long time ago to set up ruTorrent at port 777 (
http://forum.synology.com/wiki/index.php...rent_HowTo).
When I go to control panel > web services, that is checked because of phpMyAdmin. I assume that's running on port 8080, but when I go to that, I get a refused error, of course. Sickbeard runs just fine though, not sure on which server?
Am I just doing something wrong? I tried changing 8080 to 777, 80, 8000 and nothing changed, still the same 127 error.
This is what's in my log when I start it on docker.
2015-06-29 23:26:40,190 CRIT Supervisor running as root (no user in config file)
stdout
23:26:40
2015-06-29 23:26:40,190 WARN Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
stdout
23:26:40
2015-06-29 23:26:40,332 INFO RPC interface 'supervisor' initialized
stdout
23:26:40
2015-06-29 23:26:40,333 WARN cElementTree not installed, using slower XML parser for XML-RPC
stdout
23:26:40
2015-06-29 23:26:40,333 CRIT Server 'unix_http_server' running without any HTTP authentication checking
stdout
23:26:40
2015-06-29 23:26:40,334 INFO supervisord started with pid 1
stdout
23:26:41
2015-06-29 23:26:41,348 INFO spawned: 'kodi-server' with pid 9
stdout
23:26:41
2015-06-29 23:26:41,395 INFO exited: kodi-server (exit status 127; not expected)
stdout
23:26:42
2015-06-29 23:26:42,400 INFO spawned: 'kodi-server' with pid 10
stdout
23:26:42
2015-06-29 23:26:42,417 INFO exited: kodi-server (exit status 127; not expected)]
Digging deep into this 127 error... I went to the supervisord file to get the run script it was using, which got me stuck here when I try and run it manually?
root@kodi:/# /opt/kodi-server/lib/kodi/kodi.bin --nolirc --headless -p -u root /opt/kodi-server/lib/kodi/kodi.bin: error while loading shared libraries: libSDL_image-1.2.so.0: cannot open shared object file: No such file or directory
Help, anyone?
I configured so much of this stuff a long time ago, something tells me it might be easier just to try and do a system restore and start over, or something?
Downloaded some stuff with apt-get...
and got further along to ...
root@kodi:/# /opt/kodi-server/lib/kodi/kodi.bin --nolirc --headless -p -u root /opt/kodi-server/lib/kodi/kodi.bin
Can't open display
Segmentation fault
root@kodi:/#
Okay. seems to be running fine from the web interface now.
Except the Update/Clean... nothing seems to work. When I click TV/Movies/Music nothing shows up.. just loads?
However, Sickbeard apparently can send it notifications.
When I click on Master User :: Connection to Server lost... looks like a crash?
Nevermind. Apparently, I had to use the advancedsettings.xml it created, then apt-get install nano to edit it, and then after i put my stuff in it worked fine? weird but happy now