• 1
  • 38
  • 39
  • 40(current)
  • 41
  • 42
  • 58
xbmc minified as a server?
(2014-03-31, 18:59)sankaman82 Wrote:
(2014-03-31, 15:08)sankaman82 Wrote:
(2014-03-30, 12:43)wernerb Wrote: If you are having trouble compiling, use the pre-compiled version with Docker that I posted a few posts back. If only you need to update the library that is the quickest way to get there.

ok, so,
after having had some trouble to compile xbmc-server, not being satisfied with Minidlna (for one or another reason, he's not taking the .nfo's and fanart into consideration), and thinking of the Ubuntu's next big release, I'll follow your advice and go for the docker but it will be with the bridge setting since it should be working serving the xbmc clients continuously Wink

Thanks for the work already performed and you'll probably hear from me very soon.

Hi wernerb,
guess what? I got a problem...
after having installed docker and prepared the conf files, I went for the:
Code:
$ sudo docker run -d --networking=false \
  -v /directory/with/xbmcdata:/opt/xbmc-server/portable_data \
  --lxc-conf="lxc.network.type = veth" \
  --lxc-conf="lxc.network.flags = up" \
  --lxc-conf="lxc.network.link = br0" \
  --lxc-conf="lxc.network.ipv4 = 192.168.1.49" \
  --lxc-conf="lxc.network.ipv4.gateway=192.168.1.1" \
  wernerb/docker-xbmc-server
(of course with my settings)

and after pulling the complete repository, I got the error below:
Code:
2014/03/31 18:36:19 Error: Cannot start container 9b0bf3ca19bdebbbe897fffe76d79ec6614db3fba865f44a427dc00ce61366c0: lxc.network.type = veth is not supported by the native driver

Thus, I suppose this is linked to my poor ethernet card...?
Anyhow, first, I'll fetch the wife and make some cooking stuffs and hopefully, she'll be so kind to give me some more time with the container's story...

If you have any suggestions, please do not hesitate.

Fortunately I anticipated your problem Smile Look at the end, at the FAQ concerning veth problems Smile
See: https://github.com/wernerb/docker-xbmc-server

This is because you are running the latest docker which has created its own lxc driver without implementing all its features.

(2014-03-31, 18:13)3agle3ye Wrote:
(2014-03-17, 12:51)wernerb Wrote: I created a docker container that contains xbmcLibraryScan and xbmc headless for frodo 12.3 (as of yesterday).

Best of all you do not need to compile it yourself anymore.

Steps to undertake:
1. Install docker for your linux distro
2. download https://github.com/wernerb/docker-xbmc-s...ttings.xml and adjust the mysql settings.
3. set up a folder somewhere you would like to have the xbmc library stored. for example: mkdir -p /home/$(whoami)/.xbmc/userdata and put advancedsettings.xml there.

You are basicly done! The following command will download the container and run the xbmcVideoLibraryScan!
Code:
sudo docker run -v /home/$(whoami)/.xbmc:/opt/xbmc-server/portable_data --entrypoint=/opt/xbmc-server/xbmcVideoLibraryScan wernerb/docker-xbmc-server:latest --no-test --nolirc -p

Subsequent runs will obviously not re-download the container Smile

* Change /home/$(whoami)/.xbmc to the folder you use, this can be anywhere you'd like. But remember that advancedsettings.xml is needed to run correctly.

If you guys like to comment or to contribute (make a branch supporting gotham) do it at my github repository: https://github.com/wernerb/docker-xbmc-server

Tell me what you guys think Wink

Just tried the Docker solution on openSuSE 13.1. It's working ... however the advancesettings.xml is full of errors.
Could you please take a look into that wernerb?

I'am getting errors like:
Code:
15:53:53 T:139711820830592   ERROR: Error loading special://profile/advancedsettings.xml, Line 31
                                            Error reading Attributes.

Code:
16:02:59 T:139769716037504   ERROR: Error loading special://profile/advancedsettings.xml, Line 60
                                            Error reading end tag.

already tried to fix it myself ... but the formatting of that xml is horrible.
Looking forward to hear from you Wink

EDIT: forgot to say that i took the "Frodo" one!

Hi! That's weird, its working fine with that file at my end (and I haven't heard any problems thus far)
Maybe something went wrong during copy-paste? Did you try downloading the raw file at:
https://github.com/wernerb/docker-xbmc-s...ttings.xml and using it directly?
I've taken a look but there is nothing wrong with the advancedsettings.xml (even pulled it through an xml validator to be sure)

Also note that the instructions you quoted are old, see https://github.com/wernerb/docker-xbmc-server for full and better instructions!
Reply
(2014-04-01, 12:19)wernerb Wrote: Hi! That's weird, its working fine with that file at my end (and I haven't heard any problems thus far)
Maybe something went wrong during copy-paste? Did you try downloading the raw file at:
https://github.com/wernerb/docker-xbmc-s...ttings.xml and using it directly?
I've taken a look but there is nothing wrong with the advancedsettings.xml (even pulled it through an xml validator to be sure)

Also note that the instructions you quoted are old, see https://github.com/wernerb/docker-xbmc-server for full and better instructions!

Well, that explains everything Big Grin
The xml linked on the old instructions looks completely different and has about 600 lines.
The xml you linked is running fine now!
Reply
(2014-04-01, 17:41)3agle3ye Wrote:
(2014-04-01, 12:19)wernerb Wrote: Hi! That's weird, its working fine with that file at my end (and I haven't heard any problems thus far)
Maybe something went wrong during copy-paste? Did you try downloading the raw file at:
https://github.com/wernerb/docker-xbmc-s...ttings.xml and using it directly?
I've taken a look but there is nothing wrong with the advancedsettings.xml (even pulled it through an xml validator to be sure)

Also note that the instructions you quoted are old, see https://github.com/wernerb/docker-xbmc-server for full and better instructions!

Well, that explains everything Big Grin
The xml linked on the old instructions looks completely different and has about 600 lines.
The xml you linked is running fine now!

Glad to hear it ! Can you point me to the old xml instructions? I can't recall ever making a 600 line xml, and i'd rather not have people running into the same problem!

Nice to know that its working at your end. Also, i'm very interested in feedback from people running the upnp server! Its working great here (never a crash, uptime is a month), but before I made some patches (they are included with the docker container) I got lots of crashes. Thanks!
Reply
(2014-04-01, 17:57)wernerb Wrote: Glad to hear it ! Can you point me to the old xml instructions? I can't recall ever making a 600 line xml, and i'd rather not have people running into the same problem!

Nice to know that its working at your end. Also, i'm very interested in feedback from people running the upnp server! Its working great here (never a crash, uptime is a month), but before I made some patches (they are included with the docker container) I got lots of crashes. Thanks!

The point is: https://github.com/wernerb/docker-xbmc-s...ttings.xml is shown normal on github.

but as soon as i wget this file with excactly the same URL i get a file with 600 lines ... for whatever reason.

Code:
xbmc@gmdetroimp01sql:~> cat advancedsettings.xml | wc -l
621
Reply
(2014-04-01, 19:09)3agle3ye Wrote:
(2014-04-01, 17:57)wernerb Wrote: Glad to hear it ! Can you point me to the old xml instructions? I can't recall ever making a 600 line xml, and i'd rather not have people running into the same problem!

Nice to know that its working at your end. Also, i'm very interested in feedback from people running the upnp server! Its working great here (never a crash, uptime is a month), but before I made some patches (they are included with the docker container) I got lots of crashes. Thanks!

The point is: https://github.com/wernerb/docker-xbmc-s...ttings.xml is shown normal on github.

but as soon as i wget this file with excactly the same URL i get a file with 600 lines ... for whatever reason.

Code:
xbmc@gmdetroimp01sql:~> cat advancedsettings.xml | wc -l
621

Ahh. Yeah that file is an github preview of the advancedsetings.xml. So if you wget it, you get an html Smile If you go there and select "raw" you get the following link: https://github.com/wernerb/docker-xbmc-s...ttings.xml

I will update the instructions
Reply
Hi Wernerb,
Following post #586,
I succeed in the installation of the container, the daemon is working but unfortunately, I'm having issues with the bridging and I guess I'm not as clever as I would like to Wink

Thus, I'm trying to remove all of it and will start from scratch.
I'll come back to you when I'll succeed (or when you can help me because for the moment, it's not really that clear to me Wink )
Thanks anyhow,
Reply
Don't give up! you are very close Smile

Did you give http://blog.ostanin.org/2013/09/14/plex-...in-docker/ in combination with https://help.ubuntu.com/community/KVM/Networking a try?
Btw Docker is under heavy development and it will be (hopefully soon) be possible to launch containers without the bridge necessary, as a pull request is waiting exception that allows a container to work on the host network, rather than the virtualized docker bridge network Smile

Also you can always use this container to update your xbmc mysql library at least, that does not require a bridge, and is what most people in this thread want Smile
Reply
I've compiled xbmc-server Frodo (12.3) minified with NFS support.The web service is up and everyhing looks good.
I share my library via NFS, and all my clients can access it fine.

Now when I try to rescan the DB from the xbmc-server it complains about not being able to connect to NFS. Obviously I have modified my /etc/exports to allow connections from the box itself. I am able to mount the exports locally.
But xbmc-server is only able to connect via NFS after I restart nfs-kernel-server. When I restart xbmc-server I always haave to restart nfs-kernel-server, otherwise it won't work.
Any ideas why this is happening?


edit: silly me, of course I needed to add "insecure" to /etc/exports; exportfs -ra; now it works well out of the box.
I don't know why it was able to connect once after the nfs-kernel-server was restarted. Maybe a NFS bug. *shrug*
Reply
(2014-03-30, 19:30)osnabrugge Wrote: I would also like to see a Synology App created for an XBMC server. In the meantime, is it possible to install this headless version from the shell of a Synology NAS?

Possibly with this, www.synocommunity.com/help/debian-chroot,

http://www.synocommunity.com/faq#addSource
Reply
(2014-04-02, 19:16)fma965 Wrote:
(2014-03-30, 19:30)osnabrugge Wrote: I would also like to see a Synology App created for an XBMC server. In the meantime, is it possible to install this headless version from the shell of a Synology NAS?

Possibly with this, www.synocommunity.com/help/debian-chroot,

http://www.synocommunity.com/faq#addSource

That sounds interesting but i doubt my DS211 is powerful enough for running it.
Reply
I'm currently trying to set up an xbmc upnp server on my nas, to be able to stream my media library to a couple of openelec installations on rasperry pi.
I can't get it to work though.
I tried setting up your docker container and everything went fine except the network bridge. Also, I would have had to either set up another container with mysql inside or configure vmac for the host system, which i simply don't like.
So what I ended up doing, is extract the build and compile configuration from the Dockerfile and compile xbmc-server on the host system myself. It does run. But somehow the upnp doesn't work. None of my xbmc clients, be it on openelec using xbmc 12.2 or even on my windows system with xbmc 12.3.
Since I'm using ubuntu 14.04LTS as a host system I'm wondering if that may be the cause of my problems. I did have to apply an additional patch to the code since I have samba 4 running, but that only changes header includes to the samba4 header files and shouldn't affect the upnp imho.
I have teporarily installed a desktop env and tried out the xbmc version that comes with ubuntu and that works. I don't want a full desktop env running on the nas though.
I have disabled the ubuntu firewall, so that shouldn't be the problem either. The xbmc server debug log tells me that the upnp server is being started. Also, netcat tells me that the upnp port is open.
Any suggestions what the problem could be? I've been trying to get this to run for the better part of the week now.

Thanks in advance!
Reply
(2014-04-27, 02:34)eth8505 Wrote: I'm currently trying to set up an xbmc upnp server on my nas, to be able to stream my media library to a couple of openelec installations on rasperry pi.
I can't get it to work though.
I tried setting up your docker container and everything went fine except the network bridge. Also, I would have had to either set up another container with mysql inside or configure vmac for the host system, which i simply don't like.
Hi! Yeah setting up the bridge can be difficult (or just not possible). The bridge is only necessary to make sure the docker container runs on your host machine's network..
Ubuntu 14.04 should be relatively straight forward though to set up a bridge? But don't fret, docker is working on supporting host-only networking at https://github.com/dotcloud/docker/pull/4441! It will probably be merged soon, and the next docker version will support it.
If it comes through I will change the instructions to reflect the latest docker version!

(2014-04-27, 02:34)eth8505 Wrote: So what I ended up doing, is extract the build and compile configuration from the Dockerfile and compile xbmc-server on the host system myself. It does run. But somehow the upnp doesn't work. None of my xbmc clients, be it on openelec using xbmc 12.2 or even on my windows system with xbmc 12.3.
Since I'm using ubuntu 14.04LTS as a host system I'm wondering if that may be the cause of my problems. I did have to apply an additional patch to the code since I have samba 4 running, but that only changes header includes to the samba4 header files and shouldn't affect the upnp imho.
I have teporarily installed a desktop env and tried out the xbmc version that comes with ubuntu and that works. I don't want a full desktop env running on the nas though.
I have disabled the ubuntu firewall, so that shouldn't be the problem either. The xbmc server debug log tells me that the upnp server is being started. Also, netcat tells me that the upnp port is open.
Any suggestions what the problem could be? I've been trying to get this to run for the better part of the week now.
Well the Dockerfile instructions are meant for ubuntu 12.10. I haven't tested/tried using it on 14.04. I don't think its samba4.. I assume you are using the advancedsettings.xml I supplied? You can try to copy the configuration your desktop xbmc made with the headless xbmc to make sure there's nothing wrong with configuration. Not seeing anything on the clients makes me think its a networking/permission/firewall issue to multicast, but its weird your desktop version did work. Try running it as root to see what happens. Also post your logs somewhere, so I can compare it with what I have.

About a container with mysql, there is a container here: [url]https://github.com/ryan-robeson/xbmc-mysql[\url] that runs mysql as a container specifically for xbmc. You don't have to use docker for mysql, just point it to the correct database.
Reply
(2014-04-27, 11:20)wernerb Wrote: Ubuntu 14.04 should be relatively straight forward though to set up a bridge? But don't fret, docker is working on supporting host-only networking at https://github.com/dotcloud/docker/pull/4441! It will probably be merged soon, and the next docker version will support it.
If it comes through I will change the instructions to reflect the latest docker version!
Yeah, I've seen that around. Waiting for that, too. Just couldn't get the bridge to work. But since I really need the xbmc to be on the hosts network, it seems I have to wait for the new docker version.

(2014-04-27, 11:20)wernerb Wrote: Well the Dockerfile instructions are meant for ubuntu 12.10. I haven't tested/tried using it on 14.04. I don't think its samba4.. I assume you are using the advancedsettings.xml I supplied? You can try to copy the configuration your desktop xbmc made with the headless xbmc to make sure there's nothing wrong with configuration. Not seeing anything on the clients makes me think its a networking/permission/firewall issue to multicast, but its weird your desktop version did work. Try running it as root to see what happens. Also post your logs somewhere, so I can compare it with what I have.
It compiled alright... on 14.04 ;-) I'm using your docker container config entirely. Haven't tried the desktop version yet, but then again there isn't anything in the usersettings.xml except the enable flags for upnp and renderer. Port configuration etc. are done in upnpserver.xml which looks alright.
Right now I am running it as root, as I was still playing around trying to get it to work one problem at a time.
I have uploaded my logs to pastebin: http://pastebin.com/tjrEXDhx

(2014-04-27, 11:20)wernerb Wrote: About a container with mysql, there is a container here: [url]https://github.com/ryan-robeson/xbmc-mysql[\url] that runs mysql as a container specifically for xbmc. You don't have to use docker for mysql, just point it to the correct database.
That would be an option. But still: If I can't get the bridge running, I can't use the containers.

Thanks for your reply. I hope you can see something from the logs that I can't. What I find strange is it complaining about addon files.
Reply
Well the container running mysql doesn't have to be on a bridge/host network, it just needs to be accessible through tcp.
The **only** reason we are using a bridge is because docker containers usually run on its separate network which does not support multicast..
Did you try https://help.ubuntu.com/community/Networ...tionBridge ?

The log doesn't look good, lots of problems at /opt/xbmc-server.
Reply
(2014-04-27, 13:11)wernerb Wrote: Well the container running mysql doesn't have to be on a bridge/host network, it just needs to be accessible through tcp.
The **only** reason we are using a bridge is because docker containers usually run on its separate network which does not support multicast..
Did you try https://help.ubuntu.com/community/Networ...tionBridge ?
Tried it all. Couldn't get it to work. All it kept doing is break my hosts network alltogether.

(2014-04-27, 13:11)wernerb Wrote: The log doesn't look good, lots of problems at /opt/xbmc-server.
It still tells me the upnp server was started though... why exactly I see so many warnings is very mysterious. Google isn't very helpful there either...
Reply
  • 1
  • 38
  • 39
  • 40(current)
  • 41
  • 42
  • 58

Logout Mark Read Team Forum Stats Members Help
xbmc minified as a server?9