coreos docker0 interface problems
The console of my coreos machine is being flooded with messages about the docker0 interface flapping. Does anyone know what I should look into in order to figure out what configuration error is causing this?
The machine behaves fine and networking does not seem otherwise affected.
Here's a snippet of the flapping messages from my console:
[907407.098127] docker0: port 2(vethcdf7270) entered disabled state
[907418.084440] docker0: port 2(veth555720b) entered blocking state
[907418.085857] docker0: port 2(veth555720b) entered disabled state
[907418.087214] device veth555720b entered promiscuous mode
[907418.088468] IPv6: ADDRCONF(NETDEV_UP): veth555720b: link is not ready
[907418.130820] docker0: port 2(veth555720b) entered disabled state
[907418.152475] device veth555720b left promiscuous mode
[907418.153908] docker0: port 2(veth555720b) entered disabled state
[907429.034502] docker0: port 2(veth4e9c905) entered blocking state
[907429.035925] docker0: port 2(veth4e9c905) entered disabled state
[907429.037437] device veth4e9c905 entered promiscuous mode
[907429.038798] IPv6: ADDRCONF(NETDEV_UP): veth4e9c905: link is not ready
[907429.067458] docker0: port 2(veth4e9c905) entered disabled state
[907429.078632] device veth4e9c905 left promiscuous mode
[907429.079862] docker0: port 2(veth4e9c905) entered disabled state
[907440.081559] docker0: port 2(veth1723699) entered blocking state
[907440.083530] docker0: port 2(veth1723699) entered disabled state
[907440.084934] device veth1723699 entered promiscuous mode
[907440.086237] IPv6: ADDRCONF(NETDEV_UP): veth1723699: link is not ready
The block of repeating messages occurs every 10 seconds.
As a short-term solution, how can I stop receiving these messages on the system console? It makes Lish difficult to use!
1 Reply
mjones
Linode Staff
I'm not quite sure what's causing the messages, but in most cases you can use the following to keep them from being printed to console:
dmesg -D
To enable them again you can use:
dmesg -E
As for the messages themselves, something like this can happen when there's a conflict or misconfiguration with the networking service Docker is using. I found a few references online to the wicd service specifically, though those were in different OSes than you're using. Still, if wicd is running on your Linode you may want to try stopping it to see if that'll fix the problem:
systemctl stop wicd
systemctl restart docker