ciarlill

Since updating to the latest image I'm getting the following in the container log: 170801 17:54:53 mysqld_safe Logging to syslog. 170801 17:54:53 mysqld_safe Starting mysqld daemon with databases from /config/databases 170801 17:54:56 mysqld_safe Logging to syslog. 170801 17:54:56 mysqld_safe Starting mysqld daemon with databases from /config/databases 170801 17:55:00 mysqld_safe Logging to syslog. 170801 17:55:00 mysqld_safe Starting mysqld daemon with databases from /config/databases 170801 17:55:03 mysqld_safe Logging to syslog. 170801 17:55:03 mysqld_safe Starting mysqld daemon with databases from /config/databases Repeated essentially as long as the container is running. I have tried deleting the container and image and re-creating it but I continue to get the same message. I got a bash shell into the container to look at the mysql logs that are in /var/log but they were all empty. Any suggestions?

Alright I am back up and running. First, it makes sense that /var/lib/docker/containers does not exist... since the daemon couldn't start and mount it. Second, I found the config file for docker in /boot/config and was able to just edit my image size 20G. Now I can figure out the container causing the problem. Thanks

Thanks for the reply. Is there a way to do investigate and fix from the shell? My docker tab does not load anything below the navigation bar. No options whatsoever so I cannot turn it off in the UI. I also tried running du -ah /var/lib/docker/containers/ | grep -v "/$" | sort -rh | head -60 to investigate container log files as a root cause, but I have no "containers" folder under "/var/lib/docker". I have run into this issue of filling up the docker image before and tracked it down to an individual container that I just ended up rebuilding. But in that case the docker daemon was at least still running so I could interact with the containers. If possible I just want to clean up enough space to get it booted again so I can find the cause.

I ran 'diagnostics' and got the following in logs/docker.txt (full zip attached): $ tail docker.txt time="2017-05-30T16:41:42.206974508-04:00" level=info msg="libcontainerd: new containerd process, pid: 8833" time="2017-05-30T16:41:43.612576754-04:00" level=fatal msg="Error starting daemon: write /var/lib/docker/volumes/metadata.db: no space left on device" time="2017-05-30T16:41:44.163676548-04:00" level=info msg="libcontainerd: new containerd process, pid: 8997" time="2017-05-30T16:41:45.346545311-04:00" level=fatal msg="Error starting daemon: write /var/lib/docker/volumes/metadata.db: no space left on device" time="2017-05-30T17:10:32.184898289-04:00" level=info msg="libcontainerd: new containerd process, pid: 22537" time="2017-05-30T17:10:33.338567925-04:00" level=fatal msg="Error starting daemon: write /var/lib/docker/volumes/metadata.db: no space left on device" time="2017-05-30T17:10:39.085280285-04:00" level=info msg="libcontainerd: new containerd process, pid: 22749" time="2017-05-30T17:10:40.270522174-04:00" level=fatal msg="Error starting daemon: write /var/lib/docker/volumes/metadata.db: no space left on device" time="2017-05-30T17:10:49.450429338-04:00" level=info msg="libcontainerd: new containerd process, pid: 23006" time="2017-05-30T17:10:50.614545274-04:00" level=fatal msg="Error starting daemon: write /var/lib/docker/volumes/metadata.db: no space left on device" And here is my disk usage: $ df -h Filesystem Size Used Avail Use% Mounted on udev 7.6G 0 7.6G 0% /dev tmpfs 1.6G 9.3M 1.6G 1% /run /dev/sda1 48G 7.8G 38G 18% / tmpfs 7.6G 138M 7.5G 2% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 7.6G 0 7.6G 0% /sys/fs/cgroup /dev/sda5 129G 30G 92G 25% /home cgmfs 100K 0 100K 0% /run/cgmanager/fs tmpfs 1.6G 24K 1.6G 1% /run/user/1000 So it looks like the docker image itself is out of space.... but I'm not sure how to expand it. lucien-diagnostics-20170530-1713.zip

I just updated to 6.3.5. After a reboot my Docker tab is completely empty. I ssh'd into the server an it looks like dockerd was not running. I tried running it from the command line and reloaded the docker tab. At that point the tab loaded but none of my dockers were listed. Any ideas on what could have happened? What logs can I provide to help sort this out?

I am trying to run a find command with the -execdir option. However, -execdir gives this warning: find: The current directory is included in the PATH environment variable, which is insecure in combination with the -execdir action of find. Please remove the current directory from your $PATH (that is, remove "." or leading or trailing colons) I read up on that and understand the problem, but I am not sure how to remove "." from PATH, properly so it persists across reboots. I am also not sure if doing so will break some functionality of unraid? I do have NerdPack installed so I thought it is possible it may be coming from that plugin? Any help would be appreciated. Thanks. Annnd.... as usual I find the answer within minutes of posting. The "." is being added to the path in /etc/profile. Now I just need to find out how to remove it so it persists.

I had a problem with the logs growing like crazy, but it was because I left auto-update enabled. This was causing it download an update, and try to run the daemon for the new version. It could not launch because 5050 was still in use by the last process. So it just kept try to re-launch the updated version over and over constantly. I disabled the auto-update and restarted the docker and all looks good now. EDIT: Looks like this may not have had to do with auto-update, but rather restarting CPS from the WebUI. Instead, restart the docker.

Has anyone setup Sonarr with SSL? Going off the documentation here: https://github.com/Sonarr/Sonarr/wiki/SSL. Looks like httpcfg is not included in the docker even though it should be included with mono? I tried doing a 'find / -name httpcfg' in the docker container and no luck (after trying to run the command given). Even if I found httpcfg and was able to run the command... I do not think it would last past a restart or container update. edit: as usual I found my answer mere seconds after posting. httpcfg is in mono-devel. I am going to experiment with just getting it working period first, then try to figure out the best way to make it last on restart, etc. edit2: trying to manually install mono-devel (just for testing purposes) was a no-go - The following packages have unmet dependencies: mono-devel : Depends: libgamin0 but it is not installable Depends: libgnomeui-0 (>= 2.22.0) but it is not going to be installed Recommends: mono-csharp-shell but it is not going to be installed edit-final: found the github issue for this. sometimes i work from the wrong direction when solving a problem. https://github.com/linuxserver/docker-sonarr/issues/8 so i will be ditching sonarr for sickrage.

ahh i see. well thanks for explaining and saving me some time and headache i really appreciate your efforts here. looks there are plans to support docker compose in 6.2 (https://docs.docker.com/compose/) (https://lime-technology.com/forum/index.php?topic=39242.0) but will not be in the UI.

I believe you would just enable it for one or the other. No reason to enable it for both. Then you can use that proxy to browse sites over your VPN from any browser/computer on your LAN. binhex can correct me if I'm wrong. binhex - apologies if this is not the correct forum for the question -- getting off-topic a bit -- but have you considered creating a dedicated VPN/privoxy container and just using "vanilla" deluge and SABnbzd containers with configuration to enable usage of the VPN/privoxy container? I'm not sure it is even possible, but it would mean the entire unRaid box could run as a single device in the eyes of PIA. For most I'm sure a 5 device limit is not an issue, but I have 4 active devices currently so adding 2 more for both deluge and SABnbzd would put me over. It's not *really* a problem since my Usenet provider includes VPN access anyway.... just more or less something I thought about while I am considering the architecture for my server. edit: looks like SABnzbd doesn't support SOCKS5 proxying, but deluge does. I may experiment with creating a privoxy/squid/openvpn container just for the fun of it.

Thanks that explanation makes perfect sense. I have not had to deal with such ISPs thus far so I couldn't understand the reasoning before. Now that I understand, my third question seems silly, there would be no reason to run 2 instances of privoxy to tunnel over the same VPN. I saw a reference to 8181 in the description on this github page: https://github.com/binhex/arch-delugevpn and i believe in the same location for SABnbzd github page. Thanks again

3 quick questions: 1) Can you expand on what the Privoxy portion of this docker does? I understand what a proxy is, but I don't understand why you would (or would not) enable it for this docker. You mention unfiltered browsing of indexes, but I don't understand why that access would be filtered just from using a VPN in the first place. 2) If I use 2 VPN containers (Deluge & SABnbzd) does each container count against my PIA device limit? I believe PIA has a 5 device limit. 3) Will Privoxy running on both DelugeVPN and SABnbzdVPN on the same port cause a conflict? (Also on your github pages I see "Access Privoxy" showing port 8118 and in other places you mention port 8181, not sure if that is a typo or again showing my ignorance of the purpose/usage of Privoxy) Thanks!