Well this is weird. I restarted my dual boot Win7/Ubuntu 10.10 from ubuntu to windows. Everything was working fine and windows is always connecting properly to my lan. After restarting back into Ubuntu, all of a sudden I can't connect to my network. It looks as if its trying to connect through ipv6, which this network is not. I used someones advice on how to disable the ipv6 cause whenever I do ifconfig on my ubuntu it gives the following:
Sorry I can't write the whole thing but but its too long to copy it over from that computer. You can see that it addresses ipv6 still. I even have it disabled in network preferences.
I don't know what is going on!
Any help would be appreciated.
Thanks
That ipv6 stuff is always there, it doesn't mean its actually working.
1 Like
Oh okay...
Any ideas on how to check where the problem is coming from. I mean Windows has no problem connecting on the same computer so i know it's not a hardware or cable issue. Ubuntu was working fine up until days ago. The only thing that could affect it was that I installed a fresh version of the system recently. However, it worked fine for days since the reinstall.
Thanks,
Any suspicious entries in dmesg, /var/log/messages or /var/log/daemon.log?
1 Like
Daemon logs are a little strange. I was looking at them and the one that was zipped and rotated by the system has info about networking until April 24th. The next one that was rotated but not zipped yet has something saying:
I don't really know how to identify problems that good as of yet in the logs so if you can tell me what to look for it would be beneficial.
Thanks
Servus,
Please start the following command in a separate console:
$ sudo tail -f /var/log/daemon.log
Then activate the network interface.
Could you please paste the output seen in the console?
TIA, Lo�c
Sorry silly question,
How do I activate the network interface?
---------- Post updated at 04:30 PM ---------- Previous update was at 04:24 PM ----------
Sorry figured it out,
Apologies
One second to transfer log output...
---------- Post updated at 04:48 PM ---------- Previous update was at 04:30 PM ----------
Here it is. I had to stop the interface and then I restarted it:
sudo tail -f /var/log/daemon.log
[sudo] password for izivanov:
May 2 16:25:26 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
May 2 16:25:26 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Timeout) complete.
May 2 16:25:26 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
May 2 16:25:26 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) failed (no IP configuration found)
May 2 16:25:26 rti-is019-con NetworkManager[1237]: <info> (eth0): device state change: 7 -> 9 (reason 5)
May 2 16:25:26 rti-is019-con NetworkManager[1237]: <info> Marking connection 'root01.org ' invalid.
May 2 16:25:26 rti-is019-con NetworkManager[1237]: <warn> Activation (eth0) failed.
May 2 16:25:26 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
May 2 16:25:26 rti-is019-con NetworkManager[1237]: <info> (eth0): device state change: 9 -> 3 (reason 0)
May 2 16:25:26 rti-is019-con NetworkManager[1237]: <info> (eth0): deactivating device (reason: 0).
May 2 16:28:17 rti-is019-con dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 1676
May 2 16:28:17 rti-is019-con dhclient: killed old client process, removed PID file
May 2 16:28:17 rti-is019-con dhclient: Internet Systems Consortium DHCP Client V3.1.3
May 2 16:28:17 rti-is019-con dhclient: Copyright 2004-2009 Internet Systems Consortium.
May 2 16:28:17 rti-is019-con dhclient: All rights reserved.
May 2 16:28:17 rti-is019-con dhclient: For info, please visit ISC DHCP - ISC
May 2 16:28:17 rti-is019-con dhclient:
May 2 16:28:17 rti-is019-con dhclient: Listening on LPF/eth0/f0:4d:a2:db:e1:d2
May 2 16:28:17 rti-is019-con dhclient: Sending on LPF/eth0/f0:4d:a2:db:e1:d2
May 2 16:28:17 rti-is019-con dhclient: Sending on Socket/fallback
May 2 16:28:18 rti-is019-con dhclient: DHCPRELEASE on eth0 to 10.70.25.25 port 67
May 2 16:28:18 rti-is019-con dhclient: send_packet: Network is unreachable
May 2 16:28:18 rti-is019-con dhclient: send_packet: please consult README file regarding broadcast address.
May 2 16:28:18 rti-is019-con avahi-daemon[1136]: Interface eth0.IPv6 no longer relevant for mDNS.
May 2 16:28:18 rti-is019-con avahi-daemon[1136]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::f24d:a2ff:fedb:e1d2.
May 2 16:28:18 rti-is019-con avahi-daemon[1136]: Withdrawing address record for fe80::f24d:a2ff:fedb:e1d2 on eth0.
May 2 16:28:18 rti-is019-con NetworkManager[1237]: <info> (eth0): carrier now OFF (device state 3)
May 2 16:28:18 rti-is019-con NetworkManager[1237]: <info> (eth0): device state change: 3 -> 2 (reason 40)
May 2 16:28:18 rti-is019-con NetworkManager[1237]: <info> (eth0): deactivating device (reason: 40).
May 2 16:28:29 rti-is019-con dhclient: Internet Systems Consortium DHCP Client V3.1.3
May 2 16:28:29 rti-is019-con dhclient: Copyright 2004-2009 Internet Systems Consortium.
May 2 16:28:29 rti-is019-con dhclient: All rights reserved.
May 2 16:28:29 rti-is019-con dhclient: For info, please visit ISC DHCP - ISC
May 2 16:28:29 rti-is019-con dhclient:
May 2 16:28:29 rti-is019-con dhclient: Listening on LPF/eth0/f0:4d:a2:db:e1:d2
May 2 16:28:29 rti-is019-con dhclient: Sending on LPF/eth0/f0:4d:a2:db:e1:d2
May 2 16:28:29 rti-is019-con dhclient: Sending on Socket/fallback
May 2 16:28:29 rti-is019-con dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
May 2 16:28:32 rti-is019-con dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
May 2 16:28:32 rti-is019-con NetworkManager[1237]: <info> (eth0): carrier now ON (device state 2)
May 2 16:28:32 rti-is019-con NetworkManager[1237]: <info> (eth0): device state change: 2 -> 3 (reason 40)
May 2 16:28:34 rti-is019-con avahi-daemon[1136]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::f24d:a2ff:fedb:e1d2.
May 2 16:28:34 rti-is019-con avahi-daemon[1136]: New relevant interface eth0.IPv6 for mDNS.
May 2 16:28:34 rti-is019-con avahi-daemon[1136]: Registering new address record for fe80::f24d:a2ff:fedb:e1d2 on eth0.*.
May 2 16:28:39 rti-is019-con dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
May 2 16:28:48 rti-is019-con dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
May 2 16:28:57 rti-is019-con dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
May 2 16:29:07 rti-is019-con dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
May 2 16:29:21 rti-is019-con dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
May 2 16:29:21 rti-is019-con dhclient: DHCPOFFER of 10.70.29.178 from 10.70.31.252
May 2 16:29:21 rti-is019-con dhclient: DHCPREQUEST of 10.70.29.178 on eth0 to 255.255.255.255 port 67
May 2 16:29:21 rti-is019-con dhclient: DHCPACK of 10.70.29.178 from 10.70.31.252
May 2 16:29:21 rti-is019-con avahi-daemon[1136]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.70.29.178.
May 2 16:29:21 rti-is019-con avahi-daemon[1136]: New relevant interface eth0.IPv4 for mDNS.
May 2 16:29:21 rti-is019-con avahi-daemon[1136]: Registering new address record for 10.70.29.178 on eth0.IPv4.
May 2 16:29:21 rti-is019-con avahi-daemon[1136]: Withdrawing address record for 10.70.29.178 on eth0.
May 2 16:29:21 rti-is019-con avahi-daemon[1136]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.70.29.178.
May 2 16:29:21 rti-is019-con avahi-daemon[1136]: Interface eth0.IPv4 no longer relevant for mDNS.
May 2 16:29:21 rti-is019-con avahi-daemon[1136]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.70.29.178.
May 2 16:29:21 rti-is019-con avahi-daemon[1136]: New relevant interface eth0.IPv4 for mDNS.
May 2 16:29:21 rti-is019-con avahi-daemon[1136]: Registering new address record for 10.70.29.178 on eth0.IPv4.
May 2 16:29:21 rti-is019-con dhclient: bound to 10.70.29.178 -- renewal in 263731 seconds.
May 2 16:29:29 rti-is019-con ntpdate[1886]: adjust time server 91.189.94.4 offset -0.051539 sec
AFAICS, dhcp seems to work as you obtain the IP address 10.70.29.178 from our server 10.70.31.252.
I am a bit surprised however that - once NetworkManager obtains the IP - it does not continue with the registration. Is there perhaps a few more entries after May 2 16:29:29 (ideally, until NetworkManager says that the IP failed)?
Another thought: Could you check the configuration for the interface eth0:
right click on the NetworkManager icon (that shows the network connection)
edit connection
select eth0
select Edit...
go to the tab IPv4 Settings. Make sure that the method selected is DHCP
go to the tab IPv6 Settings. Make sure that the method selected is ignore
eventually save your changes "Apply..."
Lo�c
1 Like
Yeah,
That part is done correctly. I am now logged in as root and still the same problem. I have repeated the procedure and it looks that at the end of the process dhclient has permission problems. I have highlighted it and another failed flag in red.
tail -f /var/log/daemon.log
May 3 08:16:20 rti-is019-con gdm-session-worker[2650]: WARNING: Unable to load file '/etc/gdm/custom.conf': No such file or directory
May 3 08:16:20 rti-is019-con rtkit-daemon[1340]: Successfully made thread 2656 of process 2656 (n/a) owned by '113' high priority at nice level -11.
May 3 08:16:20 rti-is019-con rtkit-daemon[1340]: Supervising 4 threads of 2 processes of 2 users.
May 3 08:16:20 rti-is019-con gdm-simple-greeter[2648]: Gtk-WARNING: /build/buildd/gtk+2.0-2.22.0/gtk/gtkwidget.c:5684: widget not within a GtkWindow
May 3 08:16:20 rti-is019-con rtkit-daemon[1340]: Successfully made thread 2667 of process 2656 (n/a) owned by '113' RT at priority 5.
May 3 08:16:20 rti-is019-con rtkit-daemon[1340]: Supervising 5 threads of 2 processes of 2 users.
May 3 08:16:20 rti-is019-con rtkit-daemon[1340]: Successfully made thread 2668 of process 2656 (n/a) owned by '113' RT at priority 5.
May 3 08:16:20 rti-is019-con rtkit-daemon[1340]: Supervising 6 threads of 2 processes of 2 users.
May 3 08:16:23 rti-is019-con gdm-session-worker[2650]: GLib-GObject-CRITICAL: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed
May 3 08:16:29 rti-is019-con gnome-session[2695]: EggSMClient-WARNING: Desktop file '/root/.config/autostart/cairo-dock-cairo.desktop' has malformed Icon key 'cairo-dock.svg'(should not include extension)
May 3 08:17:39 rti-is019-con dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 1851
May 3 08:17:39 rti-is019-con dhclient: killed old client process, removed PID file
May 3 08:17:39 rti-is019-con dhclient: Internet Systems Consortium DHCP Client V3.1.3
May 3 08:17:39 rti-is019-con dhclient: Copyright 2004-2009 Internet Systems Consortium.
May 3 08:17:39 rti-is019-con dhclient: All rights reserved.
May 3 08:17:39 rti-is019-con dhclient: For info, please visit ISC DHCP - ISC
May 3 08:17:39 rti-is019-con dhclient:
May 3 08:17:39 rti-is019-con dhclient: Listening on LPF/eth0/f0:4d:a2:db:e1:d2
May 3 08:17:39 rti-is019-con dhclient: Sending on LPF/eth0/f0:4d:a2:db:e1:d2
May 3 08:17:39 rti-is019-con dhclient: Sending on Socket/fallback
May 3 08:17:39 rti-is019-con dhclient: DHCPRELEASE on eth0 to 10.70.25.25 port 67
May 3 08:17:39 rti-is019-con dhclient: send_packet: Network is unreachable
May 3 08:17:39 rti-is019-con dhclient: send_packet: please consult README file regarding broadcast address.
May 3 08:17:39 rti-is019-con avahi-daemon[1136]: Interface eth0.IPv6 no longer relevant for mDNS.
May 3 08:17:39 rti-is019-con avahi-daemon[1136]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::f24d:a2ff:fedb:e1d2.
May 3 08:17:39 rti-is019-con avahi-daemon[1136]: Withdrawing address record for fe80::f24d:a2ff:fedb:e1d2 on eth0.
May 3 08:17:39 rti-is019-con NetworkManager[1237]: <info> (eth0): carrier now OFF (device state 3)
May 3 08:17:39 rti-is019-con NetworkManager[1237]: <info> (eth0): device state change: 3 -> 2 (reason 40)
May 3 08:17:39 rti-is019-con NetworkManager[1237]: <info> (eth0): deactivating device (reason: 40).
May 3 08:17:48 rti-is019-con dhclient: Internet Systems Consortium DHCP Client V3.1.3
May 3 08:17:48 rti-is019-con dhclient: Copyright 2004-2009 Internet Systems Consortium.
May 3 08:17:48 rti-is019-con dhclient: All rights reserved.
May 3 08:17:48 rti-is019-con dhclient: For info, please visit ISC DHCP - ISC
May 3 08:17:48 rti-is019-con dhclient:
May 3 08:17:48 rti-is019-con dhclient: Listening on LPF/eth0/f0:4d:a2:db:e1:d2
May 3 08:17:48 rti-is019-con dhclient: Sending on LPF/eth0/f0:4d:a2:db:e1:d2
May 3 08:17:48 rti-is019-con dhclient: Sending on Socket/fallback
May 3 08:17:48 rti-is019-con dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
May 3 08:17:51 rti-is019-con dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
May 3 08:17:52 rti-is019-con NetworkManager[1237]: <info> (eth0): carrier now ON (device state 2)
May 3 08:17:52 rti-is019-con NetworkManager[1237]: <info> (eth0): device state change: 2 -> 3 (reason 40)
May 3 08:17:54 rti-is019-con avahi-daemon[1136]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::f24d:a2ff:fedb:e1d2.
May 3 08:17:54 rti-is019-con avahi-daemon[1136]: New relevant interface eth0.IPv6 for mDNS.
May 3 08:17:54 rti-is019-con avahi-daemon[1136]: Registering new address record for fe80::f24d:a2ff:fedb:e1d2 on eth0.*.
May 3 08:17:57 rti-is019-con dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
May 3 08:18:11 rti-is019-con dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20
May 3 08:18:31 rti-is019-con dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
May 3 08:18:31 rti-is019-con dhclient: DHCPOFFER of 10.70.29.178 from 10.70.31.253
May 3 08:18:31 rti-is019-con dhclient: DHCPREQUEST of 10.70.29.178 on eth0 to 255.255.255.255 port 67
May 3 08:18:31 rti-is019-con dhclient: DHCPACK of 10.70.29.178 from 10.70.31.253
May 3 08:18:31 rti-is019-con avahi-daemon[1136]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.70.29.178.
May 3 08:18:31 rti-is019-con avahi-daemon[1136]: New relevant interface eth0.IPv4 for mDNS.
May 3 08:18:31 rti-is019-con avahi-daemon[1136]: Registering new address record for 10.70.29.178 on eth0.IPv4.
May 3 08:18:31 rti-is019-con avahi-daemon[1136]: Withdrawing address record for 10.70.29.178 on eth0.
May 3 08:18:31 rti-is019-con avahi-daemon[1136]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.70.29.178.
May 3 08:18:31 rti-is019-con avahi-daemon[1136]: Interface eth0.IPv4 no longer relevant for mDNS.
May 3 08:18:31 rti-is019-con avahi-daemon[1136]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.70.29.178.
May 3 08:18:31 rti-is019-con avahi-daemon[1136]: New relevant interface eth0.IPv4 for mDNS.
May 3 08:18:31 rti-is019-con avahi-daemon[1136]: Registering new address record for 10.70.29.178 on eth0.IPv4.
May 3 08:18:31 rti-is019-con dhclient: bound to 10.70.29.178 -- renewal in 344655 seconds.
May 3 08:18:47 rti-is019-con ntpdate[3083]: step time server 91.189.94.4 offset 3.272073 sec
May 3 08:19:32 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) starting connection 'Auto eth0'
May 3 08:19:32 rti-is019-con NetworkManager[1237]: <info> (eth0): device state change: 3 -> 4 (reason 0)
May 3 08:19:32 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
May 3 08:19:32 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
May 3 08:19:32 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
May 3 08:19:32 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
May 3 08:19:32 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
May 3 08:19:32 rti-is019-con NetworkManager[1237]: <info> (eth0): device state change: 4 -> 5 (reason 0)
May 3 08:19:32 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
May 3 08:19:32 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
May 3 08:19:32 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
May 3 08:19:32 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
May 3 08:19:32 rti-is019-con NetworkManager[1237]: <info> (eth0): device state change: 5 -> 7 (reason 0)
May 3 08:19:32 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
May 3 08:19:32 rti-is019-con NetworkManager[1237]: <info> dhclient started with pid 3108
May 3 08:19:32 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
May 3 08:19:32 rti-is019-con dhclient: Internet Systems Consortium DHCP Client V3.1.3
May 3 08:19:32 rti-is019-con dhclient: Copyright 2004-2009 Internet Systems Consortium.
May 3 08:19:32 rti-is019-con dhclient: All rights reserved.
May 3 08:19:32 rti-is019-con dhclient: For info, please visit ISC DHCP - ISC
May 3 08:19:32 rti-is019-con dhclient:
May 3 08:19:32 rti-is019-con dhclient: /var/run/nm-dhclient-eth0.conf line 7: semicolon expected.
May 3 08:19:32 rti-is019-con dhclient: also request
May 3 08:19:32 rti-is019-con dhclient: ^
May 3 08:19:32 rti-is019-con dhclient: /var/run/nm-dhclient-eth0.conf line 8: semicolon expected.
May 3 08:19:32 rti-is019-con dhclient: also
May 3 08:19:32 rti-is019-con dhclient: ^
May 3 08:19:32 rti-is019-con dhclient: /var/run/nm-dhclient-eth0.conf line 9: semicolon expected.
May 3 08:19:32 rti-is019-con dhclient: also request
May 3 08:19:32 rti-is019-con dhclient: ^
May 3 08:19:32 rti-is019-con dhclient: /var/run/nm-dhclient-eth0.conf line 10: semicolon expected.
May 3 08:19:32 rti-is019-con dhclient: also
May 3 08:19:32 rti-is019-con dhclient: ^
May 3 08:19:32 rti-is019-con dhclient: can't create /usr/local/var/lib/dhcp3/dhclient-1537db51-4a51-4dd4-b512-c779f0b420ee-eth0.lease: No such file or directory
May 3 08:19:32 rti-is019-con dhclient: execve (/usr/local/libexec/nm-dhcp-client.action, ...): Permission denied
May 3 08:19:32 rti-is019-con dhclient: Listening on LPF/eth0/f0:4d:a2:db:e1:d2
May 3 08:19:32 rti-is019-con dhclient: Sending on LPF/eth0/f0:4d:a2:db:e1:d2
May 3 08:19:32 rti-is019-con dhclient: Sending on Socket/fallback
May 3 08:19:32 rti-is019-con dhclient: Can't create /usr/local/var/run/dhclient-eth0.pid: Permission denied
May 3 08:19:32 rti-is019-con dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
May 3 08:19:32 rti-is019-con dhclient: DHCPOFFER of 10.70.29.178 from 10.70.31.253
May 3 08:19:32 rti-is019-con dhclient: DHCPREQUEST of 10.70.29.178 on eth0 to 255.255.255.255 port 67
May 3 08:19:32 rti-is019-con dhclient: DHCPACK of 10.70.29.178 from 10.70.31.253
May 3 08:19:32 rti-is019-con dhclient: execve (/usr/local/libexec/nm-dhcp-client.action, ...): Permission denied
May 3 08:19:32 rti-is019-con dhclient: can't create /usr/local/var/lib/dhcp3/dhclient-1537db51-4a51-4dd4-b512-c779f0b420ee-eth0.lease: No such file or directory
May 3 08:19:32 rti-is019-con dhclient: bound to 10.70.29.178 -- renewal in 313910 seconds.
May 3 08:19:32 rti-is019-con dhclient: Can't create /usr/local/var/run/dhclient-eth0.pid: Permission denied
May 3 08:20:18 rti-is019-con NetworkManager[1237]: <warn> (eth0): DHCPv4 request timed out.
May 3 08:20:18 rti-is019-con NetworkManager[1237]: <info> (eth0): canceled DHCP transaction, DHCP client pid 3108
May 3 08:20:18 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Timeout) scheduled...
May 3 08:20:18 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Timeout) started...
May 3 08:20:18 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
May 3 08:20:18 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Timeout) complete.
May 3 08:20:18 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
May 3 08:20:18 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) failed (no IP configuration found)
May 3 08:20:18 rti-is019-con NetworkManager[1237]: <info> (eth0): device state change: 7 -> 9 (reason 5)
May 3 08:20:18 rti-is019-con NetworkManager[1237]: <info> Marking connection 'Auto eth0' invalid.
May 3 08:20:18 rti-is019-con NetworkManager[1237]: <warn> Activation (eth0) failed.
May 3 08:20:18 rti-is019-con NetworkManager[1237]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
May 3 08:20:18 rti-is019-con NetworkManager[1237]: <info> (eth0): device state change: 9 -> 3 (reason 0)
May 3 08:20:18 rti-is019-con NetworkManager[1237]: <info> (eth0): deactivating device (reason: 0).
May 3 08:20:18 rti-is019-con avahi-daemon[1136]: Withdrawing address record for 10.70.29.178 on eth0.
May 3 08:20:18 rti-is019-con avahi-daemon[1136]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.70.29.178.
May 3 08:20:18 rti-is019-con avahi-daemon[1136]: Interface eth0.IPv4 no longer relevant for mDNS.
Any more ideas?
Thanks
That it's trying to create a file in /usr/local is very bizzare. Have you installed any software that you built by hand?
Hey Corona.
Nope. That was bizarre. I'm not that experienced with Ubuntu but that was a little strange to me.
hmm... That's true, /usr/local is strange.
If /var symlinked to /usr/local/var?
Can you access the /usr/local/var/lib/dhcp3/ directory? If so, perhaps an apparmor issue?
/usr/local/var/lib/dhcp3/ doesn't exist.
/usr/local/var/lib/NetworkManager does though...
---------- Post updated at 12:23 PM ---------- Previous update was at 12:18 PM ----------
I've actually found some more info on those errors, and it seems to be an apparmor bug that was affecting the previous Distros. Also there seems to be a buggy issue with dhclient-script which I've tried to work on with suggestions from other forums and nothing seems to work.
I think I'm going to reinstall the system and try the new 11.04...
Just fun for, you may want to create the dhcp3 directory (with appropriate access right) under /usr/local/var/lib/dhcp3/ and check if that's do it.
drwxr-xr-x 2 root root 12288 2011-05-02 21:59 dhcp3
I have 10.04 and the dhcp3 directory for lease is located under /var/lib/dhcp3. If that directory also exists on your system, a symlink for /usr/local/... might do it also.
If you can afford it, a fresh install might be the way to go to ensure a "clean system".
1 Like
Yeah thats what I did and It works perfectly now. Something broke and was causing problems. Don't know but since I need this computer to work, I have reinstalled system and now have 11.04. It works perfectly.
Glad that you solve the problem Sometimes, it's better to (re)start from scratch...
Cheers, Lo�c
1 Like