NFS status

[Andrew Kelly]

On Tue, 2005-08-30 at 01:44, brad.mugleston at comcast.net wrote:
> On Mon, 29 Aug 2005, Andrew Kelly wrote:
> 
> > On Mon, 2005-08-29 at 05:27, brad.mugleston at comcast.net wrote:
> > > On Sun, 28 Aug 2005, inode0 wrote:
> > >
> > > > On 8/28/05, brad.mugleston at comcast.net <brad.mugleston at comcast.net> wrote:
> > > > > The error I get is:
> > > > >
> > > > > mount: RPC: Remote System Error - No Route to Host
> > > > >
> > > > > and that is where I'm stuck.
> > > > >
> > > > > Suggestions?
> > > >
> > > > Perhaps a firewall on the FC2 box? I don't have a fedora box handy so
> > > > I'm going to guess the syntax to check as
> > > >
> > > > # service iptables status
> > > >
> > > > What does that return? If it is on try
> > > >
> > > > # service iptables stop
> > > >
> > > > and see if NFS starts working ...
> > > >
> > > > John
> > > >
> > > YES!  OK, the firewall was running - now it's stopped and I can
> > > now ssh from the client to the server (no more running up and
> > > down two flights of stairs to change things).  The error I now
> > > get when mounting my server is
> > >
> > > mount: RPC: Program Not Registered
> > >
> > > Were getting close, I can feel it (plus I have to get up in 7 1/2
> > > hours).
> >
> > Portmapper service running?
> >
> 
> Running rpcinfo -p I get the following:
>  program vers proto   port
>     100000    2   tcp    111  portmapper
>     100000    2   udp    111  portmapper
>     100024    1   udp  32769  status
>     100024    1   tcp  32768  status
>     391002    2   tcp  32769  sgi_fam
>     100011    1   udp    829  rquotad
>     100011    2   udp    829  rquotad
>     100011    1   tcp    832  rquotad
>     100011    2   tcp    832  rquotad
>     100003    2   udp   2049  nfs
>     100003    3   udp   2049  nfs
>     100021    1   udp  32771  nlockmgr
>     100021    3   udp  32771  nlockmgr
>     100021    4   udp  32771  nlockmgr
>     100005    1   udp  32772  mountd
>     100005    1   tcp  32770  mountd
>     100005    2   udp  32772  mountd
>     100005    2   tcp  32770  mountd
>     100005    3   udp  32772  mountd
>     100005    3   tcp  32770  mountd
> 
> I believe that will tell you what is running - 

Yeah, looks about right.

As you'll have seen in other mail, the portmapper service needs to be
running on both server and client.

> Been doing more
> reading and I'm not sure what the problem is so I'm going to go
> through all the files (/etc/exports, /etc/hosts.allow,
> /etc/hosts.deny and anything else I can find) to make sure I
> don't have a typo someplace.

These would be interesting to see.

> I have read that portmapper is suppose to be running before NFS -
> if I discover that to not be true how does one go about changing
> the order?

The quickest and easiest I can think of without yet having had a good
tea is: use chkconfig.
Look for the chkconfig line in the early parts of the init.d scripts in
question, adjust the start and stop priorities as desired,
run chkconfig <init.d-script-name> reset on any modified files (assuming
of course these services are controlled by chkconfig. man chkconfig for
more info, of course.)

Off the top of my not-yet-up-to-speed nugget, I believe the starting
order should be portmap, netfs, nfs, but don't take that as the gospel.

Andy

> Thanks,
> 
> Brad
> 
> _______________________________________________
> Redhat-install-list mailing list
> Redhat-install-list at redhat.com
> https://www.redhat.com/mailman/listinfo/redhat-install-list
> To Unsubscribe Go To ABOVE URL or send a message to:
> redhat-install-list-request at redhat.com
> Subject: unsubscribe