Mailinglist Archive: opensuse-bugs (6095 mails)

< Previous Next >
[Bug 1088702] rpcbind not starting with 20180404 Tumbleweed release
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 19 Apr 2018 07:15:26 +0000
  • Message-id: <bug-1088702-21960-nBjfO6MG7W@http.bugzilla.suse.com/>
http://bugzilla.suse.com/show_bug.cgi?id=1088702
http://bugzilla.suse.com/show_bug.cgi?id=1088702#c8

--- Comment #8 from Thomas Blume <thomas.blume@xxxxxxxx> ---
(In reply to Scott Simpson from comment #7)
It is strange. The boot messages say rpcbind failed yet it is running right
after boot (see the attached file). ypserv doesn't start up because of a
dependency failure. You can see these messages in the "journalctl -axb"
output.

I see the problem.
The boot commandline shows:

rd.lvm.lv=system/usr rd.lvm.lv=system/swap

which only activates the logical volumes for usr and swap at the initrd stage.

That means /var is only activated later in the boot process and after the first
rpcbind startup:

-->
Apr 18 14:11:32 madhatter rpcbind[657]: rpcbind: /var/run/rpcbind.lock: No such
file or directory
Apr 18 14:11:32 madhatter systemd[1]: rpcbind.service: Main process exited,
code=exited, status=1/FAILURE
Apr 18 14:11:32 madhatter systemd[1]: rpcbind.service: Failed with result
'exit-code'.
Apr 18 14:11:32 madhatter systemd[1]: Failed to start RPC Bind.
-- Subject: Unit rpcbind.service has failed
[...]
Apr 18 14:11:38 madhatter systemd[1]: Mounting /var...
-- Subject: Unit var.mount has begun start-up
--<

Please add:

rd.lvm.lv=system/var

to the boot parameters to make /var available in time.

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >