[Bug 745859] New: network reports failure at start under systemd
https://bugzilla.novell.com/show_bug.cgi?id=745859 https://bugzilla.novell.com/show_bug.cgi?id=745859#c0 Summary: network reports failure at start under systemd Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEEDINFO Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: mt@suse.com QAContact: qa@suse.de CC: mt@suse.com, koenig@linux.de, fcrozat@suse.com Depends on: 744293 InfoProvider: koenig@linux.de Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #744293 +++ New bug nr for https://bugzilla.novell.com/show_bug.cgi?id=744293#c22: ====================================================================== Feb 7 17:20:42 t3 kernel: [ 22.656993] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Feb 7 17:20:42 t3 kernel: [ 22.657887] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Feb 7 17:20:42 t3 ifup-dhcp: eth0 Starting DHCP4 client Feb 7 17:20:42 t3 dhcpcd[1900]: eth0: dhcpcd 3.2.3 starting .. Feb 7 17:21:07 t3 network[866]: eth0 device: Intel Corporation 82573E Gigabit Ethernet Con Feb 7 17:21:07 t3 network[866]: eth0 . . . is just beeing set up Feb 7 17:21:07 t3 network[866]: eth0 IP address: 192.168.178.47/24 Feb 7 17:21:07 t3 network[866]: eth0 is up Feb 7 17:21:07 t3 network[866]: [1Awaiting Feb 7 17:21:07 t3 network[866]: eth0 interface could not be set up until now Feb 7 17:21:07 t3 network[866]: ..failedSetting up service (localfs) network . . . . . . . . ...failed Feb 7 17:21:07 t3 systemd[1]: network.service: control process exited, code=exited status=7 Feb 7 17:21:07 t3 systemd[1]: Unit network.service entered failed state. Feb 7 17:21:08 t3 rpcbind[3690]: Starting rpcbind ..done ====================================================================== Network may report failure in some cases, e.g. IPv6 duplicate address detection failure [also for IPv4 when enabled], that is in case of a true failure: network[824]: eth0 IP address: 192.168.2.5/24 network[824]: eth0 IP address: 2001:aaaa:bbbb:cccc::5/64 network[824]: eth0 is up, but has tentative ipv6 address network[824]: eth0 interface could not be set up until now Failed to start LSB: Configure the localfs depending network interfaces [ESC[1;31mFAILED See 'systemctl status network.service' for details. or when it needs longer than the time limit WAIT_FOR_INTERFACES="30" because of some other reason [e.g. bug 724777, bnx2 hardware needs too long to detect the link, dhcp server can't be reached]. When dhcp is in use [or IPv6 dad still in progress in the kernel], it will first report "in background" and after e.g. dhcp server is reachable again "rcnetwork status" may report success later. The above log looks like dhcpcd would be unable to get address or would die(?) and didn't reported "completed" state back to ifup. Please set DEBUG=EXTRA in /etc/sysconfig/network/config, reboot and attach a "tar cvzpf /tmp/network-debug.tgz /dev/.sysconfig/network". -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=745859
https://bugzilla.novell.com/show_bug.cgi?id=745859#c
Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=745859
https://bugzilla.novell.com/show_bug.cgi?id=745859#c1
--- Comment #1 from Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=745859
https://bugzilla.novell.com/show_bug.cgi?id=745859#c2
Harald Koenig
Please make sure you have the most recent systemd >= 37-3.151.1 from: http://download.opensuse.org/repositories/home:/fcrozat:/systemd/openSUSE_12...
install the sysconfig package (changelog from today, > 0.75.4-2.8) from:
http://download.opensuse.org/repositories/home:/mtomaschewski:/branches:/ope...
done> rpm -q systemd sysconfig systemd-37-3.6.1.x86_64 sysconfig-0.75.4-2.5.1.x86_64
Then set DEBUG=EXTRA in /etc/sysconfig/network/config, reboot and attach a tar.bz2 of /dev/.sysconfig/network when it occurs again.
occurs always -- voila... -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=745859
https://bugzilla.novell.com/show_bug.cgi?id=745859#c3
--- Comment #3 from Harald Koenig
https://bugzilla.novell.com/show_bug.cgi?id=745859
https://bugzilla.novell.com/show_bug.cgi?id=745859#c4
--- Comment #4 from Frederic Crozat
http://download.opensuse.org/repositories/home:/fcrozat:/systemd/openSUSE_12...
-- 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.
https://bugzilla.novell.com/show_bug.cgi?id=745859
https://bugzilla.novell.com/show_bug.cgi?id=745859#c5
--- Comment #5 from Harald Koenig
you didn't upgrade systemd (>= 37-3.151.1) from :
http://download.opensuse.org/repositories/home:/fcrozat:/systemd/openSUSE_12...
yes I did -- but I was running the "rpm -q ..." on the wrong system. sorry for the confusion:-( this should have read: # hostname t3 # rpm -q systemd sysconfig systemd-37-3.152.1.x86_64 sysconfig-0.75.4-2.8.test.1.x86_64 and with time stamps: # rpm -qa --last | head -2 sysconfig-0.75.4-2.8.test.1 Thu Feb 16 15:54:31 2012 systemd-37-3.152.1 Thu Feb 16 15:53:50 2012 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=745859
https://bugzilla.novell.com/show_bug.cgi?id=745859#c6
--- Comment #6 from Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=745859
https://bugzilla.novell.com/show_bug.cgi?id=745859#c7
--- Comment #7 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=745859
https://bugzilla.novell.com/show_bug.cgi?id=745859#c8
Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=745859
https://bugzilla.novell.com/show_bug.cgi?id=745859#c9
--- Comment #9 from Harald Koenig
Note: You don't need to _use_ any samba -- it is enough that samba-client is installed. Please update any samba related packages from:
http://download.opensuse.org/repositories/home:/fcrozat:/systemd/openSUSE_12...
interesting! ACK: with new samba-client the network startup is ok: $ systemctl status network.service network.service - LSB: Configure the localfs depending network interfaces Loaded: loaded (/etc/init.d/network) Active: active (running) since Tue, 21 Feb 2012 16:04:30 +0100; 11min ago Process: 1019 ExecStart=/etc/init.d/network start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/network.service ? 2062 /sbin/dhclient6 -6 -cf /var/lib/dhcp6/dhclient6.eth0.conf -lf /var/lib... ? 2566 /sbin/dhcpcd --netconfig -L -E -HHH -c /etc/sysconfig/network/scripts/... now the only remaining failure is NetworkManager because I've disabled it (IMHO still not a valid and "wanted" failure -- as failures are never "wanted", see bug #745653): NetworkManager.service loaded failed failed Network Manager thanks! -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=745859
https://bugzilla.novell.com/show_bug.cgi?id=745859#c10
--- Comment #10 from Marius Tomaschewski
(In reply to comment #8)
Note: You don't need to _use_ any samba -- it is enough that samba-client is installed. Please update any samba related packages from:
http://download.opensuse.org/repositories/home:/fcrozat:/systemd/openSUSE_12...
interesting!
Yes :-)
ACK: with new samba-client the network startup is ok:
OK, thanks for verification.
now the only remaining failure is NetworkManager because I've disabled it (IMHO still not a valid and "wanted" failure -- as failures are never "wanted", see bug #745653):
NetworkManager.service loaded failed failed Network Manager
Yes, I'd say it is WONTFIX. In LSB init scripts, you can return: 5 (program is not installed) alias skipped, 6 (program is not configured) alias unused, or in a "status" query 3 (service not running) alias unused. this are basically also errors, but displayed differently. Systemd does not provide such a possibility. There are several possibilities to set a "Condition" (man systemd.unit) for the start, but there is AFAIK no one that would allow to execute a test to check a custom condition [ConditionExecuteTest :-)], so we were forced to use ExecStartPre="/usr/bin/test "x${NETWORKMANAGER}" = xyes". This works (NM is not started), but is considered as an error. This is something we'll probably address in 12.2. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=745859 https://bugzilla.novell.com/show_bug.cgi?id=745859#c Bug 745859 depends on bug 744293, which changed state. Bug 744293 Summary: systemd: vdr starts before nfs-client-mount ?! http://bugzilla.novell.com/show_bug.cgi?id=744293 What |Old Value |New Value ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED -- 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.
participants (1)
-
bugzilla_noreply@novell.com