[jaunty] nfs-common fails to start unless NEED_STATD=no
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nfs-utils (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
After an upgrade from intrepid to jaunty, I installed nfs-common and attempted to start the nfs-common service.
root@blumonc:
* Starting NFS common utilities [fail]
/var/log/daemon.log had this error:
Dec 5 12:53:01 blumonc rpc.statd[10235]: Version 1.1.4 Starting
Dec 5 12:53:01 blumonc sm-notify[10236]: Already notifying clients; Exiting!
Dec 5 12:53:01 blumonc rpc.statd[10235]: unable to register (statd, 1, udp).
After making the following change to /etc/defaults/
# Do you want to start the statd daemon? It is not needed for NFSv4.
NEED_STATD=no
root@blumonc:
* Starting NFS common utilities [ OK ]
Changed in nfs-utils: | |
importance: | Undecided → High |
Confirmed on a brand new Jaunty installation as of 2009-01-02.
Suggested change in /etc/default/ nfs-common file solves the issue.