Login or Register to Ask a Question and Join Our Community


Ubuntu

Ubuntu 10.10 LAN connection stopped working...

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems Linux Ubuntu Ubuntu 10.10 LAN connection stopped working...
# 8  
Old 05-03-2011
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
This User Gave Thanks to Loic Domaigne For This Post:
zixzix01
# 9  
Old 05-03-2011
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.

Quote:
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 https://www.isc.org/software/dhcp/
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 https://www.isc.org/software/dhcp/
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 https://www.isc.org/software/dhcp/
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
# 10  
Old 05-03-2011
That it's trying to create a file in /usr/local is very bizzare. Have you installed any software that you built by hand?
# 11  
Old 05-03-2011
Hey Corona.

Nope. That was bizarre. I'm not that experienced with Ubuntu but that was a little strange to me.
# 12  
Old 05-03-2011
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?
Last edited by Loic Domaigne; 05-03-2011 at 01:24 PM.. Reason: new ideas
# 13  
Old 05-03-2011
/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...
# 14  
Old 05-03-2011
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.
Code:
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".
This User Gave Thanks to Loic Domaigne For This Post:
zixzix01
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Solaris

Mailx stopped working

after a new patch set on the 14th. I noticed that mailx stopped working, as far a I can tell that is the only thing that changed. solaris 10 OS it seems everything is the same, sendmail seems to be running root@server # ps -ef | grep -i sendmail smmsp 687 1 0 10:42:25 ? ... (0 Replies)
Discussion started by: goya
0 Replies

2. AIX

Printer stopped working

I have a serial printer connected to a 16 port ran. All of a sudden my printer stopped working and not sure how to get it back. Can anyone help pint me in the write direction? lsdev -Cc printer gives me the following. lp0 Defined 0A-08-11-00 Other serial printer lp1 Defined 0A-08-11-03... (3 Replies)
Discussion started by: Gmanx
3 Replies

3. Shell Programming and Scripting

Perl script stopped working

Hi, I have the following segment of a script which is supposed to prompt a user for password and then capture the password entered by the user. The function is called in by another script and used to work without issue, the problem is that recently the script is not waiting for the user to... (3 Replies)
Discussion started by: belalr
3 Replies

4. IP Networking

Wireless stopped working- Fedora 12

I installed F12 around the time it was released and it picked up my wireless card and worked like a charm.....Suddenly last week everything stopped working and I receive what appears to be a driver error when wlan0 tries to load. Error for wireless request "Set Mode" (8B06) : SET failed on... (1 Reply)
Discussion started by: woodson2
1 Replies

5. Shell Programming and Scripting

cronjobs stopped working

Hello people, I had these cronjobs scheduled in some Unix boxes which were running fine until yesterday.But then the password was changed for that user id and then the jobs stopped working. As far as i know cron jobs run from super user. I am completely lost over here now. Thanks. (2 Replies)
Discussion started by: King Nothing
2 Replies

6. Linux

Cronjobs stopped working

Hi All, I am user of a Linux machine and I have approximatly 15 cronjobs scheduled in my crontab. Yesterday my administrator made LDAP active on my userid and all the things are doing fine after that. But all cronjobs for my user id stored in my crontab have stopped working after that. Could... (1 Reply)
Discussion started by: bisla.yogender
1 Replies

7. Shell Programming and Scripting

#!/bin/bash has stopped working

Hi I'm writing a script and I've put #!/bin/bash as the first line so that I can just type my scripts name 'whodate' at PS1 instead of ./whodate. This has suddenly stopped working for me. It used to be the case that I could start a script with #!/bin/bash and it would work, but for this script... (2 Replies)
Discussion started by: zorrokan
2 Replies

8. UNIX for Dummies Questions & Answers

VMPlayer stopped working after ubuntu updated kernel

A month or so ago Ubuntu Dapper did its auto-update thing and installed the new kernel (intrd.img-2.6.15-28-386, upgraded from intrd.img-2.6.15-27-386). I rebooted after install and immediately the xserver would not load. I quickly figured out that I could boot the old kernel from GRUB however,... (1 Reply)
Discussion started by: forchessonly
1 Replies

9. Solaris

Internet Connection via Lan

I have a sun wokstation running solaris 9 , I want to configuring my lan card to access internet . my IP address : 192.168.144.20 ISP gateway : 192.168.144.1 DNS address : 202.56.250.5 all helps will be appreciated thanks (2 Replies)
Discussion started by: una
2 Replies
Login or Register to Ask a Question