[Bug 1129587] New: NIS / ypbind fails to start
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587 Bug ID: 1129587 Summary: NIS / ypbind fails to start Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: iforster@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After upgrading my machine from Leap 15.0 to Leap 15.1 Beta NIS fails to start on boot with the following log: Mär 18 10:26:16 lem systemd[1]: Starting NIS/YP Clients to NIS Domain Binder... Mär 18 10:26:16 lem ypbind-systemd-pre[1434]: suse.de\n Mär 18 10:26:16 lem ypbind-systemd-pre[1434]: . . . . . . . . . . /etc/yp.conf not found Mär 18 10:26:16 lem systemd[1]: ypbind.service: Control process exited, code=exited status=1 Mär 18 10:26:16 lem systemd[1]: Failed to start NIS/YP Clients to NIS Domain Binder. Mär 18 10:26:16 lem systemd[1]: ypbind.service: Unit entered failed state. Mär 18 10:26:16 lem systemd[1]: ypbind.service: Failed with result 'exit-code'. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587
Ludwig Nussel
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587#c4
--- Comment #4 from Ludwig Nussel
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587
Ludwig Nussel
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587#c5
--- Comment #5 from Thorsten Kukuk
and we can't fix ypbind to be a bit less picky?
As this is no bug in ypbind, there is nothing to fix. If there is no configuration, ypbind can nothing do. Quite simple. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587#c6
--- Comment #6 from Ludwig Nussel
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587
Ludwig Nussel
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587#c8
--- Comment #8 from Ludwig Nussel
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587
Ludwig Nussel
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587#c9
--- Comment #9 from Ludwig Nussel
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587 Bug 1129587 depends on bug 1130355, which changed state. Bug 1130355 Summary: NetworkManager-wait-online needs to be enabled with NetworkManager http://bugzilla.opensuse.org/show_bug.cgi?id=1130355 What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587#c10
Ludwig Nussel
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587#c11
Ignaz Forster
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587
Marius Tomaschewski
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587#c12
Marius Tomaschewski
bug for NM: https://bugzilla.opensuse.org/show_bug.cgi?id=1130355
So what's left is why the domainname is not set and that looks like something netconfig has to do. In fact it works when calling netconfig update after boot is done.
netconfig does it -- when somebody calls it (it's a tool, not a service), it will make a /bin/{nis,yp,}domainname `cat /etc/defaultdomain` call. /etc/defaultdomain is similar to /etc/hostname, configured by admin/yast2 and applied by boot scripts (boot.localnet in the past). The hostname is applied by systemd, defaultdomain obviously isn't. netconfig is called by NetworkManager or wicked to apply settings from sysconfig files and/or dynamic leases (dhcp,ppp). While wicked calls it for loopback interface as well, NetworkManager probably doesn't. The solution is IMO to add either: ExecStartPre=-/sbin/netconfig update to NetworkManager.service or: ExecStartPre=-/sbin/netconfig update -m nis to ypbind.service or add kind of boot.localnet systemd service. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587#c13
--- Comment #13 from Marius Tomaschewski
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587#c14
--- Comment #14 from Marius Tomaschewski
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587#c15
--- Comment #15 from Ludwig Nussel
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587
http://bugzilla.opensuse.org/show_bug.cgi?id=1129587#c20
--- Comment #20 from Anja Stock
(In reply to Ludwig Nussel from comment #17)
So don't be childish. find a better solution then.
If somebody is childisch, than it's you. We have a broken tool, which is doing things which it due to a bug not allowed to do. You propose now to workaround all consumers of the domainname syscall? This is not only ypbind, getdomainname(2) is not NIS specific. Fix the tool which is broken.
What exactly do you suggest here? What is your suggestion, how to fix that (precisely)? -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com