http://bugzilla.suse.com/show_bug.cgi?id=1117217 http://bugzilla.suse.com/show_bug.cgi?id=1117217#c6 Thomas Blume <thomas.blume@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(obermiller@schwei | |zerbart.de) --- Comment #6 from Thomas Blume <thomas.blume@suse.com> --- (In reply to Thorsten Kukuk from comment #5)

(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.

Please provide the output of: ls -l /var/run If it tells 'No such file or directory' Provide the output of: systemctl status systemd-tmpfiles-setup.service otherwise, please run: systemctl start rpcbind.service and check the status. Is it still failing? -- You are receiving this mail because: You are on the CC list for the bug.