[Bug 1558196] Re: ypbind not able to socket activate rpcbind under systemd, fails at boot unless something else starts rpcbind

ChristianEhrhardt 1558196 at bugs.launchpad.net
Fri Jul 14 08:06:57 UTC 2017


The fix for 805167 is in Yakkety.
We need to consider that as an SRU for Xenial.

** Changed in: nis (Ubuntu)
       Status: Triaged => Fix Released

** Changed in: rpcbind (Ubuntu Xenial)
       Status: Confirmed => Triaged

** Tags added: server-next

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to rpcbind in Ubuntu.
https://bugs.launchpad.net/bugs/1558196

Title:
  ypbind not able to socket activate rpcbind under systemd, fails at
  boot unless something else starts rpcbind

Status in nis package in Ubuntu:
  Fix Released
Status in rpcbind package in Ubuntu:
  Fix Released
Status in nis source package in Xenial:
  Invalid
Status in rpcbind source package in Xenial:
  Triaged
Status in nis package in Debian:
  Fix Released

Bug description:
  did apt-get update/upgrade  March 16, 2016 
  Description:    Ubuntu Xenial Xerus (development branch)
  Release:        16.04

  rpcbind does not start on boot, tried various systemd debugging steps
  with no clues. After boot systemctl start rpcbind works. There is  a
  /etc/init.d/rpcbind and a /lib/systemd/system/rpcbind.service config
  files which is confusing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1558196/+subscriptions



More information about the foundations-bugs mailing list