[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
https://bugzilla.novell.com/show_bug.cgi?id=806725
https://bugzilla.novell.com/show_bug.cgi?id=806725#c2
Tim Hardeck
https://bugzilla.novell.com/show_bug.cgi?id=806725
https://bugzilla.novell.com/show_bug.cgi?id=806725#c5
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=806725
https://bugzilla.novell.com/show_bug.cgi?id=806725#c7
Tim Hardeck
https://bugzilla.novell.com/show_bug.cgi?id=806725
https://bugzilla.novell.com/show_bug.cgi?id=806725#c8
--- Comment #8 from Tim Hardeck
https://bugzilla.novell.com/show_bug.cgi?id=806725
https://bugzilla.novell.com/show_bug.cgi?id=806725#c9
--- Comment #9 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=806725
https://bugzilla.novell.com/show_bug.cgi?id=806725#c10
--- Comment #10 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=806725
https://bugzilla.novell.com/show_bug.cgi?id=806725#c12
--- Comment #12 from Tim Hardeck
https://bugzilla.novell.com/show_bug.cgi?id=806725
https://bugzilla.novell.com/show_bug.cgi?id=806725#c13
--- Comment #13 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=806725
https://bugzilla.novell.com/show_bug.cgi?id=806725#c17
Ludwig Nussel
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
https://bugzilla.novell.com/show_bug.cgi?id=806725
https://bugzilla.novell.com/show_bug.cgi?id=806725#c19
--- Comment #19 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=806725
https://bugzilla.novell.com/show_bug.cgi?id=806725#c20
--- Comment #20 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=806725
https://bugzilla.novell.com/show_bug.cgi?id=806725#c21
--- Comment #21 from Thomas Renninger
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
https://bugzilla.novell.com/show_bug.cgi?id=806725
https://bugzilla.novell.com/show_bug.cgi?id=806725#c22
--- Comment #22 from Tim Hardeck
https://bugzilla.novell.com/show_bug.cgi?id=806725
https://bugzilla.novell.com/show_bug.cgi?id=806725#c23
--- Comment #23 from Frederic Crozat
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
https://bugzilla.novell.com/show_bug.cgi?id=806725
https://bugzilla.novell.com/show_bug.cgi?id=806725#c25
Michael Karbach
https://bugzilla.novell.com/show_bug.cgi?id=806725
https://bugzilla.novell.com/show_bug.cgi?id=806725#c26
Tim Hardeck
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
https://bugzilla.novell.com/show_bug.cgi?id=806725
https://bugzilla.novell.com/show_bug.cgi?id=806725#c28
--- Comment #28 from Tim Hardeck
* 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
https://bugzilla.novell.com/show_bug.cgi?id=806725
https://bugzilla.novell.com/show_bug.cgi?id=806725#c30
Tim Hardeck
https://bugzilla.novell.com/show_bug.cgi?id=806725
https://bugzilla.novell.com/show_bug.cgi?id=806725#c31
Frederic Crozat
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
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
https://bugzilla.novell.com/show_bug.cgi?id=806725
https://bugzilla.novell.com/show_bug.cgi?id=806725#c34
Tim Hardeck
participants (1)
-
bugzilla_noreply@novell.com