group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #36470
[Bug 1890276] Re: inetd does not answer broadcast requests
# working env: xenial (without inetd)
*:111 *:* users:(("rpcbind",pid=6679,fd=6))
*:919 *:* users:(("rpcbind",pid=6679,fd=7))
*:998 *:* users:(("rpc.rstatd",pid=6759,fd=3))
(c)rafaeldtinoco@xenial:~$ sudo tcpdump -i eth0 -n
12:23:59.243382 IP 10.250.97.142.38369 > 10.250.97.255.111: UDP, length 100
12:23:59.245356 IP 10.250.97.213.919 > 10.250.97.142.38369: UDP, length 140
# working env: bionic (without inetd)
0.0.0.0:111 0.0.0.0:* users:(("rpcbind",pid=1073,fd=6))
0.0.0.0:825 0.0.0.0:* users:(("rpcbind",pid=1073,fd=7))
0.0.0.0:752 0.0.0.0:* users:(("rpc.rstatd",pid=10753,fd=3))
(c)rafaeldtinoco@bionic:~$ sudo tcpdump -i eth0 -n
11:49:40.673843 IP 10.250.97.227.38276 > 10.250.97.255.111: UDP, length 100
11:49:40.677280 IP 10.250.97.142.825 > 10.250.97.227.38276: UDP, length 140
----
# not-working env: eoan (without inetd)
0.0.0.0:111 0.0.0.0:* users:(("rpcbind",pid=2799,fd=5),("systemd",pid=1,fd=32))
0.0.0.0:901 0.0.0.0:* users:(("rpc.rstatd",pid=2846,fd=3))
(c)rafaeldtinoco@eoan:~$ sudo tcpdump -i eth0 -n
11:54:17.931899 IP 10.250.97.227.48295 > 10.250.97.255.111: UDP, length 100
# not-working env: focal (without inetd)
0.0.0.0:111 0.0.0.0:* users:(("rpcbind",pid=6184,fd=5),("systemd",pid=1,fd=42))
127.0.0.1:862 0.0.0.0:* users:(("rpc.statd",pid=6198,fd=5))
0.0.0.0:39800 0.0.0.0:* users:(("rpc.statd",pid=6198,fd=8))
note: systemd has rpcbind socket, removing that variable had no effect.
----
But I noticed rpcbind is running as _rpc user in the non-working
environments.
There was a major change in rpcbind from affected versions.
And… finally:
(c)rafaeldtinoco@groovy:~$ rup
bionic.lxd 12:56 up 18:31, load 0.22 0.16 0.10
groovy.lxd 12:56 up 12:51, load 0.22 0.16 0.10
xenial.lxd 12:56 up 18:26, load 0.22 0.16 0.10
I had to replace groovy rpcbind with rpcbind from bionic.
Now, in some other time, I'll have to check what changes to rpcbind (a
lot) made this happen.
** Summary changed:
- inetd does not answer broadcast requests
+ rpcbind changes after bionic broke rup broadcast feature
** Also affects: rpcbind (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: openbsd-inetd (Ubuntu)
** No longer affects: openbsd-inetd (Ubuntu Xenial)
** No longer affects: openbsd-inetd (Ubuntu Eoan)
** No longer affects: openbsd-inetd (Ubuntu Bionic)
** No longer affects: openbsd-inetd (Ubuntu Focal)
** Changed in: rpcbind (Ubuntu)
Status: New => Confirmed
** Changed in: rpcbind (Ubuntu Focal)
Status: New => Confirmed
** Changed in: rpcbind (Ubuntu Eoan)
Status: New => Confirmed
** Changed in: rpcbind (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: rpcbind (Ubuntu Xenial)
Status: New => Fix Released
** Changed in: rpcbind (Ubuntu)
Importance: Undecided => Medium
** Changed in: rpcbind (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1890276
Title:
rpcbind changes after bionic broke rup broadcast feature
Status in rpcbind package in Ubuntu:
Confirmed
Status in rpcbind source package in Xenial:
Fix Released
Status in rpcbind source package in Bionic:
Fix Released
Status in rpcbind source package in Eoan:
Confirmed
Status in rpcbind source package in Focal:
Confirmed
Bug description:
When I call inetd services rup or rusersd in broadcast mode, I get
answers from my Ubuntu 18.04 machines only. An Ubuntu 20.04 machine
(here rzpc101) answers only when addressed directly:
zierke@rzpc100$ rup
rzpc100.informatik.un 14:02 up 10 days, 8:30, load 0.52 0.38 0.23
rzlinux.informatik.un 14:02 up 1 day, 3:12, load 0.04 0.09 0.03
rzpc174.informatik.un 14:02 up 4 days, 19:28, load 0.00 0.01 0.00
^C
zierke@rzpc100$ rup rzpc101
rzpc101.informatik.un 14:02 up 3:29, 3 users, load 0.33 0.32 0.15
zierke@rzpc100$ rusers
rzpc100.informatik.u zierke zierke
rzlinux.informatik.u zierke zierke zierke
^C
zierke@rzpc100$ rusers rzpc101
rzpc101.informatik.u zierke zierke zierke
zierke@rzpc101$ lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04
zierke@rzpc100$ lsb_release -rd
Description: Ubuntu 18.04.4 LTS
Release: 18.04
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: openbsd-inetd 0.20160825-4build1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 4 14:03:06 2020
InstallationDate: Installed on 2020-07-24 (11 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: openbsd-inetd
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1890276/+subscriptions