[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#562737: closed by Luk Claes <luk@debian.org> (Bug#562737: fixed in nfs-utils 1:1.2.2-5)



Luk Claes wrote:
> Ok, so it seems to be portmap specific. It would be nice if you could
> try portmap from experimental (similar fix as rpcbind got for a related
> bug) to see if that fixes it.

Doesn't help.

  # apt-get install -t experimental portmap
  Reading package lists... Done
  Building dependency tree       
  Reading state information... Done
  The following packages will be REMOVED:
    rpcbind
  The following NEW packages will be installed:
    portmap
  0 upgraded, 1 newly installed, 1 to remove and 297 not upgraded.
  Need to get 39.0 kB of archives.
  After this operation, 4,096 B of additional disk space will be used.
  Do you want to continue [Y/n]? 
  Get:1 http://ftp.us.debian.org/debian/ experimental/main portmap amd64 6.0.0-5 [39.0 kB]
  Fetched 39.0 kB in 0s (69.8 kB/s)
  Preconfiguring packages ...
  dpkg: rpcbind: dependency problems, but removing anyway as you requested:
   nfs-common depends on rpcbind | portmap; however:
    Package rpcbind is to be removed.
    Package portmap is not installed.
    Package rpcbind which provides portmap is to be removed.
   fam depends on portmap; however:
    Package portmap is not installed.
    Package rpcbind which provides portmap is to be removed.
   nfs-common depends on rpcbind | portmap; however:
    Package rpcbind is to be removed.
    Package portmap is not installed.
    Package rpcbind which provides portmap is to be removed.
  (Reading database ... 324403 files and directories currently installed.)
  Removing rpcbind ...
  Stopping rpcbind daemon....
  Processing triggers for man-db ...
  Selecting previously deselected package portmap.
  (Reading database ... 324396 files and directories currently installed.)
  Unpacking portmap (from .../portmap_6.0.0-5_amd64.deb) ...
  Processing triggers for man-db ...
  Setting up portmap (6.0.0-5) ...
  Starting portmap daemon....
  There are RPC services which were registered with the portmapper
  before the configuration was changed.
  You need to manually restart them in order for the changes to take effect.
  Current registered services:
  ------------------------------------------------
      391002    2   tcp    923  sgi_fam
  ------------------------------------------------

  # /sbin/rpc.statd -Fd
  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: 102, 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

Bob



Reply to: