[Bug 774502] New: NTP & NFS mount fail before network is up
https://bugzilla.novell.com/show_bug.cgi?id=774502 https://bugzilla.novell.com/show_bug.cgi?id=774502#c0 Summary: NTP & NFS mount fail before network is up Classification: openSUSE Product: openSUSE 12.2 Version: RC 1 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: shaggyman@bobsown.net QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20100101 Firefox/14.0.1 NTP is configured to sync on boot-up. There are several NFS mounts in /etc/fstab, one with a server name and the other with an ip address to the same server. All fail before the network is fully up. I've tried with the system defaulting to getting it's address from DHCP and specifying the ip address manually. Reproducible: Always Steps to Reproduce: 1.Configure NTP to start on bootup 2.Add NFS mounts via YAST (or manually to /etc/fstab) 3.reboot Actual Results: NTP failed to access the public server. None of the NFS mounts happened. Expected Results: NTP should have set the system clock and the NFS directories should have been mounted -- 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=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c
kk zhang
https://bugzilla.novell.com/show_bug.cgi?id=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c1
Peter Varkoly
https://bugzilla.novell.com/show_bug.cgi?id=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c
Peter Varkoly
https://bugzilla.novell.com/show_bug.cgi?id=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c2
Bob Ewart
https://bugzilla.novell.com/show_bug.cgi?id=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c3
Peter Varkoly
https://bugzilla.novell.com/show_bug.cgi?id=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c4
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c5
--- Comment #5 from Bob Ewart
https://bugzilla.novell.com/show_bug.cgi?id=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c6
--- Comment #6 from Bob Ewart
https://bugzilla.novell.com/show_bug.cgi?id=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c7
Bob Ewart
https://bugzilla.novell.com/show_bug.cgi?id=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c8
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c9
Marius Tomaschewski
from what I see, your system is configured to use ifup/ifdown (not NetworkManager) to configure your network, and network.service is being started after 3s, so it should wait until network is up.
Sorry, but I don't understand what last commenter wanted to say here :-) AFAIS, the start order is OK but you're using ifplugd. When you're using it, change to start all network related services via network hooks, see "man ifservices". In ifplugd mode, rcnetwork returns "done" as soon as possible and starts the interface in the background... Please disable it -- change /etc/sysconfig/network/ifcfg-eth0 to use: STARTMODE=auto When really required (I don't think so), set LINK_READY_WAIT="15" in the same file. Alternatively, you can also use STARTMODE=nfsroot -- it causes that network will be persistent / a stop does not remove IP addresses. -- 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=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c10
--- Comment #10 from Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c11
Bob Ewart
https://bugzilla.novell.com/show_bug.cgi?id=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c12
Marius Tomaschewski
Yes it does.
I did a fresh install from openSUSE-KDE-LiveCD-Build0091-x86_64.iso
ifcfg-etho had STARTMODE='ifplugd'
I added 2 nfs mounts via Yast. The mount failed. I tried to mount them as root and it complained that rpc.statd wasn't running.
I started rpcbind via YAST and could mount them.
When I set STARTMODE='auto' it worked.
Looks like the default STARTMODE is wrong
Well, the proposal yast2 makes depends on the view / focus. For notebooks or "home desktops" (that are "focused" on openSUSE), where things like nfs usually aren't in use/needed [and also the rpcbind is disabled by default?], ifplugd is not really wrong: it starts and stops one or more interfaces (you can also set a priority, e.g. to prefer lan over wlan) on demand. Independently of the above, this is a configuration issue and thus I reassign it to yast2. Perhaps yast2 can be improved here. -- 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=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c13
Marius Tomaschewski
Alternatively, you can also use STARTMODE=nfsroot -- it causes that network will be persistent / a stop does not remove IP addresses.
BTW / for completeness: This is mandatory for nfsroot, /usr on nfs and other [iSCSI] scenarios where the filesystems or discs are started in the initrd and accessed over the network and a "rcnetwork stop" should not stop interfaces. -- 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=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c14
Michal Filka
When I set STARTMODE='auto' it worked.
Looks like the default STARTMODE is wrong
there is several "defaults" in networking - depending on target system. Just to be sure. Did you perform installation at laptop, rigth? -- 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=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c15
--- Comment #15 from Bob Ewart
https://bugzilla.novell.com/show_bug.cgi?id=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c16
Bob Ewart
https://bugzilla.novell.com/show_bug.cgi?id=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c17
Michael Catanzaro
https://bugzilla.novell.com/show_bug.cgi?id=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c18
Axel Braun
https://bugzilla.novell.com/show_bug.cgi?id=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c19
--- Comment #19 from Marius Tomaschewski
I dont feel that this is a configuration issue, but correct me if I'm wrong. IMHO ntp should restart after each network connection (i.e. after resume from suspend)
Not any more: - Fixed netconfig/ntp-runtime to not use try-restart as its start may block for a while, so just add servers ourself in background. When ntpd is not running (not yet started), the ntp init script will pickup our servers later at ntp start (bnc#780644). In another words, when the network starts, and gets a lease including an ntp server, 'echo "addserver xxx" | ntpdc' is used now to sync the time and the ntp servers are written to /var/run/ntp/servers-netconfig. When ntpd is already started [e.g. lease renew], ntpdc makes the sync, otherwise the ntp init script will pick up the server list from the /var/run/ntp/servers-netconfig file when it (re)starts. So (at boot) first the network starts and does nothing with ntp (ntpdc addserver fails). Then, the ntpd starts and the init script makes the ntpdc addserver call. Further, as I wrote in e.g. comment 9, do not use STARTMODE='ifplugd' (On-Cable-Connect or something like this in yast2). With STARTMODE='ifplugd', it is required to disable ntp & nfs start (all services which can't be started without network up) at boot time and use ifup(8) or ifservices(5) hooks to start them when network goes up. AFAIS, there is no dependency (Required-Start, Should-Start) to ntp ($time) in /etc/init.d/nfs at all and this is IMO the problem here. -- 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=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c20
--- Comment #20 from Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c21
--- Comment #21 from Axel Braun
(In reply to comment #18)
I dont feel that this is a configuration issue, but correct me if I'm wrong. IMHO ntp should restart after each network connection (i.e. after resume from suspend)
Not any more: - Fixed netconfig/ntp-runtime to not use try-restart as its start may block for a while, so just add servers ourself in background. When ntpd is not running (not yet started), the ntp init script will pickup our servers later at ntp start (bnc#780644).
Hmm....this bug mentions openSUSE 12.2 (src): sysconfig-0.76.4-1.4.1 as package where the solution is available. It is installed on my system, but still the ntp-bug exists... Or is it openSUSE 12.1 (src): sysconfig-0.75.4-2.16.1 but not just for 12.1? -- 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=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c22
--- Comment #22 from Marius Tomaschewski
(In reply to comment #19)
(In reply to comment #18)
I dont feel that this is a configuration issue, but correct me if I'm wrong. IMHO ntp should restart after each network connection (i.e. after resume from suspend)
Not any more: - Fixed netconfig/ntp-runtime to not use try-restart as its start may block for a while, so just add servers ourself in background. When ntpd is not running (not yet started), the ntp init script will pickup our servers later at ntp start (bnc#780644).
Hmm....this bug mentions openSUSE 12.2 (src): sysconfig-0.76.4-1.4.1 as package where the solution is available. It is installed on my system, but still the ntp-bug exists...
Seems, you didn't read the complete comment... Above I just said, that ntp is not restarted any more on network connection changes. Further, I also said: AFAIS, there is no dependency (Required-Start, Should-Start) to ntp ($time) in /etc/init.d/nfs at all and this is IMO the problem here. -- 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=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c23
--- Comment #23 from Axel Braun
Seems, you didn't read the complete comment...
Lets say, I didnt get it....
Above I just said, that ntp is not restarted any more on network connection changes.
Further, I also said:
AFAIS, there is no dependency (Required-Start, Should-Start) to ntp ($time) in /etc/init.d/nfs at all and this is IMO the problem here.
/etc/init.d/nfs ...relates to the classical startup sequence, no? Sorry, I'm not an expert in systemd or init scripts, I just can see from the LSB-header if /etc/init.d/nfs that it requires the network to be started. And that was nicely working in old times. With systemd obviously not. So IMHO this is a problem in systemd, or am I wrong? -- 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=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c24
--- Comment #24 from Marius Tomaschewski
/etc/init.d/nfs ...relates to the classical startup sequence, no?
Yes.
Sorry, I'm not an expert in systemd or init scripts, I just can see from the LSB-header if /etc/init.d/nfs that it requires the network to be started.
Network yes, but neither $time (ntp) nor $named. And it will never work with STARTMODE='ifplugd' or NetworkManager, unless you handle it yourself via ifservices(5) or NetworkManager dispatcher scripts. => Use STARTMODE=auto or STARTMODE=nfsroot. AFAIS it fails because name resolution (comment 7). Does your /etc/resolv.conf contains the correct name server settings when the network is completely up? Are you able to resolve the hostnames used in fstab then (e.g. "host nfsserver")?
And that was nicely working in old times. With systemd obviously not. So IMHO this is a problem in systemd, or am I wrong?
systemd makes much more in parallel. You can try to double the WAIT_FOR_INTERFACES and DHCLIENT_WAIT_AT_BOOT that are in /etc/sysconfig/network/{config,dhcp}. When these timeouts expire for some reason, /etc/init.d/network reports 0 (success) to the systemd even the network is not completely started. Please attach a supportconfig (install supportutils) output. -- 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=774502
https://bugzilla.novell.com/show_bug.cgi?id=774502#c25
--- Comment #25 from Axel Braun
participants (1)
-
bugzilla_noreply@novell.com