eg4190

Thanks for the response. So I guess what I really want is for the Dropbox container to run as root. Everything else on my server is running as root and creating downloaded files as root:root, and I've had no issues witht his. I have no personal information on my server and it's just movies, music and comic books, so I really don't care about the security implications of this. If I were to run this Dropbox container under my non-root username, I would also need to move every other container over to that username. So my preference would be to just run this Dropbox container as root. I tried this by entering DROPBOX_USER = root, DROPBOX_USERID = 0, DROPBOX_GROUP = root, and DROPBOX_GROUPID = 0. I'm getting this in the log after activation: usermod: user root is currently used by process 1 WARNING:tornado.access:404 HEAD /blocks/510013235/NV50NTkhIybNc_1--VF0mY4chlBSPeR7fQZwTf1bf4k (172.17.42.1) 678.61ms WARNING:tornado.access:404 HEAD /blocks/510013235/NV50NTkhIybNc_1--VF0mY4chlBSPeR7fQZwTf1bf4k (172.17.42.1) 716.83ms ... ... And so on, with a few thousand of those 404 errors. ... ... Finally, the container dies with this at the end of the log: /usr/local/bin/myinit.sh: line 14: 14 Killed su -l ${DROPBOX_USER} -c "/dropbox/.dropbox-dist/dropboxd" So apparently the container doesn't like running as root, but I'm getting similar 404 errors (minus the first and last error) running as either "nobody" or my non-root UID, just because neither of those accounts has access to the files the other containers are putting in the Dropbox folder.

That's actually something I'm confused about -- I'm assuming all of the other processes are creating new files as root, because none of the other containers specify a user. When I Google how to change the default user for new files, I wind up reading a lot of responses about how doing so is evil. I do have a non-root user account set up on my unRAID box, but I'm not sure how to set that account as the default user for new files, so that all of my other Docker containers are writing to the Dropbox folder as that user (I'm assuming the other containers all have access to the same user accounts as the unRAID box?). Any help would be much appreciated.

I'm getting a weird syncing issue with this container. If I drag/update files into my local Dropbox folder on the various machines I have around the house, the Docker instance on my server is syncing the files properly. But any changes that originate on the server are not being reflected on my local machines. I would like certain automated downloads of mine to move over to Dropbox automatically, but this currently isn't working because the unRAID Docker instance doesn't seem to upload anything. Any ideas?

So I don't know if this is a Kodi-headless question or a Headphones question -- I've got Kodi-headless receiving update notifications from CouchPotato, SickRage and Headphones and this all works near-flawlessly. However, one thing I noticed is that Kodi-headless only has the bare minimum installed in terms of addons. Movies and TV shows are scraping just fine, and so are albums in my music library, but not music artists. When Headphones grabs something from a new artist and sends a notification that the download is complete, I'm noticing that Kodi-headless is scraping just the album info, but not the artist info. In order to pull the artist fanart and info, I have to manually update the music library using one of my frontends. Looking in the Kodi-headless addons folder, it seems that the Universal Artist Scraper isn't installed. Since this version is headless, I wasn't sure how to install the artist scraper without the GUI, so I just unzipped the latest version into my addons folder to see if that would do it. Still seeing that albums are scraped, but not artists. Is there something else I need to do to enable the artist scraper? Is the Headphones notification only prompting album-level scraping instead of a full music library update?

Yeah, deleting the plugins completely and rebooting did bring the Web GUI back. I will look into installing these apps via Docker. I think the documentation could be a little clearer about this, though.

New to unRAID, just installed it on my old home-built NAS which I use primarily as a media server. Had absolutely no issues with the install, started migrating my 16 TB of movies and TV shows over to the new array. But then I got greedy and started to set up Sab/SickBeard/Couch Potato using this guide: http://lime-technology.com/wiki/index.php/Setting_Up_SABnzbd,_SickBeard,_and_CouchPotoato I have a moderate level of Linux experience and have installed these three programs on a number of different devices. However, after I ran the Sab install command ("installplg sabnzbd_unplugged.plg") and moved on to "installplg sickbeard_unplugged.plg" the problems started. Running the Sickbeard install command led to this error message: /usr/bin/php: error while loading shared libraries: libsqlite3.so.0: cannot open shared object file: No such file or directory That was bad enough, but at precisely this point the WebGUI stopped working. I tried a few things, namely this: killall emhttp nohup /usr/local/sbin/emhttp & The first time I ran that, I got a "Segmentation fault" error. I restarted the machine and the WebGUI was still down (can Telnet into the box with no problem, and UnMenu still works). This time, running the killall and nohup commands yielded this: nohup: ignoring input and appending output to Ç nohup.out So no error message, but the WebGUI is still down. I tried deleting the /boot/config/plugins/sabnzbd folder and rebooting, but that didn't do anything. This is a particularly frustrating issue because a lot of people seem to be having similar problems, but none of the recommended solutions worked. Any help would be greatly appreciated. syslog.zip