This bug was fixed in the package rpcbind - 0.2.3-0.2ubuntu0.1
---
rpcbind (0.2.3-0.2ubuntu0.1) xenial; urgency=medium
* d/rpcbind.service: Add WantedBy=multi-user.target, this should ensure
that rpcbind daemon is started before nis (Closes: #805167, LP: #1558196)
Thanks to
On Monday, August 10 2020, Dan Streetman wrote:
> autopkgtest note: nfs-utils(s390x) fails, but appears to have always
> failed; the test runs that 'passed' back in 2017 just skipped the
> now-failing testcase due to lack of machine isolation back then:
> "local-server-client SKIP Test requires
autopkgtest note: nfs-utils(s390x) fails, but appears to have always failed;
the test runs that 'passed' back in 2017 just skipped the now-failing testcase
due to lack of machine isolation back then:
"local-server-client SKIP Test requires machine-level isolation but testbed
does not provide
ubuntu@lp1558196-x:~$ dpkg -l|grep rpcbind
ii rpcbind 0.2.3-0.2
amd64converts RPC program numbers into universal addresses
ubuntu@lp1558196-x:~$ sudo reboot
...(reboot)...
ubuntu@lp1558196-x:~$ sudo systemctl status
Hello John, or anyone else affected,
Accepted rpcbind into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/rpcbind/0.2.3-0.2ubuntu0.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: rpcbind (Ubuntu Xenial)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558196
Title:
ypbind not able to socket activate rpcbind under systemd,
** Changed in: rpcbind (Ubuntu Xenial)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Description changed:
- did apt-get update/upgrade March 16, 2016
+ [Impact]
+
+ Due to a missing "WantedBy" directive in the .service file's [Install]
+ section, rpcbind does not properly
** Merge proposal linked:
https://code.launchpad.net/~sergiodj/ubuntu/+source/rpcbind/+git/rpcbind/+merge/387318
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558196
Title:
ypbind not able to
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
If this is still a valid and understood issue for Xenial then its status
should be Triaged, not Incomplete. Otherwise it looks like it doesn't
have enough information to be worked on. Please see
https://wiki.ubuntu.com/Bugs/Status
** Changed in: rpcbind (Ubuntu Xenial)
Status: Incomplete
date
Thu Jul 12 12:57:35 EDT 2018
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.4 LTS
Release:16.04
Codename: xenial
apt-cache policy rpcbind
rpcbind:
Installed: 0.2.3-0.2
Candidate: 0.2.3-0.2
This bug was opened on
** Changed in: rpcbind (Ubuntu Xenial)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558196
Title:
ypbind not able to socket activate rpcbind under systemd,
$ cat /etc/systemd/system/rpcbind.socket.d/override.conf
[Unit]
DefaultDependencies=no
Wants=rpcbind.target
Before=rpcbind.target
Fixed xenial for me. Would be nice to have a fixed package for LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@paelzer: Is this being considered for SRU? Could it still make it into
16.04.4?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558196
Title:
ypbind not able to socket activate rpcbind under
As nis needs no change set that to invalid.
** Changed in: nis (Ubuntu Xenial)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558196
Title:
ypbind not able to
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
The referenced fix below [2] mentioned by Michael in [1] fixes the issue
for my 16.04.
```
$ cat /etc/systemd/system/rpcbind.socket.d/override.conf
[Unit]
DefaultDependencies=no
Wants=rpcbind.target
Before=rpcbind.target
```
[1] https://bugs.debian.org/805167#88
[2]
Debian will accept a Non-Maintainer Upload. Since the backport is so
trivial (The patch from yakkety works perfectly), would that be possible
here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Still broken on Ubuntu 16.04.2 LTS. Completely ruined crucial NFS server
functionality. How it is even possible for such a critical bug to stay
unfixed for years??
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm not sure anyone in charge cares...
The solution I felt back to is changing my authentication system...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558196
Title:
ypbind not able to socket
Bump.
Almost one year passed, still broken in Xenial... Why not backport
Yakkety or Debian's fix to Xenial?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558196
Title:
ypbind not able to socket
(I mean the fix introduce in 0.2.3-0.4 which is only available in
yakkety.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558196
Title:
ypbind not able to socket activate rpcbind under systemd,
Any plan to incorporate at least the first fix described here into Xenial?
This bug just prevents any machine using nis to migrate to the new LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558196
Jacques,
Ditto for rpcbind patch not being enough. I have traced the issue via syslogs
to nis starting too early, before kernel has brought network interfaces up.
**If** the network interfaces get up "fast", then boot succeeds. Otherwise
nfs fails and nameserver might never be there, and
oops.. typo ... nis fails (not nfs fails)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558196
Title:
ypbind not able to socket activate rpcbind under systemd, fails at
boot unless something
Same issue here, my machines now get automatically updated to the new
LTS and rpcbind/nis break.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558196
Title:
ypbind not able to socket activate
Any idea when this package/fix is going to hit the Xenial repos? 23/07
and 16.04.1 and package still not available
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558196
Title:
ypbind not able to
I also use NIS, because it supports NFS-exports, mail-aliases, and
netgroups in a lot of files.
Simply writing:
# /bin/systemctl add-wants multi-user.target rpcbind.service
is not enough. Sometimes boot is OK, sometimes not.
Starting manually rpcbind then ypbind is not OK. For instance, syslogd,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nis (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558196
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rpcbind (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558196
** Also affects: nis (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: rpcbind (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package rpcbind - 0.2.3-0.4
---
rpcbind (0.2.3-0.4) unstable; urgency=medium
* Non-maintainer upload.
* debian/rcpbind.service: Add WantedBy=multi-user.target, this should ensure
that rpcbind daemon is started before nis (Closes: #805167, LP:
** Changed in: nis (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558196
Title:
ypbind not able to socket activate rpcbind under systemd, fails at
** Also affects: nis (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805167
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558196
Title:
@John Sopko
yes, that is the trick!
Strange however that for all previous releases this parameter could be left at
compat.
So I did not think of if to check this parameter, but thank you very much!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Does your /etc/nsswitch.conf have:
group: files nis
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558196
Title:
ypbind not able to socket activate rpcbind under systemd, fails at
boot
It does not work completely!
You can log in, however de UID/GID settings are not correct.
yptest and ypcat give the right results. But groups just returns the local
group's and not the extra NIS-enabled groups.
The user is not able to access the server directory's if they need the extra
This has solved the issue for me also.
Ubuntu 16.04 with rpcbind 0.2.3-0.2- apt updated on March 21st 15:15 GMT.
/bin/systemctl add-wants multi-user.target rpcbind.service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This has solved the issue for me also.
Ubuntu 16.04 with rpcbind 0.2.3-0.2- apt updated on March 21st 15:15 GMT.
/bin/systemctl add-wants multi-user.target rpcbind.service
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rpcbind
I'd like to confirm that on Ubuntu 16.04 the following allowed rpcbind to start
on fresh bootup:
/bin/systemctl add-wants multi-user.target rpcbind.service
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rpcbind in Ubuntu.
I'd like to confirm that on Ubuntu 16.04 the following allowed rpcbind to start
on fresh bootup:
/bin/systemctl add-wants multi-user.target rpcbind.service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Doing this forces rpcbind to start on boot and then nis starts
correctly:
# /bin/systemctl add-wants multi-user.target rpcbind.service
Created symlink from
/etc/systemd/system/multi-user.target.wants/rpcbind.service to
/lib/systemd/system/rpcbind.service
--
You received this bug notification
Doing this forces rpcbind to start on boot and then nis starts
correctly:
# /bin/systemctl add-wants multi-user.target rpcbind.service
Created symlink from
/etc/systemd/system/multi-user.target.wants/rpcbind.service to
/lib/systemd/system/rpcbind.service
--
You received this bug notification
IMHO if the rpcbind service is enabled it should just start at boot time
and not have to be self activated.
Found this but no real good solution.
"Regression: rpcbind doesn't start at boottime on systemd controlled
machines."
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805167
** Bug
** Changed in: nis (Ubuntu)
Status: New => Triaged
** Changed in: rpcbind (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558196
Title:
ypbind not able
** Changed in: nis (Ubuntu)
Status: New => Triaged
** Changed in: rpcbind (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rpcbind in Ubuntu.
https://bugs.launchpad.net/bugs/1558196
Title:
IMHO if the rpcbind service is enabled it should just start at boot time
and not have to be self activated.
Found this but no real good solution.
"Regression: rpcbind doesn't start at boottime on systemd controlled
machines."
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805167
** Bug
47 matches
Mail list logo
