[Bug 806725] New: ypbind and autofs aren't started correctly
https://bugzilla.novell.com/show_bug.cgi?id=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c0 Summary: ypbind and autofs aren't started correctly Classification: openSUSE Product: openSUSE 12.3 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: thardeck@suse.com QAContact: qa-bugs@suse.de CC: trenn@suse.com, fcrozat@suse.com Found By: Development Blocker: --- Created an attachment (id=527482) --> (http://bugzilla.novell.com/attachment.cgi?id=527482) dmesg + systemd debug messages before manually restarting the services I can't login over NIS in openSUSE 12.3 until I switch to console and manually restart the following services in the correct succession: ypbind nfs autofs It seems that these services are either not started in the correct order or are blocking each other. A similar issue appeared on 12.2 but only on some systems. Now it seems to happen every time. -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c1 --- Comment #1 from Tim Hardeck <thardeck@suse.com> 2013-02-28 13:48:55 UTC --- Created an attachment (id=527483) --> (http://bugzilla.novell.com/attachment.cgi?id=527483) dmesg + systemd debug messages after manually restarting the services -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c2 Tim Hardeck <thardeck@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |werner@suse.com --- Comment #2 from Tim Hardeck <thardeck@suse.com> 2013-02-28 13:57:53 UTC --- There was a bug against 12.2 for this issue: bnc#780441 but it might be something else according to Thomas. -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c5 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |thardeck@suse.com --- Comment #5 from Frederic Crozat <fcrozat@suse.com> 2013-03-04 17:20:51 UTC --- could you attach output for: systemctl show autofs.service systemctl show nfs.service systemctl show ypbind.service -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c7 Tim Hardeck <thardeck@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|thardeck@suse.com | --- Comment #7 from Tim Hardeck <thardeck@suse.com> 2013-03-05 09:10:19 UTC --- Created an attachment (id=528130) --> (http://bugzilla.novell.com/attachment.cgi?id=528130) output of systemctl show for all three services -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c8 --- Comment #8 from Tim Hardeck <thardeck@suse.com> 2013-03-05 09:13:03 UTC --- I ran these comments before the manual restart of the services. The output afterwards did only seem to differ in timestamps and pids. -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c9 --- Comment #9 from Thomas Renninger <trenn@suse.com> 2013-03-05 10:12:10 UTC --- I looked at this for 12.2, but there it was slightly different. Afaik on 12.2 only specific machines run into this. Now every machine I tried runs into this. What is missing in nfs-utils is proper systemd integration (not sure whether someone else looked at this meanwhile, I will attach my work I've already done against 12.2 nfs-utils package). I never came to test this on 12.2, this does not help for 12.3. -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c10 --- Comment #10 from Frederic Crozat <fcrozat@suse.com> 2013-03-05 10:23:57 UTC --- maybe a stupid test to do, but still: You are using NetworkManager and NetworkManager-wait-online.service is configured by default to not wait at all for network to become "up and running". Could you change in /etc/sysconfig/network/config NM_ONLINE_TIMEOUT to 30 ? If it works, it means NM should restart ypbind when it is connected (so far, we have only hooks for restarting nfs and autofs, not ypbind, see /etc/NetworkManager/dispatcher.d -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c12 --- Comment #12 from Tim Hardeck <thardeck@suse.com> 2013-03-05 10:37:16 UTC --- I am not using the Networkmanager, I am using ifup with static ip configuration. -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c13 --- Comment #13 from Frederic Crozat <fcrozat@suse.com> 2013-03-05 10:39:22 UTC --- That's not what I see in the initial trace you posted, NM is used. -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c17 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Component|Basesystem |YaST2 InfoProvider| |thardeck@suse.com QAContact|qa-bugs@suse.de |jsrain@suse.com --- Comment #17 from Ludwig Nussel <lnussel@suse.com> 2013-03-05 15:09:39 CET --- I fail to see how this has anything to do with insserv. ypbind and autofs are systemd services. The yast2 nis module is buggy though, it doesn't enable them (will file bug for that). Check for i in rpcbind.socket ypbind autofs; do systemctl status $i; done to make sure those services are enabled and running. -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c18 --- Comment #18 from Dr. Werner Fink <werner@suse.com> 2013-03-05 15:34:40 UTC --- (In reply to comment #17) At least openldap2 seems to have a problem as Peter Varkoly <varkoly@suse.com> had tried it. After my tip to do `systemctl daemon-reload' and `sysrtemctl enable ldap' it had worked. -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c19 --- Comment #19 from Thomas Renninger <trenn@suse.com> 2013-03-05 17:38:57 UTC --- Created an attachment (id=528240) --> (http://bugzilla.novell.com/attachment.cgi?id=528240) nfs-utils .spec file changes to intergrate an systemd nfs.target This was my try to fix 12.2. IMO something like this is missing to be able to synchronize with nfs. Even better would be to further separate nfs targets. The same someone wanted to do in init V already (/etc/init.d/nfs): # XXX: there should be separate init scripts for these really IDMAPD_BIN=/usr/sbin/rpc.idmapd GSSD_BIN=/usr/sbin/rpc.gssd STATD_BIN=/usr/sbin/rpc.statd Fedora has something similar. I will attach the real nfs.target file as well. I could imagine, that might have helped on 12.2, where my machine worked with ypbind (but slower ones did not?), but it got worse and you now always do not get ypbind working. So I could imagine there are several issues, the nfs.target may address one. -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c20 --- Comment #20 from Thomas Renninger <trenn@suse.com> 2013-03-05 17:39:51 UTC --- Created an attachment (id=528241) --> (http://bugzilla.novell.com/attachment.cgi?id=528241) nfs.target and the actual systemd target file. -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c21 --- Comment #21 from Thomas Renninger <trenn@suse.com> 2013-03-05 17:43:05 UTC ---
Fedora has something similar They had not split targets to imapd/gssd/statd yet and I tried to more or less adopt the dependencies of nfs.target to what services we have. I need some review/testing and I can submit this (or adjusted).
-- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c Andreas Jaeger <aj@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aj@suse.com AssignedTo|bnc-team-screening@forge.pr |fcrozat@suse.com |ovo.novell.com | -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c22 --- Comment #22 from Tim Hardeck <thardeck@suse.com> 2013-03-10 09:30:53 UTC --- After installing 12.3 GM I still had network issues in Stage 2 but after fixing them manually this issue is gone for me. Was anything updated in this regard besides the NetworkManager which isn't started anymore if it is disabled? -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c23 --- Comment #23 from Frederic Crozat <fcrozat@suse.com> 2013-03-11 09:33:31 UTC --- (In reply to comment #22)
Was anything updated in this regard besides the NetworkManager which isn't started anymore if it is disabled? I'm not aware of any change.
-- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c24 --- Comment #24 from Michael Karbach <michael@karbach.org> 2013-03-29 08:47:28 UTC --- Sorry, I also have this bug and I am using ifup with dhcp. I have updated from OS-12.1 to OS-12.3 via DVD. Unfortunately I do not know what to do for fixing this upon reading the above messages. Manually restarting the services from post one solves this problem temporary. -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c25 Michael Karbach <michael@karbach.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |michael@karbach.org --- Comment #25 from Michael Karbach <michael@karbach.org> 2013-04-01 07:01:38 UTC --- Note, in addition to the above problems, also sshd and cupsd are not started and have to be start manually too. -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c26 Tim Hardeck <thardeck@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|thardeck@suse.com | --- Comment #26 from Tim Hardeck <thardeck@suse.com> 2013-04-01 13:22:22 UTC --- (In reply to comment #24)
Sorry, I also have this bug and I am using ifup with dhcp. I have updated from OS-12.1 to OS-12.3 via DVD. Have you checked if the process NetworkManager is running?
(In reply to comment #25)
Note, in addition to the above problems, also sshd and cupsd are not started and have to be start manually too. Sounds like an upgrade issue - maybe because of the direct update from 12.1 to 12.3 and the systemd changes.
Have you tried activating the services again with chkconfig or yast? -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c27 --- Comment #27 from Michael Karbach <michael@karbach.org> 2013-04-01 15:28:15 UTC --- * Yes, NW is running: 481 0.0 0.2 241864 8528 ? Ssl 08:54 0:00 /usr/sbin/NetworkManager --no-daemon Is this ok, if one is using if-up? * Yes, I have done this with yast2. But I am wondering, in expert-mode I do not see the options for different runlevels. Is this also due to systemd? * What I have also observed is, that after boot with rcypbind status this process actually is running, but it definitely needs a rcypbind restart in order to work. -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c28 --- Comment #28 from Tim Hardeck <thardeck@suse.com> 2013-04-01 15:59:23 UTC --- (In reply to comment #27)
* Yes, NW is running: 481 0.0 0.2 241864 8528 ? Ssl 08:54 0:00 /usr/sbin/NetworkManager --no-daemon
Is this ok, if one is using if-up? No, it is not ok. I would try to enable the NetworkManager in `yast2 lan` and after confirming the change enable the traditional method again.
* Yes, I have done this with yast2. But I am wondering, in expert-mode I do not see the options for different runlevels. Is this also due to systemd? It seems that way: http://www.freedesktop.org/wiki/Software/systemd/FrequentlyAskedQuestions
-- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c29 --- Comment #29 from Michael Karbach <michael@karbach.org> 2013-04-01 16:14:40 UTC --- OK, thanks, switching to NWM and back has solved my problems! Thanks, Michael -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c30 Tim Hardeck <thardeck@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |fcrozat@suse.com --- Comment #30 from Tim Hardeck <thardeck@suse.com> 2013-04-01 16:34:29 UTC --- Could we update the NetworkManager or systemd packages so that during a dist upgrade from earlier openSUSE versions the sysconfig NetworkManager entry is analyzed and the links set accordingly? It seems that only the unrequested start of NetworkManager is causing this issue. -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c31 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|fcrozat@suse.com |mt@suse.com --- Comment #31 from Frederic Crozat <fcrozat@suse.com> 2013-04-02 09:15:01 UTC --- (In reply to comment #25)
Note, in addition to the above problems, also sshd and cupsd are not started and have to be start manually too.
I think it is unrelated to this particular bug. I might be a dup of bnc#809695(In reply to comment #30)
Could we update the NetworkManager or systemd packages so that during a dist upgrade from earlier openSUSE versions the sysconfig NetworkManager entry is analyzed and the links set accordingly?
This is not systemd job to handle specific package upgrade issue. Maybe NM package should be modified.. -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c32 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |mt@suse.com InfoProvider|mt@suse.com | --- Comment #32 from Marius Tomaschewski <mt@suse.com> 2013-04-02 11:42:37 UTC --- (In reply to comment #30)
Could we update the NetworkManager or systemd packages so that during a dist upgrade from earlier openSUSE versions the sysconfig NetworkManager entry is analyzed and the links set accordingly?
The /etc/sysconfig/network/config NETWORKMANAGER variable is migrated on update from <= 12.2 to 12.3, fixed in bnc#803058. See "rpm -q --scripts sysconfig" and also "rpm -q --scripts NetworkManager" on 12.3-final (RC2). More exactly, the variable is migrated, when the previous sysconfig were providing it. When you've had some 12.3-Beta/RC version installed before, the migration is *not* preformed [some tools may still set it using own obsolete defaults]. Also not, when you try to trigger it with e.g.: echo 'NETWORKMANAGER="no"' >> /etc/sysconfig/network/config
It seems that only the unrequested start of NetworkManager is causing this issue.
Yes, it does. ifup refuses do do anything when NetworkManager is enabled. This happens on systems which were updated to some 12.3-Beta or RC before. As this bug is reported with "Found in Version: RC2", I'd say we can close it as dup of bnc#803058 -- we've already verified the migration in several duplicates. -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c33 --- Comment #33 from Marius Tomaschewski <mt@suse.com> 2013-04-02 11:46:21 UTC --- BTW: Please make sure you've all updates installed, especially the last sysconfig update: Wed Mar 20 09:44:26 UTC 2013 - mt@suse.de - Fixed to wait for dhcp/ipv6 under systemd again. Fixed regression caused by bnc#785240, bnc#780644 fixes to not discard the dhcp/ipv6 dupplicate address detection in progress error codes under systemd completely, but wait until dhcp/ipv6 dad finished or the WAIT_FOR_INTERFACES timeout is reached and then discard in the status returned to systemd (bnc#808718). It caused failures of other services trying to bind tentative IPv6 addresses, e.g. in mixed dhcp4 / static IPv6 setups. Thanks to Rolf Eike Beer for the report/tests/debug outputs. [0001-Fixed-to-wait-for-dhcp-ipv6-under-systemd-again.patch] -- 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=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c34 Tim Hardeck <thardeck@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #34 from Tim Hardeck <thardeck@suse.com> 2013-04-02 11:51:30 UTC --- This autofs issue might still happen if the NetworkManager is used but there is another report for this issue. Marking as resolved. -- 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