I update Tumbleweed once a week. This week 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. Maybe /var/run isn't there yet when rpcbind comes up?
El 07-04-2018 a las 16:10, Scott Simpson escribió:
I update Tumbleweed once a week. This week rpcbind didn't start up. I got
on boot. Maybe /var/run isn't there yet when rpcbind comes up?
rpcbind should take its lock on /run/rpcbind/ directory if that is really needed or find a less racy method of doing so.
FIll a bug report.