primeval_god

I am not super knowledgeable about swap, but I think the best place to put a swap file would be on a drive mounted with the Unassigned drives plugin. The cache pool would probably be the next best place. I am certain that you wouldnt want it in the unRAID array. As to SSD vs HDD, I would guess an SSD would be the way to go but it probably depends on your usage pattern. BTW 128GB seems like a lot for swap space.

@melmurp @muslimsteel You might want to consider raising an issue over at https://github.com/netdata/netdata/ where the developers of Netdata and the Docker container reside.

Luckly you are wrong here. Multi Container Apps can be achieved using dockerman, its just not as straight forward to do as with other tools. You will have to manually create the docker networks required for the application, but once created they are available as a network option in the dockerman interface. Additionally there are other methods of getting compose on unRAID for instance I recently saw this intriguing post by @Thx And Bye. There are also other GUI based docker managers that exist that would allow you to utilize the more advanced features of docker. https://www.portainer.io/ for instance runs within a docker container itself, thus could be used on unRAID without any command line setup. Finally just a thought on limetech's motivations here. Note I am not associated with them or privy to their priorities of plans. My guess though would by that supporting more advanced container configurations, either via dockerman or by integrating something like compose is quite a ways down their priority queue. Likely because early on, when docker was introduced on unRAID as the primary avenue to install applications, the unRAID community began to create and coalesce around fat containers that package all processes required for a particular application stack. I have no interest in arguing container design philosophy, I just mean to point out that by and large the containers most prevalent on unRAID are likely those created by the unRAID community, which tend to be single container applications.

Are you perhaps looking for this support thread ? I dont believe that the netdata container supported by this thread has an override folder at this point.

As of last night i also got compilation working. It doesnt like being compiled under debian8. Changed the container to a debian 9 base and everything went smoothly.

I have been playing around with OpenRGB as well. I was going the docker route though. Having issues compiling at the moment. Also my target is a Gigabyte board, not that it matters thought.

Create an account on my.jdownloader.org and then log in with both your jdownloader app and any extension(s) you want to use. You can also use the interface at my.jdownloader.org or the android app.

A while back this template switched to using the official Netdata Docker Image netdata/netdata. The official image does not have the /etc/netdata/override feature that was present in the old titpetric/netdata image. Try mapping your config folder to /etc/netdata directly (/mnt/cache/appdata/netdata -> /etc/netdata). I believe that is the proper way to do it now, but if it doesnt work or causes other problems try mapping the file into the container instead -v /mnt/cache/appdata/netdata/netdata.conf:/etc/netdata/netdata.conf @szymon @Arbadacarba Did you have a config file mapped in to get UPS support? If so see my answer to @AlexB108 above.

Maybe this thread should be moved to the Plugin Support Forum?

I don't think this was intended to be a place to make feature requests. I would advise making your request in the Feature Requests Section of the forums. Be sure to check for duplicate existing request threads and like or continue the discussion in those.

Custom commands before sleep

Unfortunately that is not the way this plugin works. It does not include functionality for automatically waking your server. The time you added simply prevent it from going to sleep during those times if it is already on. To get wakeup to work you will need to insert a custom script to set an RTC wake alarm. There are various examples around the forums and farther back in this thread. The most recent I commented on is here Be warned though, RTC hardware support is notoriously inconsistent. Your system may or may not be capable of RTC wake. Take a look at the settings for the plugin with Help on. There is a way to save a log to determine why your server didnt sleep. I would take a shot in the dark and guess its a disk spindown issue, such as your cache disk being included in the list but never being able to spindown.

@Kazino43 did you try the script posted above? It has been a while since i used s3 sleep with my server but the scripts on this page look correct.

Correct, unRAID unpacks fresh from RAM on every boot. Technically speaking this item is the only one on the list that can't be done without using Docker/VM, due to the fact that unRAID does not have apt-get (or any common package manager for that matter). While this is not the only way to do things it is definitely the one i recommend. I would start by looking on docker hub for a base image of a distro you are most comfortable using, preferably an official image or one from well known maintainer (Python images are available as well). From there you have a couple of paths. You could pull the image, spin up a container and exec in, install all the extras you want in the container, then commit it to a new image for later use. Alternatively (and my preference) would be to write a Dockerfile that makes the customization to the base image as that will make rebuilding the image with new packages easier. Once you have a custom image you can either run your scripts manually from the unRAID CLI or using the user scripts plugin by spinning up a containers with the correct script. Something like docker run --rm -v /mnt/user/share-or-path-to-files:/path-in-container:rw my-custom-image /script-in-image.py --args-for-script or if you dont want to bake the script into the image docker run --rm -v /mnt/user/share-or-path-to-files:/path-in-container:rw -v /mnt/user/scripts:/scripts:ro my-custom-image /scripts/my-script.py --args-for-script You will want to look at the docker run -d and -i and -t flags as they can control if the container runs like a daemon or like a script on the console.

You cannot. The unRAID OS is unpacked fresh into RAM from the flash drive on each boot. Any modifications made to the OS (read files added or changes that are not on the array) are lost on reboot. The correct way of getting something "persistent" is to either package it as an unRAID plugin or to create a script (with the user.scripts plugin) that runs at bootup and re-applies your changes to the OS.

Not really news. You should take a closer look at the explanations of what the nvidia plugin actually does. TLDR; it does not install nvidia drivers on unRAID, rather it provides a means to install a custom version of unRAID with nvidia drivers baked in. As it is developed by a third-party, and is quite complex, a new version is not yet available. My money would by on "cpu isolation".

You dont update netdata in the container, rather you update the whole netdata container. Go to unRAID's docker page and use the check for updates button. Be aware though this particular project/container puts out new version constantly.

Sorry I dont use either plugin at the moment but out of curiosity, does the system crash regardless of whether the nvidia card is currently assigned to a running docker?

So i am trying to get qBittorrent VPN setup but i am running into some issues. The container and application come up, and i can access the webui. I can open a console into the container and check that i have a valid IP address through the VPN. qBittorrent however never finds any peers or shows any signs that it can contact the outside world. What am i doing wrong? docker create --name='qbittorrentvpn' --net='bridge' --log-opt max-size='50m' --log-opt max-file='3' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'WEBUI_PORT'='7070' -e 'INCOMING_PORT'='8999' -e 'VPN_ENABLED'='yes' -e 'VPN_USERNAME'='' -e 'VPN_PASSWORD'='' -e 'LAN_NETWORK'='192.168.0.0/24' -e 'NAME_SERVERS'='8.8.8.8,8.8.4.4,1.1.1.1' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='002' -p '7070:7070/tcp' -p '8999:8999/tcp' -p '8999:8999/udp' -v '/mnt/user/Video_Conversion/bit':'/downloads':'rw' -v '/mnt/user/appdata/qbittorrentvpn':'/config':'rw' 'markusmcnugen/qbittorrentvpn' 2019-11-21 04:03:36.501191 [info] VPN_ENABLED defined as 'yes' 2019-11-21 04:03:36.533662 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn dos2unix: converting file /config/openvpn/openvpn.ovpn to Unix format... 2019-11-21 04:03:36.563569 [info] VPN remote line defined as 'example.com 1194' 2019-11-21 04:03:36.593125 [info] VPN_REMOTE defined as 'example.com' 2019-11-21 04:03:36.619303 [info] VPN_PORT defined as '1194' 2019-11-21 04:03:36.643870 [info] VPN_PROTOCOL defined as 'udp' 2019-11-21 04:03:36.668103 [info] VPN_DEVICE_TYPE defined as 'tun0' 2019-11-21 04:03:36.692478 [info] LAN_NETWORK defined as '192.168.0.0/24' 2019-11-21 04:03:36.718937 [info] NAME_SERVERS defined as '8.8.8.8,8.8.4.4,1.1.1.1' 2019-11-21 04:03:36.744692 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS) 2019-11-21 04:03:36.769547 [info] Adding 8.8.8.8 to resolv.conf 2019-11-21 04:03:36.795720 [info] Adding 8.8.4.4 to resolv.conf 2019-11-21 04:03:36.821595 [info] Adding 1.1.1.1 to resolv.conf 2019-11-21 04:03:36.845036 [info] Starting OpenVPN... Thu Nov 21 04:03:36 2019 OpenVPN 2.4.4 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Sep 5 2018 Thu Nov 21 04:03:36 2019 library versions: OpenSSL 1.1.0g 2 Nov 2017, LZO 2.08 Thu Nov 21 04:03:36 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]172.246.117.2:1194 Thu Nov 21 04:03:36 2019 UDP link local: (not bound) Thu Nov 21 04:03:36 2019 UDP link remote: [AF_INET]172.246.117.2:1194 Thu Nov 21 04:03:37 2019 [example.com] Peer Connection Initiated with [AF_INET]172.246.117.2:1194 Thu Nov 21 04:03:43 2019 TUN/TAP device tun0 opened Thu Nov 21 04:03:43 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=0 Thu Nov 21 04:03:43 2019 /sbin/ip link set dev tun0 up mtu 1500 Thu Nov 21 04:03:43 2019 /sbin/ip addr add dev tun0 local 10.200.0.22 peer 10.200.0.21 Thu Nov 21 04:03:43 2019 Initialization Sequence Completed 2019-11-21 04:03:43.885837 [info] WebUI port defined as 7070 2019-11-21 04:03:43.911684 [info] LAN Network defined as 192.168.0.0/24 2019-11-21 04:03:43.937177 [info] Default gateway defined as 172.17.0.1 2019-11-21 04:03:43.963338 [info] ip route defined as follows... -------------------- 0.0.0.0/1 via 10.200.0.21 dev tun0 default via 172.17.0.1 dev eth0 10.200.0.1 via 10.200.0.21 dev tun0 metric 1 10.200.0.21 dev tun0 proto kernel scope link src 10.200.0.22 128.0.0.0/1 via 10.200.0.21 dev tun0 172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.10 172.246.117.2 via 172.17.0.1 dev eth0 192.168.0.0/24 via 172.17.0.1 dev eth0 -------------------- iptable_mangle 16384 1 ip_tables 24576 3 iptable_filter,iptable_nat,iptable_mangle 2019-11-21 04:03:43.992738 [info] iptable_mangle support detected, adding fwmark for tables 2019-11-21 04:03:44.033458 [info] Docker network defined as 172.17.0.0/16 2019-11-21 04:03:44.089384 [info] Incoming connections port defined as 8999 2019-11-21 04:03:44.119328 [info] iptables defined as follows... -------------------- -P INPUT DROP -P FORWARD ACCEPT -P OUTPUT DROP -A INPUT -i tun0 -j ACCEPT -A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A INPUT -i eth0 -p udp -m udp --sport 1194 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 7070 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 7070 -j ACCEPT -A INPUT -s 192.168.0.0/24 -i eth0 -p tcp -m tcp --dport 8999 -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT -A INPUT -i lo -j ACCEPT -A OUTPUT -o tun0 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --dport 1194 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 7070 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 7070 -j ACCEPT -A OUTPUT -d 192.168.0.0/24 -o eth0 -p tcp -m tcp --sport 8999 -j ACCEPT -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o lo -j ACCEPT -------------------- Adding 100 group groupadd: GID '100' already exists Adding 99 user useradd: UID 99 is not unique 2019-11-21 04:03:44.168476 [info] UMASK defined as '002' 2019-11-21 04:03:44.201173 [info] Starting qBittorrent daemon... Logging to /config/qBittorrent/data/logs/qbittorrent-daemon.log. 2019-11-21 04:03:45.233003 [info] qBittorrent PID: 203 2019-11-21 04:03:45.237872 [info] Started qBittorrent daemon successfully... (N) 2019-11-21T04:03:44 - qBittorrent v4.1.5 started (I) 2019-11-21T04:03:44 - qBittorrent is trying to listen on any interface port: 8999 (N) 2019-11-21T04:03:44 - Peer ID: -qB4150- (N) 2019-11-21T04:03:44 - HTTP User-Agent is 'qBittorrent/4.1.5' (I) 2019-11-21T04:03:44 - DHT support [ON] (I) 2019-11-21T04:03:44 - Local Peer Discovery support [OFF] (I) 2019-11-21T04:03:44 - PeX support [ON] (I) 2019-11-21T04:03:44 - Anonymous mode [OFF] (I) 2019-11-21T04:03:44 - Encryption support [ON] (I) 2019-11-21T04:03:44 - Embedded Tracker [OFF] (I) 2019-11-21T04:03:44 - GeoIP database loaded. Type: GeoLite2-Country. Build time: Tue Nov 12 21:09:59 2019. (N) 2019-11-21T04:03:44 - Using built-in Web UI. (N) 2019-11-21T04:03:44 - Web UI translation for selected locale (en) has been successfully loaded. (N) 2019-11-21T04:03:44 - Web UI: Now listening on IP: *, port: 7070 (C) 2019-11-21T04:03:44 - Queue positions were corrected in 2 resume files (I) 2019-11-21T04:03:44 - qBittorrent is successfully listening on interface :: port: TCP/8999 (I) 2019-11-21T04:03:44 - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/8999 (I) 2019-11-21T04:03:44 - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/8999 (N) 2019-11-21T04:03:44 - 'linuxmint-17-cinnamon-32bit-v2.iso' restored. (N) 2019-11-21T04:03:44 - 'checkmyiptorrent' restored.

@Gyurci Good news, the PR landed today. dbengine should now be usable if you pull the latest titpetric/netdata image.

At this time the titpetric/netdata image is not compiled with support for dbengine. There is an open issue and PR about it on github.

The thing to keep in mind though is that in unRAID docker is the preferred way of installing applications. Everything from a full plex installation down to a single python script should be run in docker unless for some reason it cant. While containers use slightly more resources than a bare application, they provide varying levels of isolation to help keep applications from destabilizing the core unraid OS. Additionally they allow applications and their dependencies to be decoupled from whatever particular version of Slackware that unRAID is currently using. The key take away is that ideally plugins and additional packages should be reserved for extensions to the unRAID os and those occasional applications that require very low level system access and cannot run under docker.

Its been a while since i used the S3 plugin, but I thought that the Excluded hours setting was for doing exactly what you are trying to do. If i remember correctly the S3 Sleep plugin has some debug logging that you can enable. Have you tried enabling that and watching the syslog? That should let you see what triggers the sleep function.

On Android i use Syncthing, with my server setup to Receive only and Ignore Delete for the Android photo folder. The folder on my server is backed up along with the rest of my server data.

Unless i am mistaken, and I might be since i dont use telegraf rather i use Netdata, monitoring only needs extensive read access to the system. Additionally in the case of unRAID the benefit of containerizing applications is more about preventing third party applications from destabilizing the core os, and dealing with the dependency nightmares that can arise from installing applications in a stripped down slackware build.