is ADDRCONF error cause halt on my server

packets · 02-18-2010, 05:48 PM

I suddenly cannot access my webserver so I decided to put a monitor and I cannot see a console or shell. I decided to restart the server. Then I do some checking on the syslog. Below is the line is saw on syslog

Quote:

Feb 17 11:41:41 LB2 kernel: Removing netfilter NETLINK layer.
Feb 17 11:46:42 LB2 kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x43E1
Feb 17 11:46:46 LB2 kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
Feb 17 11:46:46 LB2 kernel: e1000: eth1: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Feb 17 11:46:46 LB2 kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Feb 17 11:49:49 LB2 kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x43E1
Feb 17 11:49:53 LB2 kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
Feb 17 11:49:54 LB2 kernel: e1000: eth1: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Feb 17 11:49:54 LB2 kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Feb 17 11:54:28 LB2 kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x43E1
Feb 17 11:54:32 LB2 kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
Feb 17 11:54:32 LB2 kernel: e1000: eth1: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Feb 17 11:54:32 LB2 kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Feb 17 11:55:37 LB2 kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Feb 17 13:03:33 LB2 kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x43E1
Feb 17 13:03:37 LB2 kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
Feb 17 13:03:37 LB2 kernel: e1000: eth1: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Feb 17 13:03:37 LB2 kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Feb 17 14:23:41 LB2 kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x43E1
Feb 17 14:23:45 LB2 kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
Feb 17 14:23:45 LB2 kernel: e1000: eth1: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Feb 17 14:23:45 LB2 kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Feb 17 14:28:07 LB2 kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x43E1
Feb 17 14:28:11 LB2 kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
Feb 17 14:28:11 LB2 kernel: e1000: eth1: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Feb 17 14:28:11 LB2 kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Feb 17 14:35:02 LB2 kernel: eth0: link down
Feb 17 14:35:13 LB2 kernel: eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
Feb 17 14:36:36 LB2 kernel: eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
Feb 17 14:36:40 LB2 kernel: e1000: eth1: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX
Feb 17 14:41:31 LB2 kernel: eth0: link down
Feb 17 14:42:30 LB2 kernel: eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
Feb 17 14:43:19 LB2 kernel: Netfilter messages via NETLINK v0.30.
Feb 17 14:43:19 LB2 kernel: ip_conntrack version 2.4 (8192 buckets, 65536 max) - 228 bytes per conntrack
Feb 17 14:44:23 LB2 kernel: eth0: link down
Feb 17 14:46:19 LB2 kernel: eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
Feb 17 14:46:35 LB2 kernel: e1000: eth1: e1000_watchdog_task: NIC Link is Down
Feb 17 14:47:01 LB2 kernel: e1000: eth1: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex, F

I'm not sure if this is relevant to the freezing of the server because its capacitor was replace with a new one before I install CentOS.

Do I have to worry on those logs? 2 days had past after this error appear. So far I haven't see it again but I want to know if this could be the cause of the server hangup? I think server should not be hang because this error is only about network. Am I correct?

business_kid · 02-20-2010, 04:48 AM

Exactly where was the capacitor replaced?
It looks like the nic is negotiating but can't communicate. Have you replaced the nic and whatever was repaired?