http://bugzilla.opensuse.org/show_bug.cgi?id=1088702 Bug ID: 1088702 Summary: rpcbind not starting with 20180404 Tumbleweed release Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: ssimpson@alumni.usc.edu QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- rpcbind didn't start up. I got Apr 07 11:00:21 madhatter rpcbind[641]: rpcbind: /var/run/rpcbind.lock: No such file or directory Apr 07 11:00:21 madhatter systemd[1]: rpcbind.service: Main process exited, code=exited, status=1/FAILURE Apr 07 11:00:21 madhatter systemd[1]: rpcbind.service: Failed with result 'exit-code'. Apr 07 11:00:21 madhatter systemd[1]: Failed to start RPC Bind. Apr 07 11:00:21 madhatter systemd[1]: Dependency failed for NIS/YP Clients to NIS Domain Binder. Apr 07 11:00:21 madhatter systemd[1]: ypbind.service: Job ypbind.service/start failed with result 'dependency'. Apr 07 11:00:21 madhatter systemd[1]: Dependency failed for NIS/YP Server. Apr 07 11:00:21 madhatter systemd[1]: ypserv.service: Job ypserv.service/start failed with result 'dependency'. on boot. rpcbind should take its lock on /run/rpcbind/ directory if that is really needed or find a less racy method of doing so. -- You are receiving this mail because: You are on the CC list for the bug.