After a power outage a few days ago, I noticed that my Sonarr Docker app had stopped working.  The dashboard showed that it was running, but I couldn't access the app.  I restarted it but then it wouldn't start back up again.  Convinced my Docker image was corrupted or something, I deleted it and created a new image.  Once that was done, I re-added the containers for Sonarr and Sabnzbd.  Almost as soon as I finished configuring them, the same issue recurred.  This time, both apps will not start.

 

My full diagnostics are attached, but this seems to be the interesting bit from my syslog (to my untrained eye):

 

Aug 29 17:51:42 Tower php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker 'start' 'binhex-sabnzbd'

Aug 29 17:51:42 Tower kernel: device veth30f1af9 entered promiscuous mode

Aug 29 17:51:42 Tower kernel: docker0: port 1(veth30f1af9) entered forwarding state

Aug 29 17:51:42 Tower kernel: docker0: port 1(veth30f1af9) entered forwarding state

Aug 29 17:51:42 Tower avahi-daemon[1462]: Withdrawing workstation service for veth8fe2d57.

Aug 29 17:51:42 Tower kernel: eth0: renamed from veth8fe2d57

Aug 29 17:51:42 Tower kernel: BTRFS warning (device loop0): csum failed ino 13297 off 425984 csum 511199381 expected csum 1006121663

Aug 29 17:51:42 Tower kernel: BTRFS warning (device loop0): csum failed ino 13297 off 438272 csum 3004422239 expected csum 720442631

Aug 29 17:51:42 Tower kernel: veth8fe2d57: renamed from eth0

Aug 29 17:51:42 Tower kernel: docker0: port 1(veth30f1af9) entered disabled state

Aug 29 17:51:42 Tower avahi-daemon[1462]: Withdrawing workstation service for veth8fe2d57.

Aug 29 17:51:42 Tower avahi-daemon[1462]: Withdrawing workstation service for veth30f1af9.

Aug 29 17:51:42 Tower kernel: docker0: port 1(veth30f1af9) entered disabled state

Aug 29 17:51:42 Tower kernel: device veth30f1af9 left promiscuous mode

Aug 29 17:51:42 Tower kernel: docker0: port 1(veth30f1af9) entered disabled state

Aug 29 17:51:45 Tower php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker 'start' 'binhex-sonarr'

Aug 29 17:51:45 Tower kernel: device veth8ae0d66 entered promiscuous mode

Aug 29 17:51:45 Tower kernel: docker0: port 1(veth8ae0d66) entered forwarding state

Aug 29 17:51:45 Tower kernel: docker0: port 1(veth8ae0d66) entered forwarding state

Aug 29 17:51:45 Tower avahi-daemon[1462]: Withdrawing workstation service for veth2643101.

Aug 29 17:51:45 Tower kernel: eth0: renamed from veth2643101

Aug 29 17:51:45 Tower kernel: BTRFS warning (device loop0): csum failed ino 13297 off 425984 csum 511199381 expected csum 1006121663

Aug 29 17:51:45 Tower kernel: BTRFS warning (device loop0): csum failed ino 13297 off 438272 csum 3004422239 expected csum 720442631

Aug 29 17:51:45 Tower kernel: veth2643101: renamed from eth0

Aug 29 17:51:45 Tower kernel: docker0: port 1(veth8ae0d66) entered disabled state

Aug 29 17:51:45 Tower kernel: docker0: port 1(veth8ae0d66) entered disabled state

Aug 29 17:51:45 Tower avahi-daemon[1462]: Withdrawing workstation service for veth2643101.

Aug 29 17:51:45 Tower avahi-daemon[1462]: Withdrawing workstation service for veth8ae0d66.

Aug 29 17:51:45 Tower kernel: device veth8ae0d66 left promiscuous mode

Aug 29 17:51:45 Tower kernel: docker0: port 1(veth8ae0d66) entered disabled state

 

Does anybody know what the heck is going on?  Thanks so much for any help!

tower-diagnostics-20160829-1751.zip

What do you have on the Dashboard - System Status for the 3rd number in flash log docker?

 

 

Here's a screenshot:

 

Flash 2% // Log 2% // Docker 17%

Delete your docker.img file and then re add your apps via CA's previous apps section.  The image is corrupted and deleting it is the easiest way to fix the problem

 

Sent from my LG-D852 using Tapatalk

 

 

Working on it.  I deleted the docker image and created a new one.  The first time I tried to reinstall Sabnzbd using CA Previous Apps, I got this error:

 

Cannot connect to the Docker daemon. Is 'docker -d' running on this host?

 

Second time I tried, I got this error:

 

Tag latest not found in repository binhex/arch-sabnzbd

 

Both times the command failed.

 

Then I tried to install Sonarr the same way:

 

Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 54 Couldn't create socket: [111] Connection refused Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 490 Couldn't create socket: [111] Connection refused

 

Then I got the same error about not connecting to the Docker daemon.

 

I'll keep trying - standby.

I got both Docker containers reinstalled using CA after a few attempts.  Configuring them now.  Last time, they crashed after configuration so we'll see how this goes.

 

UPDATE

 

Sonarr seems to be working fine, but Sabnzbd is acting up.  I can't get to the WebUI at all - "Site can't be reached" errors.  The Docker page says it's running and uninstalling/reinstalling it don't seem to help.

I got both Docker containers reinstalled using CA after a few attempts.  Configuring them now.  Last time, they crashed after configuration so we'll see how this goes.

 

UPDATE

 

Sonarr seems to be working fine, but Sabnzbd is acting up.  I can't get to the WebUI at all - "Site can't be reached" errors.  The Docker page says it's running and uninstalling/reinstalling it don't seem to help.

Doesn't make a lot of sense to me.  After nuking the image and recreating it, you should have been good to go first try.

Sonarr seems to be working fine, but Sabnzbd is acting up.  I can't get to the WebUI at all - "Site can't be reached" errors.  The Docker page says it's running and uninstalling/reinstalling it don't seem to help.

Post your settings for Sab. 

Since yesterday, the issue spread to Sonarr too.  Here are screenshots showing all the settings:

 

 

On the Docker tab, both apps look like they're running.  However, when I try to go to the WebUI, I get "Site can't be reached" errors.

 

This is the same issue I was having before I deleted my docker.img and started over.  Not sure what's causing this.

I don't use these dockers, and I'm not sure it matters, but your volume mappings are a little unusual. Most people have an appdata user share, and their dockers have /config mapped to a subfolder of that share. You instead have mapped your docker's /config in such a way that you actually have a user share for each docker. And you have sonarr's  /config and /data mapped to the same place so it is possible that if /config and /data have common filenames they will be overwriting each other.

 

I also would have to question how you have each application configured. If you have them setup to write data anywhere that you haven't mapped, then they are going to be writing within docker.img, which may be where your corruption is coming from.

 

Have you read the Docker FAQ sticky in this subforum?

Thanks for the feedback.  I nuked my docker.img again, re-added the apps, then I went over the FAQ again and fixed the configurations.  Here's what they look like now:

 

 

Both apps are running again.  I'm not sure what was making them hang before, but hopefully it was my wonky configuration as you pointed out.  I'll report back in a few hours once they've had some time to run and hit whatever snag was happening before.