https://bugzilla.novell.com/show_bug.cgi?id=407152 Summary: No IP-Address at wired networks ("dhclient: caught deadly SIGTERM") Product: openSUSE 10.3 Version: Final Platform: 32bit OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jolz@gmx.de QAContact: qa@suse.de Found By: --- Some computers have after booting no ip-adress at the login screen:

From /var/log/messages the IP vanishes with the following messages

From the Sources of NetworkManager 6.5 I learned, that the dhclient-state "IP address assigned" commes with an dbus-message. --> Logentry "DHCP daemon state is now 2 (bound) for interface eth0" (does NOT appear in this case) From the logs i just looks, as if dbus lost this single message. Is this

Jun 30 05:44:43 newsys dhclient: caught deadly SIGTERM Jun 30 05:44:43 newsys dhclient: could not restore resolv.conf: No such file or directory Jun 30 05:44:43 newsys dhclient: DHCPRELEASE on eth0 to 172.16.5.121 port 67 Jun 30 05:44:43 newsys dhclient: send_packet: Network is unreachable Jun 30 05:44:43 newsys dhclient: send_packet: please consult README file regarding broadcast address. /var/log/NetworkManager says at this second: Jun 30 05:44:43 newsys NetworkManager: <info> Device 'eth0' DHCP transaction took too long (>45s), stopping it. As root, I do a "rcnetwork restart" and wait ~10 sec or just restart the computer. Normally, network is up and the user can start to work. possible - does dbus loose messages in any case? This whole thing happens on various computers with LAN-connection (don't know about wlan networks) and is only hardly reproducible: maybe only 1 in ~100 boot cycles shows this problem. (~8 fails from >20 SuSE Boxes in one week). I'm not shure about openSuSE 11.0. I first thought, i might be a similar bug like 402575 (see https://bugzilla.novell.com/show_bug.cgi?id=402575#c13 ) P.S.: Here are some more Lines from /var/log/NetworkManager Jun 24 07:31:02 newsys NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Jun 24 07:31:02 newsys NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface eth0 Jun 24 07:31:03 newsys NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface eth0 Jun 24 07:31:06 newsys NetworkManager: <debug> [1214285466.460103] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/computer_alsa_sequencer'). Jun 24 07:31:06 newsys NetworkManager: <debug> [1214285466.515815] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/pci_10de_371_sound_card_0_oss_mi xer__1'). Jun 24 07:31:06 newsys NetworkManager: <debug> [1214285466.523460] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/pci_10de_371_sound_card_0_oss_pc m_1'). Jun 24 07:31:06 newsys NetworkManager: <debug> [1214285466.530770] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/pci_10de_371_sound_card_0_oss_pc m_0'). Jun 24 07:31:06 newsys NetworkManager: <debug> [1214285466.538184] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/pci_10de_371_sound_card_0_oss_pc m_0_0'). Jun 24 07:31:47 newsys NetworkManager: <info> Device 'eth0' DHCP transaction took too long (>45s), stopping it. Jun 24 07:31:48 newsys NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Timeout) started... Jun 24 07:31:48 newsys NetworkManager: <info> No DHCP reply received. Automatically obtaining IP via Zeroconf. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.