exist2resist

@sparklyballs, is your Kodi headless good to go, or you still working on it?

You could, but your best way is to pull mariadb docker container and set that up. Then use the headless xbmc instance for library updates. That's how I have it setup up for for multi room instances. EDIT: Do as sparklyballs suggests, have different sources set up in different rooms.

are you running unraid 6 later than b10 ? Yes I'm running b12. load it from my template, the password/user for the webui/updates etc is xbmc/xbmc and the gotham version is on port 8089 and the helix version default at 8080 The template in the first post, on here? oops, forgot the url http://lime-technology.com/forum/index.php?topic=37209.0 Still not working for me, notifications fail. Also the web GUI does not load, I get a blank page. I'm trying to use the 13.2 headless. /root/.xbmc is mapped to my XBMC folder where the userdata folder and others sit, inside the userdata I have both xml files, sources and advancedsettigs. I know my sql works because I have XBMC 13.2 pulling info from it. I can also confirm that these work because my XBMC HTPC attaches to the database and maps the right shares. the docker provides its own advancedsettings.xml , personally i find it best to start with a blank slate. save out your sources.xml, backup everything else to another folder just in case and start from scratch clean folder. enter the sql setup in the template, don't use hostnames or localhost, use the ip address of your mariadb/mysql host. Thanks, that's what it was. Needed to start with a blank advancedsettings.xml

are you running unraid 6 later than b10 ? Yes I'm running b12. load it from my template, the password/user for the webui/updates etc is xbmc/xbmc and the gotham version is on port 8089 and the helix version default at 8080 The template in the first post, on here? oops, forgot the url http://lime-technology.com/forum/index.php?topic=37209.0 Still not working for me, notifications fail. Also the web GUI does not load, I get a blank page. I'm trying to use the 13.2 headless. /root/.xbmc is mapped to my XBMC folder where the userdata folder and others sit, inside the userdata I have both xml files, sources and advancedsettigs. I know my sql works because I have XBMC 13.2 pulling info from it. I can also confirm that these work because my XBMC HTPC attaches to the database and maps the right shares.

are you running unraid 6 later than b10 ? Yes I'm running b12. load it from my template, the password/user for the webui/updates etc is xbmc/xbmc and the gotham version is on port 8089 and the helix version default at 8080 The template in the first post, on here? oops, forgot the url http://lime-technology.com/forum/index.php?topic=37209.0 Thanks I'll give it a go.

are you running unraid 6 later than b10 ? Yes I'm running b12. load it from my template, the password/user for the webui/updates etc is xbmc/xbmc and the gotham version is on port 8089 and the helix version default at 8080 The template in the first post, on here?

are you running unraid 6 later than b10 ? Yes I'm running b12.

I grabbed this XBMC build from docker... https://registry.hub.docker.com/u/sparklyballs/xbmc-headless/ I want to use it for updating my mariadb library, couple questions though. What port does this container sit on, 8089, 80, 8080....? Also what is the user id and password, xbmc:xbmc?

What's the difference between the plg for sickbeard vs sickbeard_alt?

Any idea why when I go to the settings page and click any of the plugins it comes up with a blank plugin page?

I think it was developed to be the host of docker, not the baseimage, but I might be wrong. Actually Ubuntu released a new version designated specifically to be docker baseimage. Also the Ubuntu docker images are less resource hungry than some other flavors of linux.

If someone can't handle Unraid they should invest in a QNAP device, it has a simply stupid interface. An alternative; if people don't know how to use docker or don't take the time to learn, go install the unraid 6 plugins that are readily available in the forums. Also I wanted to add that Docker is about choice. And each Unraid installation is unique to every installation. I'm just migrating to Ur6 and I will have several Windows VMs on there using KVM, because I personally believe that KVM > XEN. Then there are those that include ssh in their docker images... that's a back practice. Docker allows you to connect to the image without the need for SSH, but some want that choice. Using scripts to run installations inside the docker image... another bad practice. Some prefer these, others don't it all comes down to preference. I like my docker containers to auto update on their own, I don't have the time to baby the server and prefer automation.

Just wanted to say, thanks for the work sparklyballs. Looking forward to the Kodi release.

2014/08/25 15:03:46 docker daemon: 1.1.2 1df87acb3375b6c2765e2202f178dee699647448; execdriver: native; graphdriver: Btrfs [d8e64386] +job serveapi(unix:///var/run/docker.sock) [d8e64386] +job initserver() [d8e64386.initserver()] Creating server driver not supported [d8e64386] -job initserver() = ERR (1) 2014/08/25 15:03:46 driver not supported 2014/08/25 15:08:47 docker daemon: 1.1.2 1df87acb3375b6c2765e2202f178dee699647448; execdriver: native; graphdriver: Btrfs [748c1bf7] +job serveapi(unix:///var/run/docker.sock) [748c1bf7] +job initserver() [748c1bf7.initserver()] Creating server driver not supported [748c1bf7] -job initserver() = ERR (1) 2014/08/25 15:08:47 driver not supported What driver is it looking for?

Here is a little more info on docker not starting, got this out of the log.... 2014/08/25 15:03:46 docker daemon: 1.1.2 1df87acb3375b6c2765e2202f178dee699647448; execdriver: native; graphdriver: Btrfs [d8e64386] +job serveapi(unix:///var/run/docker.sock) [d8e64386] +job initserver() [d8e64386.initserver()] Creating server driver not supported [d8e64386] -job initserver() = ERR (1) 2014/08/25 15:03:46 driver not supported 2014/08/25 15:08:47 docker daemon: 1.1.2 1df87acb3375b6c2765e2202f178dee699647448; execdriver: native; graphdriver: Btrfs [748c1bf7] +job serveapi(unix:///var/run/docker.sock) [748c1bf7] +job initserver() [748c1bf7.initserver()] Creating server driver not supported [748c1bf7] -job initserver() = ERR (1) 2014/08/25 15:08:47 driver not supported What driver is docker referring to?

I'm doing some testing on unRaid B6, latest version as I am finally ready to move from version 5 to 6. However every time I attempt to start docker the Service Status remains shut down. I have a Btrfs formatted drive mounted. I'm using the free version of unRAID. Docker is pointing to my Btrfs mounted drive.

Thanks, this was easy to setup. Couple things to note that need to be setup after this. For instance the run as user option needs to be enabled... # If Murmur is started as root, which user should it switch to? # This option is ignored if Murmur isn't started with root privileges. uname=nobody Super user password enabled... -supw <pw> [srv] Set password for 'SuperUser' account on server srv. mumur.x86 -supw <pw> EDIT: Also to note that when adding the start line to the GO script make sure you add the -ini, other wise you will loose your settings upon reboot. So set SuperUser password upon first run and in go script add the following /mnt/system/data/murmur/murmur.x86 -ini /mnt/system/data/murmur/murmur.ini

The MediaBrowser Unraid 5 server is not installing on my system. When I go to Settings it specifies that it is NOT INSTALLED in red letters, when I click install it specifies: I assume the unfunished version is for version 6 not 5. Also when I attempt to install via bash I get the follwing... Nevermind I got it working. I downloaded the Zip file from here: https://www.dropbox.com/s/07hh1g4x9xo28jb/MBServer.Mono.zip and extracted it into my install directory. Once I did this I clicked install and it worked.

I can't wait, with Docker and Xen Unraid will just shine.

Another question, so I installed the cifs-utils, and added both cifs and nfs mount commands in fstab. I've tried them both and I get an error on nfs when I attempt to mount. CIFS works fine but NFS doesn't . To note I made the edits to the NFS share in Unraid setting it to private and adding the parameters. 10.50.70.126:/mnt/user/OwnCloud /mnt/storage nfs rw,rsize=4096,wsize=4096,hard,intr,async,nodev,nosuid 0 0 For NFS Also could we make the [GUIDE]s all sticky on the front page? Not sure if it already is.

Ha, I just came to post that I figured it out by watching (what I assume are yours) YouTube instructional videos. Thanks, I got it up and running. RTFM

I followed the instructions as per the first page with my own edits, but I'm unable to start the VM. I'm getting error when I try and run xl create debcloud.cfg /mnt/system/ is located on a mounted hard drive that is not part of the array. I realize that this issue is related to the absence of a bridged network adapter, and I have looked in the xen/scripts folder at the vif-bridge script. But I still have no idea how to bridge the adapter. Help would be appreciated.

Issue has been resolved with a newer version of Unraid

It happens right after a boot, minute and a half after emhttp is started. Then it doesn't happen again. Jan 3 17:07:32 Tower emhttp: shcmd (50): :>/etc/samba/smb-shares.conf Jan 3 17:07:32 Tower emhttp: get_config_idx: fopen /boot/config/shares/Comics.cfg: No such file or directory - assigning defaults Jan 3 17:07:32 Tower emhttp: Restart SMB... Jan 3 17:07:32 Tower emhttp: shcmd (51): killall -HUP smbd Jan 3 17:07:32 Tower emhttp: shcmd (52): ps axc | grep -q rpc.mountd Jan 3 17:07:32 Tower emhttp: _shcmd: shcmd (52): exit status: 1 Jan 3 17:07:32 Tower emhttp: shcmd (53): /usr/local/sbin/emhttp_event svcs_restarted Jan 3 17:07:32 Tower emhttp_event: svcs_restarted Jan 3 17:07:32 Tower emhttp: shcmd (54): /usr/local/sbin/emhttp_event started Jan 3 17:07:32 Tower emhttp_event: started Jan 3 17:08:51 Tower kernel: mce: [Hardware Error]: Machine check events logged How do I check the "Machine check events"?

Thanks Joe, It was the case of the "C". Rebooted and everything re installed. The reason it's on two lines is because Putty wrapped the text to the next line.