thank...
--
[jaunty] nfs-common fails to start unless NEED_STATD=no
https://bugs.launchpad.net/bugs/305589
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ub
This is not a kernel problem; the error message indicates that some
other statd process is already running that hasn't been properly stopped
during upgrade, so starting a second statd process fails.
This bug has been resolved in karmic with the conversion of nfs-common
to properly-managed upstart
Duplicated the problem and fix described above. It's still there in:
#uname -r
2.6.28.15-generic
NEED_STATD=no in /etc/default/nfs-common solves the issue.
--
[jaunty] nfs-common fails to start unless NEED_STATD=no
https://bugs.launchpad.net/bugs/305589
You received this bug notification becaus
Hello
Running Jaunty 64-bit 2.6.28.15 generic, it afects me and is cleared by:
#sudo /etc/init.d/nfs-common restart
Seems some unitialized thing, service was running.
Cheers
Antonio
--
[jaunty] nfs-common fails to start unless NEED_STATD=no
https://bugs.launchpad.net/bugs/305589
You receive
I do not have a statd package installed. Instead:
# dpkg -S /sbin/rpc.statd
nfs-common: /sbin/rpc.statd
which is:
nfs-common 1:1.1.4-1ubuntu1
NFS 3 works fine with Jaunty. At least it has been very stable in
transfers for me. I like NFS, preferring it to CIFS. FWIW, with NFSv4,
you'll
I've just upgraded a Hardy machine to Jaunty and experienced this
problem. Kernel is 2.6.28-11.
On the machine in question, I'm still using nfs v3, so the NEED_STATD=no
workaround did not help.
I think I've solved it by installing the "statd" package and starting
that daemon.
Haven't had a chanc
As Noel commented, the issue seems to be fixed by the most recent kernel
package:
$ uname -a
Linux 2.6.28-4-server #6-Ubuntu SMP Thu Jan 1 23:42:42 UTC 2009 i686 GNU/Linux
Even when removing the suggested changes to /etc/defaults/nfs-common,
the init script starts without problems.
--
[jaunty]
Do you still see this problem after upgrading the kernel to 2.6.28-4?
$ uname -r
2.6.28-4-generic
$ ps auxwww | grep rpc
statd 3150 0.0 0.0 10300 520 ?Ss Jan02 0:00
/sbin/rpc.statd
and just to confirm that the command in question works:
# /etc/init.d/nfs-common sta
Confirmed on a brand new Jaunty installation as of 2009-01-02.
Suggested change in /etc/default/nfs-common file solves the issue.
** Changed in: nfs-utils (Ubuntu)
Status: New => Confirmed
--
[jaunty] nfs-common fails to start unless NEED_STATD=no
https://bugs.launchpad.net/bugs/305589
