Control: retitle -1 "Regression: rpcbind doesn't start at boottime
on systemd controlled machines."
* Elimar Riesebieter <riese...@lxtec.de> [2015-11-15 13:56 +0100]:
> Package: rpcbind
> Version: 0.2.3-0.2
> Severity: important
>
> Can't run nis:
> # ypbind -no-dbus -broadcast -debug
> 1679: add_server() domain: mynisdomain, broadcast
> 1679: [Welcome to ypbind-mt, version 1.20.1]
> 1679: ping interval is 20 seconds
> Cannot register service: RPC: Unable to receive; errno = Connection refused
> 1679: Unable to register (YPBINDPROG, YPBINDVERS, udp).
>
> Restarting rpc bind gets me back to restart nis successfull.
It is not a restart. rpcbind doesn't start at bottime at all!
> # service rpcbind restart
> # service nis restart
Running
# systemctl start rpcbind
# service nis start
Works as well. nis package doesn't provide a service file.
> Reverting to rpcbind 0.2.1-6.1 solves the problem. Please notice
> that this happens only on systemd machines.
The systemd systems I've found this behavior are booting via
GRUB option:
GRUB_CMDLINE_LINUX_DEFAULT="init=/lib/systemd/systemd systemd.show_status=true"
> Running sysvinit only doesn't show this behaviour.
Elimar
--
We all know Linux is great... it does infinite loops in 5 seconds.
-Linus Torvalds
