http://bugzilla.suse.com/show_bug.cgi?id=1117217 http://bugzilla.suse.com/show_bug.cgi?id=1117217#c5 Thorsten Kukuk changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kukuk@suse.com |thomas.blume@suse.com Summary|ypbind (NIS) is not started |rpcbind fails to start |automatically although |(tumbleweed snapshot |configured to do so |20181120) |tumbleweed snapshot | |20181120 | Flags|needinfo?(obermiller@schwei | |zerbart.de) | --- Comment #5 from Thorsten Kukuk --- (In reply to Walter Obermiller from comment #4)

Immediately after booting: reservex:~ # journalctl| grep rpc Dec 11 10:00:23 reservex rpcbind[390]: rpcbind: /var/run/rpcbind.lock: No such file or directory Dec 11 10:00:23 reservex systemd[1]: rpcbind.service: Main process exited, code=exited, status=1/FAILURE Dec 11 10:00:23 reservex systemd[1]: rpcbind.service: Failed with result 'exit-code'.

Could this be a timing issue (rpcbind is not finished starting when ypbind tries to use rpcbind ?) I am a systemd-ignorant person.

No, rpcbind fails to start, and if rpcbind fails, systemd cannot fullfill the requirements of ypbind and cannot start it. It's not a problem of ypbind, that's only a followup error. No idea why rpcbind fails. Either your /var/run symlink to /run is broken, or the rpcbind systemd dependencies don't fit. -- You are receiving this mail because: You are on the CC list for the bug.