Comment 9 for bug 484209
Revision history for this message
| Mikkel Christensen (mbc-baekhoej) wrote | #9 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Sorry, my above comment got posted before I was done writing.
Before applying Malcolm's patch, I got:
start: Job failed to start
when I tried to start statd.
This problem was preventing me from using NFS shares mounted by autofs. Needless to say, it was a critical problem for me that users could not access their files! I really think that this fix needs to be applied to Karmic most urgently. I can't be the only one affected.
If you try to reproduce this bug, please keep in mind that it doesn't fail every time. Being a race condition it succeeds sometimes and fails sometimes.
And finally: Thank you THANK YOU to Malcolm for providing the explanation as well as a solution. I had been tearing my hair out over this one!
It took me hours of work to track down this solution. I will post some of the symptoms I had of the NFS failures here so that other googlers may find this solution more easily:
/var/log/syslog:
automount[1812]: attempting to mount entry /mnt/fileserver
automount[5556]: >> mount.nfs: rpc.statd is not running but is required for remote locking.
init: statd pre-start process (6242) terminated with status 1