Network log?

So it happened again, hopefully I copied the right text from syslog...

Aug 7 23:54:37 Edward NetworkManager[1158]: <info> (eth0): IP6 addrconf timed out or failed.
Aug 7 23:54:37 Edward NetworkManager[1158]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Aug 7 23:54:37 Edward NetworkManager[1158]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Aug 7 23:54:37 Edward NetworkManager[1158]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
 
Is this the same as your other thread? If so, why not just use that one?

Those messages are irrelevant unless you are using IPv6. Have you tried a different cable?
 
lamboman said:
Is this the same as your other thread? If so, why not just use that one?

Those messages are irrelevant unless you are using IPv6. Have you tried a different cable?
Click to expand...

The cable is fine, it works fine after reconnect... Today just a few minutes ago it stopped going anywher & I got this...

eth0: link is not ready
Aug 11 13:19:09 Edward NetworkManager[1163]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Aug 11 13:19:09 Edward NetworkManager[1163]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Aug 11 13:19:09 Edward NetworkManager[1163]: <info> urfkill disappeared from the bus
Aug 11 13:19:09 Edward NetworkManager[1163]: <info> ModemManager available in the bus

Reboot fixed it, just wondering what that came from??? First time I have seen it say that...
 
Last edited:
All these messages are unrelated to the problem I'm afraid. lo is just your local device (127.0.0.1), urfkill is related to disabling wireless devices, ModemManager is just that.

You'll need to post a full log, try a different cable, see if it is a problem on the other side etc. If you aren't getting any bizarre messages in the logs, it's not likely to be a software issue on the machine at least.
 
Sorry with all this that prob. really means nothing, but a min. back I got...
Aug 11 17:26:09 Edward NetworkManager[1161]: <info> (eth0): device state change: activated -> unavailable (reason 'carrier-changed') [100 20 40]
Aug 11 17:26:09 Edward NetworkManager[1161]: <info> (eth0): deactivating device (reason 'carrier-changed') [40]
Aug 11 17:26:09 Edward NetworkManager[1161]: <info> (eth0): canceled DHCP transaction, DHCP client pid 2885
Aug 11 17:26:09 Edward avahi-daemon[933]: Withdrawing address record for 192.168.0.107 on eth0.
Aug 11 17:26:09 Edward avahi-daemon[933]: Leaving mDNS multicast group on interface eth0.IPv4 with address ***.***.*.***.
Aug 11 17:26:09 Edward avahi-daemon[933]: Interface eth0.IPv4 no longer relevant for mDNS.
Aug 11 17:26:09 Edward NetworkManager[1161]: <warn> DNS: plugin dnsmasq update failed
Aug 11 17:26:09 Edward NetworkManager[1161]: <info> Removing DNS information from /sbin/resolvconf
Aug 11 17:26:09 Edward dnsmasq[2300]: setting upstream servers from DBus
Aug 11 17:26:09 Edward NetworkManager[1161]: <info> NetworkManager state is now DISCONNECTED

These are all new, never happened before...
 
"carrier-changed" is due to the link on that device going down. It's likely to be a Layer 1 issue (physical).

Different cable, check ports are clean, check your switch/router is functioning properly, etc.
 
lamboman said:
"carrier-changed" is due to the link on that device going down. It's likely to be a Layer 1 issue (physical).

Different cable, check ports are clean, check your switch/router is functioning properly, etc.
Click to expand...

Thanks, it is reconnected again... What is the best way to see if it is the cable/router/my ethernet port?

I am on wireless now, hopefully this fixes it for good... Checked the wire on a laptop, same thing so prob. a bad wire...
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom