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

[David Hansen]

This is still a valid issue, I just performed a do-release-upgrade on a
v14.04 system yesterday and the same rpcbind issue reared it's ugly
little head.

Reading the posts here should conclude that it is an understood issue
for Xenial.

My post here was two years ago. This ticket was created four years ago.
If rpcbind package v0.2.3-0.4 (Released four years ago!) really does fix
this issue then what in the world is holding up it being included in
Xenial? 16.04.06 and the package still has not been included yet.

What further information is needed to work on this?

-- 
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