April 29, 201511 yr anything we can do to help? At this point, no. I think we have it fixed. Had someone test a new build for me overnight with their setup (reporting the exact same problem). No issues today.
April 29, 201511 yr We are actively looking into this and testing with Docker 1.6 to see if this problem exists there. If not, phew. If so, we will need to open a bug report with docker. Bottom line: you should ALWAYS be able to kill a running container. If that doesn't work, something is broken. in docker 1.4 there was a bug that if you were exec'd in to a container and issued a stop command elsewhere for that container it locked up and you couldn't kill it. in unraid that meant it killed the webui as well. sure it was reported somewhere round here.
April 29, 201511 yr We are actively looking into this and testing with Docker 1.6 to see if this problem exists there. If not, phew. If so, we will need to open a bug report with docker. Bottom line: you should ALWAYS be able to kill a running container. If that doesn't work, something is broken. in docker 1.4 there was a bug that if you were exec'd in to a container and issued a stop command elsewhere for that container it locked up and you couldn't kill it. in unraid that meant it killed the webui as well. sure it was reported somewhere round here. Well isn't that solution to not be "exec'd" into the container? lol. It wouldn't surprise me in 1.4 because I think that was when they had just introduced docker exec, so maybe a few bugs existed still there.
April 29, 201511 yr Author sab crashed again. This time with the multicore option turned off. looks like mine crashed overnight too with single core, I guess jonp is onto something with it being a docker bug.
April 30, 201511 yr Author so i manually rebooted my server (again) and now my cache SMB share is broken. i can see the contents at /mnt/cache but nothing via windows explorer or "view" on the shares page. probably totally unrelated but i've attached my syslog. syslog1.txt
April 30, 201511 yr so i manually rebooted my server (again) and now my cache SMB share is broken. i can see the contents at /mnt/cache but nothing via windows explorer or "view" on the shares page. probably totally unrelated but i've attached my syslog. Just the cache share? So your other shares are browsable? And on the shares page in the webGui, you're not going through SMB, so that would indicate to me this isn't a SMB issue, but something with user shares maybe? Stopping / starting array doesn't solve this?
April 30, 201511 yr Author correct. I've stopped/started and rebooted and it's persistent. could the manual reboots have caused some user share config corruption or something? it just seems weird that it's only cache and nothing else. The only thing of note that i can think of is that cache is usually still mounted during my manual reboots because the hung docker process is holding onto it.
April 30, 201511 yr Author something happened and now all my user shares broken vm console: syslog: Apr 30 11:01:33 vault13 php: /usr/bin/docker start SickRage Apr 30 11:01:33 vault13 kernel: device vethf08fcc4 entered promiscuous mode Apr 30 11:01:33 vault13 avahi-daemon[4589]: Withdrawing workstation service for veth86962cc. Apr 30 11:01:33 vault13 kernel: eth0: renamed from veth86962cc Apr 30 11:01:33 vault13 kernel: docker0: port 5(vethf08fcc4) entered forwarding state Apr 30 11:01:33 vault13 kernel: docker0: port 5(vethf08fcc4) entered forwarding state Apr 30 11:01:33 vault13 php: SickRage Apr 30 11:01:44 vault13 emhttp: /usr/bin/docker logs --tail=350 -f SickRage 2>&1 Apr 30 11:01:48 vault13 kernel: docker0: port 5(vethf08fcc4) entered forwarding state Apr 30 11:11:44 vault13 php: /usr/bin/docker stop Sonarr Apr 30 11:11:44 vault13 php: Sonarr Apr 30 11:11:44 vault13 avahi-daemon[4589]: Withdrawing workstation service for vethddc7f4c. Apr 30 11:11:44 vault13 kernel: docker0: port 3(vethddc7f4c) entered disabled state Apr 30 11:11:44 vault13 kernel: device vethddc7f4c left promiscuous mode Apr 30 11:11:44 vault13 kernel: docker0: port 3(vethddc7f4c) entered disabled state Apr 30 11:12:05 vault13 emhttp: /usr/bin/docker logs --tail=350 -f Sonarr 2>&1 Apr 30 11:13:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/3dmovies Transport endpoint is not connected Apr 30 11:13:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/anime Transport endpoint is not connected Apr 30 11:13:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/appdata Transport endpoint is not connected Apr 30 11:13:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/apps Transport endpoint is not connected Apr 30 11:13:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/backup Transport endpoint is not connected Apr 30 11:13:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/cache Transport endpoint is not connected Apr 30 11:13:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/docker Transport endpoint is not connected Apr 30 11:13:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/downloads Transport endpoint is not connected Apr 30 11:13:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/games Transport endpoint is not connected Apr 30 11:13:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/movies Transport endpoint is not connected Apr 30 11:13:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/music Transport endpoint is not connected Apr 30 11:13:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/photos Transport endpoint is not connected Apr 30 11:13:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/porn Transport endpoint is not connected Apr 30 11:13:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/tv Transport endpoint is not connected Apr 30 11:13:40 vault13 php: /usr/bin/docker start Sonarr Apr 30 11:13:40 vault13 kernel: device vethb1c41c1 entered promiscuous mode Apr 30 11:13:40 vault13 avahi-daemon[4589]: Withdrawing workstation service for veth0e7f247. Apr 30 11:13:40 vault13 kernel: eth0: renamed from veth0e7f247 Apr 30 11:13:40 vault13 kernel: docker0: port 3(vethb1c41c1) entered forwarding state Apr 30 11:13:40 vault13 kernel: docker0: port 3(vethb1c41c1) entered forwarding state Apr 30 11:13:41 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/3dmovies Transport endpoint is not connected Apr 30 11:13:41 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/anime Transport endpoint is not connected Apr 30 11:13:41 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/appdata Transport endpoint is not connected Apr 30 11:13:41 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/apps Transport endpoint is not connected Apr 30 11:13:41 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/backup Transport endpoint is not connected Apr 30 11:13:41 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/cache Transport endpoint is not connected Apr 30 11:13:41 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/docker Transport endpoint is not connected Apr 30 11:13:41 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/downloads Transport endpoint is not connected Apr 30 11:13:41 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/games Transport endpoint is not connected Apr 30 11:13:41 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/movies Transport endpoint is not connected Apr 30 11:13:41 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/music Transport endpoint is not connected Apr 30 11:13:41 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/photos Transport endpoint is not connected Apr 30 11:13:41 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/porn Transport endpoint is not connected Apr 30 11:13:41 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/tv Transport endpoint is not connected Apr 30 11:13:41 vault13 avahi-daemon[4589]: Withdrawing workstation service for vethb1c41c1. Apr 30 11:13:41 vault13 kernel: docker0: port 3(vethb1c41c1) entered disabled state Apr 30 11:13:41 vault13 kernel: device vethb1c41c1 left promiscuous mode Apr 30 11:13:41 vault13 kernel: docker0: port 3(vethb1c41c1) entered disabled state Apr 30 11:13:46 vault13 emhttp: /usr/bin/docker logs --tail=350 -f Sonarr 2>&1 Apr 30 11:13:52 vault13 php: /usr/bin/docker start Sonarr Apr 30 11:13:52 vault13 kernel: device veth77103c7 entered promiscuous mode Apr 30 11:13:52 vault13 avahi-daemon[4589]: Withdrawing workstation service for vethc75e731. Apr 30 11:13:52 vault13 kernel: eth0: renamed from vethc75e731 Apr 30 11:13:52 vault13 kernel: docker0: port 3(veth77103c7) entered forwarding state Apr 30 11:13:52 vault13 kernel: docker0: port 3(veth77103c7) entered forwarding state Apr 30 11:13:52 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/3dmovies Transport endpoint is not connected Apr 30 11:13:52 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/anime Transport endpoint is not connected Apr 30 11:13:52 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/appdata Transport endpoint is not connected Apr 30 11:13:52 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/apps Transport endpoint is not connected Apr 30 11:13:52 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/backup Transport endpoint is not connected Apr 30 11:13:52 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/cache Transport endpoint is not connected Apr 30 11:13:52 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/docker Transport endpoint is not connected Apr 30 11:13:52 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/downloads Transport endpoint is not connected Apr 30 11:13:52 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/games Transport endpoint is not connected Apr 30 11:13:52 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/movies Transport endpoint is not connected Apr 30 11:13:52 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/music Transport endpoint is not connected Apr 30 11:13:52 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/photos Transport endpoint is not connected Apr 30 11:13:52 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/porn Transport endpoint is not connected Apr 30 11:13:52 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/tv Transport endpoint is not connected Apr 30 11:13:53 vault13 kernel: docker0: port 3(veth77103c7) entered disabled state Apr 30 11:13:53 vault13 kernel: device veth77103c7 left promiscuous mode Apr 30 11:13:53 vault13 kernel: docker0: port 3(veth77103c7) entered disabled state Apr 30 11:13:53 vault13 avahi-daemon[4589]: Withdrawing workstation service for veth77103c7. Apr 30 11:13:55 vault13 emhttp: /usr/bin/docker logs --tail=350 -f Sonarr 2>&1 Apr 30 11:14:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/3dmovies Transport endpoint is not connected Apr 30 11:14:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/anime Transport endpoint is not connected Apr 30 11:14:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/appdata Transport endpoint is not connected Apr 30 11:14:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/apps Transport endpoint is not connected Apr 30 11:14:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/backup Transport endpoint is not connected Apr 30 11:14:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/cache Transport endpoint is not connected Apr 30 11:14:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/docker Transport endpoint is not connected Apr 30 11:14:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/downloads Transport endpoint is not connected Apr 30 11:14:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/games Transport endpoint is not connected Apr 30 11:14:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/movies Transport endpoint is not connected Apr 30 11:14:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/music Transport endpoint is not connected Apr 30 11:14:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/photos Transport endpoint is not connected Apr 30 11:14:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/porn Transport endpoint is not connected Apr 30 11:14:01 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/tv Transport endpoint is not connected Apr 30 11:14:34 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/3dmovies Transport endpoint is not connected Apr 30 11:14:34 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/anime Transport endpoint is not connected Apr 30 11:14:34 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/appdata Transport endpoint is not connected Apr 30 11:14:34 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/apps Transport endpoint is not connected Apr 30 11:14:34 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/backup Transport endpoint is not connected Apr 30 11:14:34 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/cache Transport endpoint is not connected Apr 30 11:14:34 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/docker Transport endpoint is not connected Apr 30 11:14:34 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/downloads Transport endpoint is not connected Apr 30 11:14:34 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/games Transport endpoint is not connected Apr 30 11:14:34 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/movies Transport endpoint is not connected Apr 30 11:14:34 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/music Transport endpoint is not connected Apr 30 11:14:34 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/photos Transport endpoint is not connected Apr 30 11:14:34 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/porn Transport endpoint is not connected Apr 30 11:14:34 vault13 emhttp: get_filesystem_status: statfs: /mnt/user/tv Transport endpoint is not connected
April 30, 201511 yr There is this in your syslog: Apr 29 21:28:49 vault13 kernel: FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
April 30, 201511 yr Author There is this in your syslog: Apr 29 21:28:49 vault13 kernel: FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. that's my vmdk that boots unraid from ssd before switching over to USB, it's always said that.
April 30, 201511 yr Why does your screenshot have /mnt/user/cache in it? Do you actually have a user share named cache? Perhaps created accidentally?
April 30, 201511 yr is that not normal? No. None of the disks should appear in /mnt/user. Seen quite a few examples of users accidentally creating a user share named disk4, for example. What do you have for v /mnt/user
April 30, 201511 yr Author yeah you're right, /mnt/user got bunged up, probably due to the "cache" share adn had weird d???? perms. a reboot seems to have fixed the issue. thanks man
May 1, 201511 yr Just wanted to add myself to the list for this. In my case Needo's Sabnzbd locked up twice and when I try to stop locks up the web ui. One interesting note is I can access the web ui's of my other dockers normally. Also only started with beta 15. Last line of log was a docker stop command issued by GUI.
May 1, 201511 yr Definitely think we have this issue resolved (famous last words...I know) in the next release with the upgrade to Docker 1.6.
May 1, 201511 yr Author I've have great success with using NZBget to replace Sabnzbd in the meantime for those of you experiencing issues. It works fairly well, except i don't really like the app and it's not dealing with older files very well..but it works to keep current tv flowing.
May 2, 201511 yr For anyone experiencing this issue, are you mapping a NFS enabled user share to the container in question? To check, review your volume mappings and see what user shares you are mapping to the container(s) having this problem. Then goto your share settings and see if NFS is on. If so, bonus points would be to turn NFS off for that share and test again to see if this has any impact. Please report back with your results either way.
May 3, 201511 yr Using NFS, but since it happens so irregularly, not sure how long it will be before I will have an answer if it helps.
May 4, 201511 yr I've just had the issue again, this time not running sabnzbd. It's been running for a week, but nzbget has just frozen. Same issue as with sabnzb - docker kill/stop don't stop the process. Unfortunately this time killing the parent docker process didn't restore the web UI. Trying to shutdown manually won't work either, as /mnt/cache won't dismount (because /var/lib/docker is mounted off /mnt/cache), and /var/lib/docker won't unmount either. I ran lsof against /mnt/cache and got - root@behemoth:~# lsof /mnt/cache COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME shfs 8737 root 4u REG 0,30 3 463372 /mnt/cache/appdata/nzbget/downloads/nzbget.lock fuser 23795 root cwd DIR 0,30 46 256 /mnt/cache fuser 23795 root 3r DIR 0,30 46 256 /mnt/cache Killing 8737 worked succesfully, but 23795 wouldn't die even with kill -9. After attempting to kill that process, now neither fuser nor lsof will return any results - when run against any share both commands just hang. I've waited over 5 minutes for both commands to respond with no luck. More details on the 23795 process is below, though I'm not sure what that process belongs to or what started it off. root 23795 0.0 0.0 4564 1740 ? D May02 0:00 fuser -s ./movies/<name of movie>/<name of movie>.sub I've also tried forcing an umount with -f, but no luck there either. Unfortunately I think this means I'll have to force a reboot on the machine without a clean shutdown again... Hopefully the next beta will fix it, is there any ETA on when that will be released, or any way of getting a preview?
May 4, 201511 yr Oh, and forgot to reply to the previous question - I'm not using NFS, nor AFP or FTP. Just SMB via Workgroup with everything public, no user permissions.
May 4, 201511 yr Author yeah my nzbget just crashed too (though it lasted much longer), there must be a common component between nzbget and sab that's causing these issues.
Archived
This topic is now archived and is closed to further replies.