Erro de rede do Ubuntu na inicialização, funciona com reinicialização

Question

Recentemente, em uma reinicialização do sistema, somos forçados a ativar nossa rede inserindo manualmente o comando

/etc/init.d/networking restart

caso contrário, eth0 não está definido ou ativo.

Alguém pode identificar com isso qual é o problema e como podemos resolver isso?

Saída de registros: cat /var/log/messages | grep eth0 (observe que eu o ativei manualmente depois que o login falhou em ter esse conjunto)

Aug 17 13:05:48 sugarbackup-desktop kernel: [    4.216762] eth0: Tigon3 [partno(BCM95784M) rev 5784100 PHY(5784)] (PCI Express) 10/100/1000Base-T Ethernet 00:21:9b:72:90:ac
Aug 17 13:05:48 sugarbackup-desktop kernel: [    4.216766] eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1]
Aug 17 13:05:48 sugarbackup-desktop kernel: [    4.216768] eth0: dma_rwctrl[76180000] dma_mask[64-bit]
Aug 17 13:05:49 sugarbackup-desktop kernel: [   16.814063] tg3: eth0: Link is up at 100 Mbps, full duplex.
Aug 17 13:05:49 sugarbackup-desktop kernel: [   16.814066] tg3: eth0: Flow control is on for TX and on for RX.
Aug 17 14:10:15 sugarbackup-desktop kernel: [    4.228756] eth0: Tigon3 [partno(BCM95784M) rev 5784100 PHY(5784)] (PCI Express) 10/100/1000Base-T Ethernet 00:21:9b:72:90:ac
Aug 17 14:10:15 sugarbackup-desktop kernel: [    4.228761] eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1]
Aug 17 14:10:15 sugarbackup-desktop kernel: [    4.228763] eth0: dma_rwctrl[76180000] dma_mask[64-bit]
Aug 17 14:10:16 sugarbackup-desktop kernel: [   16.805430] tg3: eth0: Link is up at 100 Mbps, full duplex.
Aug 17 14:10:16 sugarbackup-desktop kernel: [   16.805433] tg3: eth0: Flow control is on for TX and on for RX.
Aug 17 15:05:58 sugarbackup-desktop kernel: [    4.244599] eth0: Tigon3 [partno(BCM95784M) rev 5784100 PHY(5784)] (PCI Express) 10/100/1000Base-T Ethernet 00:21:9b:72:90:ac
Aug 17 15:05:58 sugarbackup-desktop kernel: [    4.244603] eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1]
Aug 17 15:05:58 sugarbackup-desktop kernel: [    4.244605] eth0: dma_rwctrl[76180000] dma_mask[64-bit]
Aug 17 15:05:59 sugarbackup-desktop kernel: [   16.738952] tg3: eth0: Link is up at 100 Mbps, full duplex.
Aug 17 15:05:59 sugarbackup-desktop kernel: [   16.738955] tg3: eth0: Flow control is on for TX and on for RX.
Aug 17 15:07:05 sugarbackup-desktop kernel: [  114.555430] ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 17 15:07:07 sugarbackup-desktop kernel: [  116.152273] tg3: eth0: Link is up at 100 Mbps, full duplex.
Aug 17 15:07:07 sugarbackup-desktop kernel: [  116.152278] tg3: eth0: Flow control is on for TX and on for RX.
Aug 17 15:07:07 sugarbackup-desktop kernel: [  116.152889] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Aug 17 15:20:27 sugarbackup-desktop kernel: [    4.212747] eth0: Tigon3 [partno(BCM95784M) rev 5784100 PHY(5784)] (PCI Express) 10/100/1000Base-T Ethernet 00:21:9b:72:90:ac
Aug 17 15:20:27 sugarbackup-desktop kernel: [    4.212751] eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1]
Aug 17 15:20:27 sugarbackup-desktop kernel: [    4.212753] eth0: dma_rwctrl[76180000] dma_mask[64-bit]
Aug 17 15:20:27 sugarbackup-desktop kernel: [   16.797888] tg3: eth0: Link is up at 100 Mbps, full duplex.
Aug 17 15:20:27 sugarbackup-desktop kernel: [   16.797892] tg3: eth0: Flow control is on for TX and on for RX.
Aug 17 15:21:13 sugarbackup-desktop kernel: [   90.723423] ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 17 15:21:15 sugarbackup-desktop kernel: [   92.258276] tg3: eth0: Link is up at 100 Mbps, full duplex.
Aug 17 15:21:15 sugarbackup-desktop kernel: [   92.258282] tg3: eth0: Flow control is on for TX and on for RX.
Aug 17 15:21:15 sugarbackup-desktop kernel: [   92.258450] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Aug 17 15:22:46 sugarbackup-desktop kernel: [  183.595465] ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 17 15:22:48 sugarbackup-desktop kernel: [  185.130353] tg3: eth0: Link is up at 100 Mbps, full duplex.
Aug 17 15:22:48 sugarbackup-desktop kernel: [  185.130359] tg3: eth0: Flow control is on for TX and on for RX.
Aug 17 15:22:48 sugarbackup-desktop kernel: [  185.130527] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Aug 17 16:42:34 sugarbackup-desktop kernel: [    4.228620] eth0: Tigon3 [partno(BCM95784M) rev 5784100 PHY(5784)] (PCI Express) 10/100/1000Base-T Ethernet 00:21:9b:72:90:ac
Aug 17 16:42:34 sugarbackup-desktop kernel: [    4.228623] eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1]
Aug 17 16:42:34 sugarbackup-desktop kernel: [    4.228626] eth0: dma_rwctrl[76180000] dma_mask[64-bit]
Aug 17 16:42:35 sugarbackup-desktop kernel: [   16.843218] tg3: eth0: Link is up at 100 Mbps, full duplex.
Aug 17 16:42:35 sugarbackup-desktop kernel: [   16.843221] tg3: eth0: Flow control is on for TX and on for RX.
Aug 17 16:44:40 sugarbackup-desktop kernel: [  171.575406] ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 17 16:44:42 sugarbackup-desktop kernel: [  173.110268] tg3: eth0: Link is up at 100 Mbps, full duplex.
Aug 17 16:44:42 sugarbackup-desktop kernel: [  173.110275] tg3: eth0: Flow control is on for TX and on for RX.
Aug 17 16:44:42 sugarbackup-desktop kernel: [  173.110764] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Aug 17 17:00:35 sugarbackup-desktop kernel: [ 1126.999527] ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 17 17:00:37 sugarbackup-desktop kernel: [ 1128.714587] tg3: eth0: Link is up at 100 Mbps, full duplex.
Aug 17 17:00:37 sugarbackup-desktop kernel: [ 1128.714593] tg3: eth0: Flow control is on for TX and on for RX.
Aug 17 17:00:37 sugarbackup-desktop kernel: [ 1128.714766] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Aug 18 10:08:33 sugarbackup-desktop kernel: [    4.220739] eth0: Tigon3 [partno(BCM95784M) rev 5784100 PHY(5784)] (PCI Express) 10/100/1000Base-T Ethernet 00:21:9b:72:90:ac
Aug 18 10:08:33 sugarbackup-desktop kernel: [    4.220742] eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1]
Aug 18 10:08:33 sugarbackup-desktop kernel: [    4.220745] eth0: dma_rwctrl[76180000] dma_mask[64-bit]
Aug 18 10:08:34 sugarbackup-desktop kernel: [   16.845252] tg3: eth0: Link is up at 100 Mbps, full duplex.
Aug 18 10:08:34 sugarbackup-desktop kernel: [   16.845255] tg3: eth0: Flow control is on for TX and on for RX.
Aug 18 10:09:34 sugarbackup-desktop kernel: [   94.511408] ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 18 10:09:37 sugarbackup-desktop kernel: [   96.046199] tg3: eth0: Link is up at 100 Mbps, full duplex.
Aug 18 10:09:37 sugarbackup-desktop kernel: [   96.046204] tg3: eth0: Flow control is on for TX and on for RX.
Aug 18 10:09:37 sugarbackup-desktop kernel: [   96.046648] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Aug 18 10:15:25 sugarbackup-desktop kernel: [    4.332749] eth0: Tigon3 [partno(BCM95784M) rev 5784100 PHY(5784)] (PCI Express) 10/100/1000Base-T Ethernet 00:21:9b:72:90:ac
Aug 18 10:15:25 sugarbackup-desktop kernel: [    4.332753] eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1]
Aug 18 10:15:25 sugarbackup-desktop kernel: [    4.332755] eth0: dma_rwctrl[76180000] dma_mask[64-bit]
Aug 18 10:15:26 sugarbackup-desktop kernel: [   17.798590] tg3: eth0: Link is up at 100 Mbps, full duplex.
Aug 18 10:15:26 sugarbackup-desktop kernel: [   17.798594] tg3: eth0: Flow control is on for TX and on for RX.
Aug 18 10:17:36 sugarbackup-desktop kernel: [  172.483750] ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 18 10:17:38 sugarbackup-desktop kernel: [  174.081384] tg3: eth0: Link is up at 100 Mbps, full duplex.
Aug 18 10:17:38 sugarbackup-desktop kernel: [  174.081390] tg3: eth0: Flow control is on for TX and on for RX.
Aug 18 10:17:38 sugarbackup-desktop kernel: [  174.081815] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Aug 18 14:32:47 sugarbackup-desktop kernel: [    3.500752] eth0: Tigon3 [partno(BCM95784M) rev 5784100 PHY(5784)] (PCI Express) 10/100/1000Base-T Ethernet 00:21:9b:72:90:ac
Aug 18 14:32:47 sugarbackup-desktop kernel: [    3.500756] eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1]
Aug 18 14:32:47 sugarbackup-desktop kernel: [    3.500758] eth0: dma_rwctrl[76180000] dma_mask[64-bit]
Aug 18 14:32:48 sugarbackup-desktop kernel: [   16.803614] tg3: eth0: Link is up at 100 Mbps, full duplex.
Aug 18 14:32:48 sugarbackup-desktop kernel: [   16.803617] tg3: eth0: Flow control is on for TX and on for RX.
Aug 18 14:33:37 sugarbackup-desktop kernel: [   91.987489] ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 18 14:33:38 sugarbackup-desktop kernel: [   93.522265] tg3: eth0: Link is up at 100 Mbps, full duplex.
Aug 18 14:33:38 sugarbackup-desktop kernel: [   93.522271] tg3: eth0: Flow control is on for TX and on for RX.
Aug 18 14:33:38 sugarbackup-desktop kernel: [   93.522597] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

root@sugarbackup-desktop:~# find /etc/rc*.d/*Netw*
/etc/rc2.d/S28NetworkManager
/etc/rc3.d/S28NetworkManager
/etc/rc4.d/S28NetworkManager
/etc/rc5.d/S28NetworkManager

root@sugarbackup-desktop:~# find /etc/rc*.d/*netw*
/etc/rc0.d/S35networking
/etc/rc6.d/S35networking
/etc/rcS.d/S40networking    

> 
# aptitude reinstall network-manager
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Reading extended state information      
Initializing package states... Done
The following packages will be REINSTALLED:
  network-manager 
The following packages will be REMOVED:
  libbsd-resource-perl{u} linux-headers-2.6.27-7{u} 
  linux-headers-2.6.27-7-generic{u} 
0 packages upgraded, 0 newly installed, 1 reinstalled, 3 to remove and 209 not upgraded.
Need to get 0B of archives. After unpacking 52.2MB will be freed.
Do you want to continue? [Y/n/?] y
E: I wasn't able to locate file for the network-manager package. This might mean you need to manually fix this package.
Writing extended state information... Done
E: I wasn't able to locate file for the network-manager package. This might mean you need to manually fix this package.
E: Internal error: couldn't generate list of packages to downloa

    

Answer 1

Você pode verificar as seguintes coisas: - Verifique se há problemas com a obtenção do IP através do DHCP. - No meu Ubuntu-9.04, é eth1 (não eth0 é criado). - Pode haver uma condição de corrida acontecendo durante a inicialização ... devido a qual A interface pode ser criada após a ativação da rede.

    

Answer 2

Obviamente, mais detalhes ajudariam aqui, verifique seus logs para qualquer menção de eth0 com

%pr_e%

Se você pudesse adicionar a saída do comando /etc/init.d/networking restart à sua pergunta, isso também ajudaria. Como sudeshpawar disse, isso poderia ser uma falha do DHCP em atribuir um endereço a tempo.

Pode ser que o serviço NetworkManager não esteja sendo iniciado, mas sem a saída log / dmesg é difícil dizer.

Ativando e desativando serviços durante a inicialização no GNU / Linux

Ubuntu / Debian Linux: Ferramenta de configuração de serviços para iniciar / parar o sistema Serviços

Verifique se o serviço NetworkManager é iniciado no momento da inicialização com o seguinte comando:

%pr_e%

Da sua saída / var / log / messages, podemos ver que o eth0 aparece durante o boot após 16 segundos. Eu suponho que a próxima atividade é você reiniciar o serviço de rede.

# cat /var/log/messages | grep eth0

A saída do comando find também parece correta, a única diferença da minha é a 28 que é simplesmente usada para indicar a sequência na qual todos os scripts init são iniciados.

%pr_e%

A única área a verificar é a ferramenta do gerenciador de rede da GUI. Se você estiver usando o GNOME, clique com o botão direito do mouse no ícone do gerenciador de rede, selecione Editar conexões, destaque eth0 e selecione Editar e certifique-se de que a caixa Conectar automaticamente esteja marcada.

Seissoaindanãocorrigirascoisas,posteasaídadoseguintecomandologoapósainicialização.

#find/etc/rc*.d/Network/etc/rc2.d/S50NetworkManager/etc/rc3.d/S50NetworkManager/etc/rc4.d/S50NetworkManager/etc/rc5.d/S50NetworkManager

saída

Aug1814:32:47sugarbackup-desktopkernel:[3.500752]eth0:Tigon3[partno(BCM95784M)rev5784100PHY(5784)](PCIExpress)10/100/1000Base-TEthernet00:21:9b:72:90:acAug1814:32:47sugarbackup-desktopkernel:[3.500756]eth0:RXcsums[1]LinkChgREG[0]MIirq[0]ASF[0]WireSpeed[1]TSOcap[1]Aug1814:32:47sugarbackup-desktopkernel:[3.500758]eth0:dma_rwctrl[76180000]dma_mask[64-bit]Aug1814:32:48sugarbackup-desktopkernel:[16.803614]tg3:eth0:Linkisupat100Mbps,fullduplex.Aug1814:32:48sugarbackup-desktopkernel:[16.803617]tg3:eth0:FlowcontrolisonforTXandonforRX.Aug1814:33:37sugarbackup-desktopkernel:[91.987489]ADDRCONF(NETDEV_UP):eth0:linkisnotreadyAug1814:33:38sugarbackup-desktopkernel:[93.522265]tg3:eth0:Linkisupat100Mbps,fullduplex.Aug1814:33:38sugarbackup-desktopkernel:[93.522271]tg3:eth0:FlowcontrolisonforTXandonforRX.Aug1814:33:38sugarbackup-desktopkernel:[93.522597]ADDRCONF(NETDEV_CHANGE):eth0:linkbecomesready

VocêpodereinstalaronetworkmanagerOUinstalarumsubstitutocomooWICD.

Parareinstalaronetworkmanager,executeoseguintecomando

%pr_e%

SevocêestiverexecutandooUbuntu9.04(Jaunty),simplesmenteexecuteestecomandoparainstalaroWICD

%pr_e%

casocontrário,sigaoguia aqui

    

Answer 3

O que acontece quando você tenta reiniciar a pilha da rede?

/etc/init.d/networking restart

Além disso, como você está configurado com um IP estático, você está conectado a um roteador que está tentando distribuir endereços DHCP? Em caso afirmativo, você pode desativar o DHCP no roteador e simplesmente atuar como um gateway?

Isso pode ser parte do motivo pelo qual você não está recebendo tráfego. Até onde você não pode trazer o cartão, verifique se os drivers estão instalados. modprobe o driver no kernel e tente ifconfig eth0 static 192.168.0.X up . ( x é uma variável para representar endereços IP diferentes).

Não use o gerenciador de rede, ele não funciona e não é necessário. Na verdade, o gerenciador de rede geralmente não configura corretamente o subsistema Linux, que é diretamente responsável pelo gerenciamento da sua pilha de rede.