| 1 |
On Tue, 25 Sep 2007, John Blinka wrote: |
| 2 |
> I think it happens when booting, but I see this message in the system log: |
| 3 |
> |
| 4 |
> Sep 23 21:12:01 tobey rc-scripts: ERROR: cannot start nfs as |
| 5 |
> rpc.statdcould not start |
| 6 |
|
| 7 |
John, I've hesitated to join this thread because I haven't felt I've been able |
| 8 |
to throw any light on your problem - just hoped that you'd get some |
| 9 |
resolution that I could then apply to my own situation which is very similar |
| 10 |
to yours ... but as it's not looking so "rosy" maybe my experience may spark |
| 11 |
some other avenue to explore? |
| 12 |
|
| 13 |
I've been running an amd64 nfs mount successfully for some months on this |
| 14 |
machine until around about mid August (difficult to tell exactly when as I |
| 15 |
had temporary wireless network about then because of building alterations) |
| 16 |
but from that point on have had major problems trying to mount the nfs |
| 17 |
directory. No point in going though all the error codes etc. again as they |
| 18 |
are pretty similar to yours - main one is always "mount: RPC: Timed out", but |
| 19 |
I have variations. Like you I _never_ get it to mount from boot as it always |
| 20 |
did in earlier days: now, with a bit of patience, and re-running nfs, |
| 21 |
nfsmount - and sometimes portmap scripts, I can sometimes get it to mount. |
| 22 |
Sometimes I can get it to mount using the manual mount command. Other times |
| 23 |
it just plain refuses to do anything until I go away for an hour or so - then |
| 24 |
come back and take it by surprise with nfsmount or manual mount and wham, bam |
| 25 |
we're away laughing! Or sort of. |
| 26 |
|
| 27 |
I've googled extensively and followed up avenue after avenue, wiki after wiki: |
| 28 |
I've recompiled nfs-utils, portmap, baselayout. I've altered hosts.allow and |
| 29 |
hosts.deny, etc., etc., and then tried all Emil's suggestions as on this |
| 30 |
thread. But I still get nowhere, and I think I've now spent so much time on |
| 31 |
it that I really can't see the wood for the trees! It's obviously something |
| 32 |
so simple, but I just can't see it. Feel a bit of a prat, but this morning |
| 33 |
was the last straw when I thought I'd better join your thread: no success |
| 34 |
until I left it and went away for an hour - then came back and |
| 35 |
input "mount -t nfs 192.168.0.216:/usr/portage /mnt/nfs_portage/" and away we |
| 36 |
went. All ok, just in time for a cronjob emerge --sync. |
| 37 |
|
| 38 |
But not very satisfactory. It's almost as though the original "mount" called |
| 39 |
by the scripts and earlier efforts takes some time to "die", and a fresh |
| 40 |
instance does the trick! But I don't know enough about the process to know if |
| 41 |
that's so - I just seem to recall someone somewhere in my endless searches |
| 42 |
saying something along those lines ... |
| 43 |
|
| 44 |
Strange that it's just the two of us to be afflicted by this at about the same |
| 45 |
time? AAMOI have you tried taking your machine by surprise? |
| 46 |
|
| 47 |
Bogo |
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
|
| 53 |
-- |
| 54 |
gentoo-user@g.o mailing list |
Archives