Linode running Docker keeps becoming unresponsive
Linode
Linode Staff
My Linode keeps becoming unresponsive. It runs Docker and I am seeing the following messages on my console log:
[ 18.501513] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)
[ 18.512782] br-0ea93a274d5d: port 1(veth3efa949) entered blocking state
[ 18.514123] br-0ea93a274d5d: port 1(veth3efa949) entered disabled state
[ 18.516916] device veth3efa949 entered promiscuous mode
[ 18.523052] br-0ea93a274d5d: port 1(veth3efa949) entered blocking state
[ 18.524349] br-0ea93a274d5d: port 1(veth3efa949) entered forwarding state
[ 18.528912] br-0ea93a274d5d: port 1(veth3efa949) entered disabled state
[ 18.560360] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
[ 18.568269] br-0ea93a274d5d: port 2(veth658cec9) entered blocking state
[ 18.569687] br-0ea93a274d5d: port 2(veth658cec9) entered disabled state
[ 18.573752] device veth658cec9 entered promiscuous mode
[ 18.581739] br-0ea93a274d5d: port 2(veth658cec9) entered blocking state
[ 18.583081] br-0ea93a274d5d: port 2(veth658cec9) entered forwarding state
[ 18.588661] IPv6: ADDRCONF(NETDEV_CHANGE): br-0ea93a274d5d: link becomes ready
[ 18.590564] br-0ea93a274d5d: port 2(veth658cec9) entered disabled state
[ 18.650611] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
[ 18.660205] br-0ea93a274d5d: port 3(vethd2fd2e2) entered blocking state
[ 18.668203] br-0ea93a274d5d: port 3(vethd2fd2e2) entered disabled state
[ 18.671454] device vethd2fd2e2 entered promiscuous mode
[ 18.689021] br-0ea93a274d5d: port 3(vethd2fd2e2) entered blocking state
[ 18.690346] br-0ea93a274d5d: port 3(vethd2fd2e2) entered forwarding state
[ 18.724445] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
[ 18.766747] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
[ 18.797678] docker0: port 1(veth39a2f3d) entered blocking state
[ 18.800512] docker0: port 1(veth39a2f3d) entered disabled state
I'm trying to back this Linode up with rsync, but it keeps freezing with without explaination.
3 Replies
hphillips
Linode Staff
It looks like your Linode may be having problems keeping a stable network connection due to the repeated disabling and enabling of interfaces. Based on your console log, the following Reddit post suggests that this may be due to a container that keeps stopping and starting:
You may want to investigate your Docker log files to see which container keeps starting and stopping. Here is an article that talks about reviewing your Docker logs:
According to this article (assuming that you are running Debian) you can check them with the following command:
tail -f -n 1000 /var/log/daemon.log | grep --color docker
Backing Up Your Disk
You will want to to boot your Linode into Rescue Mode and mount your filesystem to /media/sda.
You should then be able to use rsync to backup your files without interference from your interfaces going up and down.
Other backup methods are covered here:
Hi, is there clear reason that docker containers restarted frequently cause host machine unresponsive, is it related kernel or hardware? why net devices enable/disable make host unavaiable?
I had this problem. I reinstalled Mastodon. A couple days later this problem started again. During those operational days I did not take Mastodon down. I did not do anything to the containers. In fact I never connected SSH to do anything aside from initial configuration. Any changes I made were made using the admin panel in Mastodon. Please advise.