The kernel gave those error messages because it could not talk to the rpc.statd server. Sorry, I don't understand why you think it would be a bug in initscripts... Do you think I > > should try to upgrade user-mode-linux? > > it shouldn't make much of a difference. > Anyway I still can't reproduce the problem even automounting an Full text and rfc822 format available. have a peek at this web-site
Message #45 received at [email protected] (full text, mbox, reply): From: Oren Held
View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by David the H. 04-01-2011, 09:20 AM #2 AlucardZero Senior Member Registered: May 2006 But there was also a bug in the debian packaging system keeping it from transitioning properly. Yes, it's Debian as my profile says. rpc.statd is not running4mount to nfs server failed, system error: no route to host0NFS: failed to create MNT RPC client status = -1012Vagrant: failed to mount nfs shared folder (mount.nfs: Operation
Even rpcinfo-0.2.0-2 installed, this problem still exists. Message #46 received at [email protected] (full text, mbox, reply): From: Nicolas Boullis
Copy sent to Anibal Monsalve Salazar
Full text and rfc822 format available. Rpc.statd Service Linked 1 Not mounting NFS shared folders with vagrant libvirt provider in Debian Jessie Related 3Why is file ownership inconsistent between two systems mounting the same NFS share?2OpenBSD NFS server with In that case, it sounds more like a bug in initscripts to me? /* Steinar */ - always trigger happy at the reassigning :-) -- Homepage: http://www.sesse.net/ Information forwarded to [email protected], The clients are Linux.
Date: Mon, 04 Dec 2006 11:52:52 +0100 Hi, Sorry for the late reply, I was on holiday. http://www.linuxquestions.org/questions/linux-networking-3/rpc-statd-not-running-872348/ Copy sent to Anibal Monsalve Salazar
Acknowledgement sent to Michael Rasmussen
Date: Tue, 29 Dec 2009 09:52:52 +0800 Hi, I can reproduce this nfs-common problem in my Sid system. This thread was almost 6 years old, and quite a lot has changed in nfs since then, so it's not longer applicable anyway. UNIX is a registered trademark of The Open Group. Copy sent to Anibal Monsalve Salazar
Date: Mon, 20 Nov 2006 17:55:12 +0100 On Mon, Nov 20, 2006 at 12:03:30PM +0100, Nicolas Boullis wrote: > Although I don't think it makes a big difference, note that this Failed To Create Rpc Listeners Exiting Redhat See "systemctl status rpc-statd.service" and "journalctl -xe" for details.mount.nfs: rpc.statd is not running but is required for remote locking.mount.nfs: Either use '-o nolock' to keep locks local, or start statd.mount.nfs: an Cheers, Nicolas Information forwarded to [email protected], Debian sysvinit maintainers
This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. Main Menu LQ Calendar LQ Rules LQ Sitemap Site FAQ View New Posts View Latest Posts Zero Reply Threads LQ Wiki Most Wanted Jeremy's Blog Report LQ Bug Syndicate Latest Your /etc/exports looks ok to me. Failed To Start Nfs Status Monitor For Nfsv2/3 Locking You could probably find that yourself with locate statd which gives you among others /etc/init.d/statd.
and the insecure bit i needed to make macosx like it. I've been looking around the web, but I haven't been able to find anything useful, or even understandable to me. Installing, enabling, and starting the rpcbind service solved the problem. Copy sent to Debian sysvinit maintainers
Acknowledgement sent to Julien BLACHE
Tony Houghton wrote: > I've got the same problem. Gunderson"