Bug#562737: seems to be back
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
With the upgrade to nfs-common 1:1.2.3-1 this problem seems to be back.
Using rpcbind instead of portmap (6.0.0-3) nfs-common starts cleanly.
nfs-common version 1:1.2.2-5 + portmap didn't show this problem either.
"rpc.statd -dF" shows (using portmap):
rpc.statd: Version 1.2.3 starting
rpc.statd: Flags: No-Daemon Log-STDERR TI-RPC
sm-notify: Version 1.2.3 starting
sm-notify: Already notifying clients; Exiting!
rpc.statd: Local NSM state number: 3
rpc.statd: Failed to unregister program 100024, version 1
rpc.statd: Effective UID, GID: 101, 0
rpc.statd: Failed to register (statd, 1, udp)
rpc.statd: Failed to register (statd, 1, tcp)
rpc.statd: Failed to register (statd, 1, udp6)
rpc.statd: Failed to register (statd, 1, tcp6)
rpc.statd: failed to create RPC listeners, exiting
"rpc.statd -dF" shows (using rpcbind):
rpc.statd: Version 1.2.3 starting
rpc.statd: Flags: No-Daemon Log-STDERR TI-RPC
sm-notify: Version 1.2.3 starting
sm-notify: Already notifying clients; Exiting!
rpc.statd: Local NSM state number: 3
rpc.statd: Effective UID, GID: 101, 0
rpc.statd: Waiting for client connections
The old "rpc.statd -dF" (version 1:1.2.2-5) shows together
with portmap:
rpc.statd: Version 1.2.2 starting
rpc.statd: Flags: No-Daemon Log-STDERR
sm-notify: Version 1.2.2 starting
sm-notify: Already notifying clients; Exiting!
rpc.statd: Local NSM state number: 3
rpc.statd: Failed to unregister program 100024, version 1
rpc.statd: Effective UID, GID: 101, 0
rpc.statd: Waiting for client connections
Please mail if I can help to track this down.
Regards
Harri
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk2YdzYACgkQUTlbRTxpHjcA3ACfajDYwO8qgYPDxlZH6sknjCZr
rd4AoIedQJo+BWeY50F9uH5d7huLAwxK
=ZGNO
-----END PGP SIGNATURE-----
Reply to: