Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Mount: 1831-010

1,114 views
Skip to first unread message

Big Kahuna

unread,
Oct 4, 2001, 12:37:14 PM10/4/01
to
Hi gang, I was hoping someone in here would be kind enough to help me out in
a pinch... I keep receiving the following error:

mount: 1831-010 server myservername not responding: RPC: 1832-019 program
not registered

As far as I know, all the programs on the system ARE registered. Any ideas
on how I can fix this problem?

Thanks in advance!


sp2 admin

unread,
Oct 4, 2001, 3:24:06 PM10/4/01
to
sounds like the filesystem you are trying to mount via nfs was not exported
properly from nfs server. otherwise, check if /usr/sbin/rpc.mountd is
running properly

Luterin

unread,
Oct 4, 2001, 4:32:48 PM10/4/01
to
> mount: 1831-010 server myservername not responding: RPC: 1832-019 program
> not registered
>
Also,
- make sure the portmapper is running (man portmap)
- if need to start portmap, stopsrc -g nfs, startsrc -s portmap,
startsrc -g nfs
- make sure myservername is reachable

-Lute.


Big Kahuna

unread,
Oct 4, 2001, 5:17:25 PM10/4/01
to
Well it turns out that one of our knucklehead sysadmins started the nfsd but
nothing else. So, after administering a "wet willy" and giving him a "pink
belly," I corrected the problem. If anyone else runs into this "problem,"
do what I didn't do:

1. Check to see if you can ping the server [okay, I actually DID do that
part just in case].
2. run lssrc -a | grep nfs to make sure the nfs system is running [I got a
bunch of "inoperative" messages!].
3. also run ps -ef | grep nfs to make sure some knucklehead didn't already
start some portions of nfs independent of the rest of the resource group [as
was the case in our little scenario].
4. If any portion of nfs is running? Kill it.
5. Then start [restart] the services by issuing the startsrc -g nfs command.

Then everything should be hunkey dorey.

Thanks for the laughs!

"Big Kahuna" <kah...@bigman.com> wrote in message
news:_e0v7.607948$T97.82...@typhoon.nyroc.rr.com...

0 new messages