January 28, 201610 yr One of my dockers was unresponsive tonight, so I decided to shutdown the docker and restart it. It failed to start, so I then disabled the docker daemon and tried to restart it. It will not start up now. Below is what I get in the sys log when I try to start the docker daemon. Jan 28 00:55:52 Tower kernel: BTRFS info (device loop0): disk space caching is enabled Jan 28 00:55:52 Tower kernel: BTRFS: has skinny extents Jan 28 00:55:52 Tower logger: Resize '/var/lib/docker' of 'max' Jan 28 00:55:52 Tower logger: starting docker ... Jan 28 00:55:52 Tower kernel: BTRFS: new size for /dev/loop0 is 21474836480 Jan 28 00:56:18 Tower logger: Updating templates... Updating info... Jan 28 00:56:18 Tower logger: 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 Jan 28 00:56:18 Tower logger: Couldn't create socket: [111] Connection refused Done. Any ideas? I wasn't working on the server or doing anything when this happened. Seemed to come out of the "Blue"
January 28, 201610 yr Author I tried increasing the docker image size, but that didn't do the trick. Jan 28 08:51:54 Tower logger: stopping docker ... Jan 28 08:51:57 Tower php: /usr/local/emhttp/plugins/dynamix.docker.manager/event/started Jan 28 08:51:57 Tower kernel: BTRFS info (device loop0): disk space caching is enabled Jan 28 08:51:57 Tower kernel: BTRFS: has skinny extents Jan 28 08:51:57 Tower logger: Resize '/var/lib/docker' of 'max' Jan 28 08:51:57 Tower logger: starting docker ... Jan 28 08:51:57 Tower kernel: BTRFS: new size for /dev/loop0 is 21474836480 Jan 28 08:52:24 Tower logger: Updating templates... Updating info... Jan 28 08:52:24 Tower logger: 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 Jan 28 08:52:24 Tower logger: Couldn't create socket: [111] Connection refused Done. Jan 28 09:00:10 Tower php: /usr/local/emhttp/plugins/dynamix.docker.manager/event/stopping_svcs Jan 28 09:00:10 Tower logger: stopping docker ... Jan 28 09:00:10 Tower logger: unmounting docker loopback Jan 28 09:00:21 Tower php: /usr/local/emhttp/plugins/dynamix.docker.manager/event/started Jan 28 09:00:22 Tower kernel: BTRFS info (device loop0): disk space caching is enabled Jan 28 09:00:22 Tower kernel: BTRFS: has skinny extents Jan 28 09:00:22 Tower kernel: BTRFS: new size for /dev/loop0 is 26843545600 Jan 28 09:00:22 Tower logger: Resize '/var/lib/docker' of 'max' Jan 28 09:00:22 Tower logger: starting docker ... Jan 28 09:00:48 Tower logger: Updating templates... Updating info... Jan 28 09:00:48 Tower logger: 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 Jan 28 09:00:48 Tower logger: Couldn't create socket: [111] Connection refused Done. The docker size is currently set at 25G. Docker image location: /mnt/cache/appdata/docker.img (has been working for about 6 months like this and just stopped all the sudden last night and provides the above errors in the sys log).
January 28, 201610 yr Author I "nuked" the docker image (deleted it). I created a new one and it started right up. It must have become corrupt or something. A bit disappointing to have to baby sit docker like that. I've got to try and figure out what happened. Maybe logs filled it up and then at low space something weird could have happened causing it to currupt. I'm going to keep an eye on it and see where the culprit is, assuming that's what happened.
January 28, 201610 yr Community Expert See this thread for some ideas on what you might need to do to fix your setup. See this thread for a method for cleaning things up.
February 1, 201610 yr Author Thank you very much. I've narrowed it down to headphones and couchpotato causing all the excessive logs. I cleared them and in about a week they were about 10MB, which isn't terribly bad. They were about 7GB before I cleared them. I suppose I'll log on and clear the logs once in a while, that's not so bad. Maybe create a cron or something to do it once a week or so.
Archived
This topic is now archived and is closed to further replies.