networking di banchina che si blocca casualmente

A volte, tutte le reti del mio server dedicato sono in freddo (anche ssh non funziona). viene ripetutamente ripetuta.

OS: Ubuntu 14.04.3 LTS

  • Come get "tail -f" che funziona su un file situato in una condivisione di Windows
  • Impostazioni Fail2ban dopo la modifica della port ssh
  • Latenza nelle reti TCP / IP-over-Ethernet
  • Perché la function TCP Chimney Offload su alcune tabs ethernet non riesce a passare alcuni pacchetti di networking al sistema operativo?
  • Creare un sotto-dominio utilizzando Amazon AWS vs Creare il sotto-dominio dall'interno del server - Qual è la differenza?
  • MySQL interroga il sito di hang
  • Sui server binari installati sul server, e vedo nei registri dmesg :

    [1568390.415464] IPv6: ADDRCONF(NETDEV_UP): veth70c3620: link is not ready [1568390.415571] docker0: port 2(vethfd09262) entered forwarding state [1568390.415575] docker0: port 2(vethfd09262) entered forwarding state [1568390.415586] IPv6: ADDRCONF(NETDEV_CHANGE): veth70c3620: link becomes ready [1568390.453889] eth0: renamed from veth70c3620 [1568405.455565] docker0: port 2(vethfd09262) entered forwarding state [1568490.807194] aufs au_opts_verify:1612:docker[22618]: dirperm1 breaks the protection by the permission bits on the lower branch [1568490.839695] aufs au_opts_verify:1612:docker[25041]: dirperm1 breaks the protection by the permission bits on the lower branch [1568490.873185] aufs au_opts_verify:1612:docker[25041]: dirperm1 breaks the protection by the permission bits on the lower branch [1568491.213577] aufs au_opts_verify:1612:docker[25041]: dirperm1 breaks the protection by the permission bits on the lower branch [1568491.248730] aufs au_opts_verify:1612:docker[25041]: dirperm1 breaks the protection by the permission bits on the lower branch [1568491.292433] aufs au_opts_verify:1612:docker[22618]: dirperm1 breaks the protection by the permission bits on the lower branch [1568491.544051] aufs au_opts_verify:1612:docker[22618]: dirperm1 breaks the protection by the permission bits on the lower branch [1568491.571716] aufs au_opts_verify:1612:docker[22618]: dirperm1 breaks the protection by the permission bits on the lower branch [1568491.605760] aufs au_opts_verify:1612:docker[22618]: dirperm1 breaks the protection by the permission bits on the lower branch [1568491.858186] aufs au_opts_verify:1612:docker[25041]: dirperm1 breaks the protection by the permission bits on the lower branch [1568491.885767] aufs au_opts_verify:1612:docker[25041]: dirperm1 breaks the protection by the permission bits on the lower branch [1568491.919876] aufs au_opts_verify:1612:docker[25041]: dirperm1 breaks the protection by the permission bits on the lower branch [1568492.164684] aufs au_opts_verify:1612:docker[25041]: dirperm1 breaks the protection by the permission bits on the lower branch [1568492.197225] aufs au_opts_verify:1612:docker[25041]: dirperm1 breaks the protection by the permission bits on the lower branch [1568492.233425] aufs au_opts_verify:1612:docker[25041]: dirperm1 breaks the protection by the permission bits on the lower branch [1568502.618191] veth70c3620: renamed from eth0 [1568502.653605] docker0: port 2(vethfd09262) entered disabled state [1568502.681529] docker0: port 2(vethfd09262) entered disabled state [1568502.682111] device vethfd09262 left promiscuous mode [1568502.682113] docker0: port 2(vethfd09262) entered disabled state [1568503.037301] aufs au_opts_verify:1612:docker[25411]: dirperm1 breaks the protection by the permission bits on the lower branch [1568503.071988] aufs au_opts_verify:1612:docker[25370]: dirperm1 breaks the protection by the permission bits on the lower branch [1568503.102768] aufs au_opts_verify:1612:docker[4932]: dirperm1 breaks the protection by the permission bits on the lower branch [1568503.103562] device veth6cd39d2 entered promiscuous mode [1568503.103649] IPv6: ADDRCONF(NETDEV_UP): vethffd65cb: link is not ready [1568503.103702] docker0: port 2(veth6cd39d2) entered forwarding state [1568503.103706] docker0: port 2(veth6cd39d2) entered forwarding state [1568503.103719] IPv6: ADDRCONF(NETDEV_CHANGE): vethffd65cb: link becomes ready [1568503.146365] eth0: renamed from vethffd65cb [1568518.132006] docker0: port 2(veth6cd39d2) entered forwarding state 

    Docker informazioni:

     Containers: 40 Images: 538 Storage Driver: aufs Root Dir: /var/lib/docker/aufs Backing Filesystem: extfs Dirs: 618 Dirperm1 Supported: true Execution Driver: native-0.2 Logging Driver: json-file Kernel Version: 3.19.0-25-generic Operating System: Ubuntu 14.04.3 LTS CPUs: 8 Total Memory: 31.29 GiB Name: crosspromo-inpgngno01.xxxxxxx ID: EOO2:DMGR:POHZ:VLKM:6KKZ:DX6S:5XIN:X4DA:22HH:L62N:FCI5:O32P WARNING: No swap limit support 

    uname -a

     Linux crosspromo-inpgngno01.xxxxxxx 3.19.0-25-generic #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux 

    Così: sono i problemi del docker, o forse l'interface uplink è rotta?

    One Solution collect form web for “networking di banchina che si blocca casualmente”

    Stai eseguendo un sistema noto per NON funziona con Docker. A giudicare dall'errore, sta semplicemente schiantando il sistema, ripetutamente.

    • AUFS è instabile e conosciuto per causare panico al kernel.
    • Ubuntu 14 sta eseguendo un vecchio kernel che manca componenti critici per la containerizzazione
    • Vecchia versione di Docker, guidata da bug.

    Puoi iniziare dall'aggiornamento a Ubuntu 16.04 TLS (l'ultima di questa scrittura). Buona fortuna per far funzionare Docker, l'installazione predefinita di solito non lo fa.

    Fondamentalmente, Docker è completamente spezzato e instabile nella maggior parte dei sisthemes. Vedi questi articoli per la versione lunga e drammatica.

    Suggerimenti per Linux e Windows Server, quali Ubuntu, Centos, Apache, Nginx, Debian e argomenti di rete.