JimL

The system will still power everything but you will of course not have a power draw that's anywhere close to the hw being in use. Same with CPU and hard drives, if you're only using 10% of them then your power draw will reflect that. I don't think so. I'd leave the VM for a gaming VM and have Plex running in Linux (in Docker). That way you can update/restore/shut off/etc your gaming machine without your entertainment going down. You'd also be able to isolate them from eachother, so if you wanted to play a game you had some dedicated cores for that.

Will you be transcoding HD or 4k? Budget?

I might be slow but I still find it extremely confusing. Like, I understand (from your posts, not the web ui) that if I select the cores to be isolated then I am stuck with assigning ONE core to each "thing". But does that mean VMs can also only run on one (isolated) core? Seems like a use case that at least I find to be very edge case / never used.

It's not normal. Can you post a diagnostics file from when or right after the system slows down? tools -> Diagnostics or run "diagnostics" in ssh/terminal

Started to see a few dockers deprecate UID/GID environment variables now in favor of using the user param that can be passed when running/creating containers. Would be nice with a GUI addition for it, now that we have the wonderful CPU pinning in the form it would be nice to build on it https://docs.docker.com/engine/reference/run/#user

Discussion here as well

It would at least help if the text was changed to this Instead of what it currently is, which explicitely states you can use isolated cores for docker containers But yes I would agree, disabling the cores where they are not usable, preferably with a tooltip saying the core is isolated would be very nice.

I also went in this trap. So I isolated half of the cores (6-11 + 18-23). I've since been troubles with Plex just grinding to a halt, and had actually decided to look into that today. Seems like I no longer have to. Running two 4K transcodes at the same time I could see it 100% the four cores it still had access to (it was pinned to 4-9 + 16-21), while it should have utilized up to 8 more cores. I'm assuming this will solve my issues. If isolation isn't supposed to let you assign cores to Docker I really think the help text should be updated.

I'd like something like this. Both to easily reuse Docker Compose setups, but also to be able to group applications together in the Unraid UI. Atm it feels like Unraid promotes bad Docker practice by making it way easier bundling all the services of an app in a single container instead of doing one service per container. If the GUI supported making apps consisting of several containers it would be easier to work with the general best practices. Depending on the UI novice users might not even have to worry about how many containers the app consists of.

96 GB

Make sure you scroll all the way down in the templates list. It first lists the default templates then user templates (your versions) at the bottom

Decided to try to get this running. This is what I did: I first had a look at the dockerfile https://github.com/danielquinn/paperless/blob/master/docker-compose.yml.example It creates two services, the webserver and a consumer. Both using the same dockerfile but with some varying settings https://github.com/danielquinn/paperless/blob/master/Dockerfile Lets start with the webserver service Unraid - apps - search for paperless - search docker hub - select danielquinn/paperless Fill it out as follows: Change 8001 to whichever port you want to use (one that is available on your unraid server) And of course set some password instead of my (dummy) one I got the paths, port and environment variables from the docker compose file, which also referenced a separate env file https://github.com/danielquinn/paperless/blob/master/docker-compose.env.example I did not include the group id as on my first run this errored out because the unraid default group (100) already exists in the container. Which is unfortunate, but I won't bother with it atm. The reason we set up user id and group id for the docker containers is so the file permissions/ownerships stay "in sync" between unraid and the containers. It fired up! But I could not log in. I got stumped, I could not find a default login anywhere. After googling paperless default login I ended up here https://github.com/danielquinn/paperless/blob/master/docs/setup.rst In order to run this "createsuperuser" command I recreated the container again, just to copy the command it uses. In order to recreate: click the paperless container in the Unraid Web Ui, dummy change some value (add a space and remove it again) and hit apply so the container is recreated. The reason for this is that we can hook on to that command and get an interactive shell, and by using the same command we get the same volume (folder) mounts. Which means our changes will hopefully be saved to our config folder and persist when recreating the container. We'll modify this command for our use. You could probably simplify this command by removing a lot of (possibly) unnecessary configs. But as it's a simple copy/paste with a couple of edits I chose to not clean it up as all it would really get me was possible error sources. docker run -d --name='paperless' --net='bridge' -e TZ="America/Los_Angeles" -e HOST_OS="unRAID" -e 'PAPERLESS_OCR_LANGUAGES'='' -e 'USERMAP_UID'='99' -e 'PAPERLESS_PASSPHRASE'='xxIj4C2n7vIwLcyiu6xQ' -p '8001:8000/tcp' -v '/mnt/user/appdata/paperless/data':'/usr/src/paperless/data':'rw' -v '/mnt/user/appdata/paperless/media':'/usr/src/paperless/media':'rw' -v '/mnt/user/appdata/paperless/consume':'/consume':'rw' -v '/mnt/user/appdata/paperless/export':'/export':'rw' 'danielquinn/paperless' runserver --insecure --noreload 0.0.0.0:8000 We need to remove the existing container first so we can create a new one when running our craetesuperuser command. Run this on the server: docker rm paperless Then I simply modified the command above for the container to be removed automatically as we don't want to save this container which tries to create a super user on start (--rm), changed it out to be interactive (-it) and I removed -d for daemon (background process) and changed the command from running the server to creating the super user. Run this on the server: docker run --rm -it --name='paperless' --net='bridge' -e TZ="America/Los_Angeles" -e HOST_OS="unRAID" -e 'PAPERLESS_OCR_LANGUAGES'='' -e 'USERMAP_UID'='99' -e 'PAPERLESS_PASSPHRASE'='xxIj4C2n7vIwLcyiu6xQ' -p '8001:8000/tcp' -v '/mnt/user/appdata/paperless/data':'/usr/src/paperless/data':'rw' -v '/mnt/user/appdata/paperless/media':'/usr/src/paperless/media':'rw' -v '/mnt/user/appdata/paperless/consume':'/consume':'rw' -v '/mnt/user/appdata/paperless/export':'/export':'rw' 'danielquinn/paperless' createsuperuser Enter username, email and password when prompted. You should be disconnected from the container afterwards. Then click the paperless container in the Unraid Web Ui again, dummy change some value (add a space and remove it again) and hit apply so our proper container is recreated. Paperless should now be running at http://tower:8001 (or whichever port you chose) --- But! It's not doing much since we don't yet have the consumer service running. So on to the next service, since it's basically the same docker container it should be simple (??) Go to http://tower/Docker/AddContainer Select the paperless template we just made (it should now be under user templates) Fill it out as follows: It's cruical you select the same passphrase here as in the other container You must also select a different name as you can't have two containers with the same name And lastly you should add the languages you want the OCR to use You should now have both paperless and paperless_consumer running. If you now try to copy a file over to the consume folder (I have it available over SMB/windows file share) and wait a few moments it should dissappear from the consume folder and magically pop up in the admin ui edit: fixed a typo -rm -> --rm

adoucette: the linuxserver nextcloud container only exposes the tls port (443), are you sure you can use port 80? In order to get my services set up with Traefik I had to add this to traefik.toml (top level) in order to allow self signed certs in the containers running on https insecureSkipVerify = true You will also have to set the labels for the service traefik.protocol=https traefik.port=443

I had tried deleting the config dir / box and setting it up again. but! Container worked flawlessly after updating, didn't have to do any changes or anything. Great work, thanks a lot. Used to run OpenVPN-AS in a VM on a box at home, much better to have it as a docker container on my file server

Tried installing the OpenVPN-AS docker container on Unraid 6 final (fresh install / 5.x config set up 10 days ago) but can't get it to work (got several other docker containers running on Unraid atm). I've added the environment variables, and mapped the data volume. When I try to access the Web UI (https://tower:943/admin) I get "ERR_CONNECTION_REFUSED" root@012ebad9e29a:/# tail -n 100 /var/log/openvpnas.log 2015-06-30 10:53:21+0000 [-] Log opened. 2015-06-30 10:53:21+0000 [-] twistd 9.0.0 (/usr/local/openvpn_as/bin/python 2.7.6) starting up. 2015-06-30 10:53:21+0000 [-] reactor class: twisted.internet.epollreactor.EPollReactor. 2015-06-30 10:53:21+0000 [-] rmdir /usr/local/openvpn_as/etc/db_push 2015-06-30 10:53:22+0000 [-] ACCESS SERVER starting, version=2.0.17 2015-06-30 10:53:22+0000 [-] Max open files set to (4096, 4096) 2015-06-30 10:53:22+0000 [-] /etc/resolv.conf changed, reparsing 2015-06-30 10:53:22+0000 [-] Resolver added ('193.213.112.4', 53) to server list 2015-06-30 10:53:22+0000 [-] Resolver added ('130.67.15.198', 53) to server list 2015-06-30 10:53:22+0000 [-] Resolver added ('192.168.1.1', 53) to server list 2015-06-30 10:53:23+0000 [-] twisted.web.server.Site starting on "u'/usr/local/openvpn_as/etc/sock/sagent'" 2015-06-30 10:53:23+0000 [-] *** MyError.report *** 2015-06-30 10:53:23+0000 [-] Stack Traceback 2015-06-30 10:53:23+0000 [-] ('build/bdist.linux-x86_64/egg/pyovpn/sagent/svcset.py', 147, 'transition', None) 2015-06-30 10:53:23+0000 [-] ('build/bdist.linux-x86_64/egg/pyovpn/sagent/svcset.py', 626, '__init__', None) 2015-06-30 10:53:23+0000 [-] ('build/bdist.linux-x86_64/egg/pyovpn/sagent/svcset.py', 549, 'bind', None) 2015-06-30 10:53:23+0000 [-] ('build/bdist.linux-x86_64/egg/pyovpn/sagent/svcset.py', 482, 'bind_unix', None) 2015-06-30 10:53:23+0000 [-] ('build/bdist.linux-x86_64/egg/pyovpn/sagent/svcset.py', 464, 'listen', None) 2015-06-30 10:53:23+0000 [-] ('/usr/local/openvpn_as/lib/python2.7/site-packages/Twisted-9.0.0-py2.7-linux-x86_64.egg/twisted/application/service.py', 185, 'setServiceParent', 'self.parent.addService(self)') 2015-06-30 10:53:23+0000 [-] ('/usr/local/openvpn_as/lib/python2.7/site-packages/Twisted-9.0.0-py2.7-linux-x86_64.egg/twisted/application/service.py', 304, 'addService', 'service.privilegedStartService()') 2015-06-30 10:53:23+0000 [-] ('/usr/local/openvpn_as/lib/python2.7/site-packages/Twisted-9.0.0-py2.7-linux-x86_64.egg/twisted/application/internet.py', 85, 'privilegedStartService', 'self._port = self._getPort()') 2015-06-30 10:53:23+0000 [-] ('/usr/local/openvpn_as/lib/python2.7/site-packages/Twisted-9.0.0-py2.7-linux-x86_64.egg/twisted/application/internet.py', 116, '_getPort', '*self.args, **self.kwargs)') 2015-06-30 10:53:23+0000 [-] ('/usr/local/openvpn_as/lib/python2.7/site-packages/Twisted-9.0.0-py2.7-linux-x86_64.egg/twisted/internet/posixbase.py', 314, 'listenUNIX', 'p.startListening()') 2015-06-30 10:53:23+0000 [-] ('/usr/local/openvpn_as/lib/python2.7/site-packages/Twisted-9.0.0-py2.7-linux-x86_64.egg/twisted/internet/unix.py', 91, 'startListening', 'raise CannotListenError, (None, self.port, le)') 2015-06-30 10:53:23+0000 [-] Server agent initialization failed: Couldn't listen on any:/usr/local/openvpn_as/etc/sock/sagent: [Errno 38] Function not implemented.: sagent/svcset:147,sagent/svcset:626,sagent/svcset:549,sagent/svcset:482,sagent/svcset:464,application/service:185,application/service:304,application/internet:85,application/internet:116,internet/posixbase:314,internet/unix:91 (twisted.internet.error.CannotListenError) 2015-06-30 10:53:23+0000 [-] Main loop terminated. 2015-06-30 10:53:23+0000 [-] Server Shut Down.

Any more info on this? I tried searching the forums and got nothing edit: nevermind, suddenly I found lots of stuff

syslog http://jimleirvik.no/syslog-2014-02-07.txt (it was too large to upload even when zipped)

Hey, I just added 8 disks to my unraid server and at the same time upgraded to v5.0.5 I can't for the life of me find the SMB security settings for the disks, so the new disks are now shared (which I don't want to do) I am looking for this: http://www.avforums.com/threads/smurfs-monster-40tb-unraid-nas-build-part-ii.1511151/page-13#post-20047615 But I can only find this I've tried rebooting and tried opening the disk settings with the array started and not. I'm sure I'm missing something silly, but I'm really stuck.

Thanks

attached syslog syslog-2014-02-06.txt.zip

I've just upgraded to new hardware and software. And I'm having some trouble with the normal web gui (unmenu works fine) It works for a while after a reboot, then it goes offline. If I try to manually restart it this shows up in the logs Other interesting logs System:

PSU issue it was. But in case I couldn't get this running again, how would I access the error log?

The server boots fine and I can get into shell/webgui/unmenu but after a few seconds it physically powers down / shuts off.

All fans running as they should, I will try to swap out the PSU tonight and see if it help Thanks for the prompt reply! I'll get that update sorted as well, I'm not running 5.0.3 as it probably wasn't released when I installed, haven't rebooted since.

I've had Unraid 5.0.1 running smoothly for (almost) a month, haven't touched it since I set it up, but today it just died. I can boot it up and it works fine for a few seconds, then it crashes / shuts down. How can I get to the error log? I don't have time to do anything on the live system, and I can't find it on the USB.