RE: nfs issue...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



got it...

it was the iptables....

now... how/what do i have to do to the iptables app to get it to run/coexist
with nfs...

a former "linux" admin had set things up..and he's nowhere to be found!!!

thanks..

-bruce


-----Original Message-----
From: Pete Nesbitt [mailto:pete@xxxxxxxxx]
Sent: Thursday, July 01, 2004 5:36 PM
To: bedouglas@xxxxxxxxxxxxx; General Red Hat Linux discussion list
Subject: Re: nfs issue...


On July 1, 2004 05:22 pm, bruce wrote:
> also....
>
> what is an "empty mount point" and how does one go about creating one!!!!!

A "mount point" is simply a directory where you want to mount a file system.
An empty one would be an empty dirrectory, one that does not contain other
files nor is it being used as a mount point for another fs. (It is possible
to mount over-top of a non-empty directory, making it somewhat hidden)

So, to create a mount point called /mnt/remote_nfs_share
... "mkdir /mnt/remote_nfs_share" :)


>
> thanks
>
>
> ok..
>
> for now i seem to have gotten the appropriate services up/running on the
> nfs server... i made a change to the /etc/export file to allow a client
> linux box to have rw access to a idr "/colleges/data"....
>
> i haven't made any other changes to the server (i still can't get the NFS
> Server Config app to work under gnome. It's throwing python errors.... The
> actual app is the redhat-config-nfs app)

never used it, sorry.

>
> i tried to access the nfs server from the client and got a "connection
> refused" message....
>
> in reading through various threads on google.. i come across the
allow/deny
> files.. but i thought if the client wasn't listed in either file.. it
> should be allowed...

If BOTH /etc/hosts.allow & /etc/hosts.deny are empty, then all access is
allowed. If there is anything beyond commented lines in either file, then
any
service built to use tcpwrappers (or its lib) must pass the rules those two
files create. If nothing applies, (no catch-all rules) then the connection
is
allowed. (is there anything in either file?)

Do you have iptables running?  Try connecting after 'service iptables stop'

>
> any ideas/comments welcome..!!!!
>
> thanks
>
> -bruce
>
>
> -----Original Message-----
> From: redhat-list-bounces@xxxxxxxxxx
> [mailto:redhat-list-bounces@xxxxxxxxxx]On Behalf Of Pete Nesbitt
> Sent: Thursday, July 01, 2004 5:05 PM
> To: bedouglas@xxxxxxxxxxxxx; General Red Hat Linux discussion list
> Subject: Re: nfs issue...
>
> On July 1, 2004 04:01 pm, bruce wrote:
> > ok..
> >
> > here's what i get now.... (i rebooted the box)
> >
> > it looks like i don't have some processes running... also, the NFS
Server
> > Config dialog never comes up from the Gnome User Interface...
> >
> > any ideas as to what's going on...????
> >
> > thanks...
> >
> > -bruce
> >
> >
> > [root@lserver3 root]# rpcinfo -p
> >    program vers proto   port
> >     100000    2   tcp    111  portmapper
> >     100000    2   udp    111  portmapper
>
> You should have way more in rpcinfo (like nfs!). So are there errors or
> anything at the command line with (last email I said nfsd, but it's just
> nfs):
> # service nfs start
>
> > from "grep nfs /var/log/messages"
> >
> > [root@lserver3 root]# grep nfs /var/log/messages
> > Jul  1 14:24:25 lserver3 kernel: Installing knfsd (copyright (C) 1996
> > okir@xxxxxxxxxxxx).
> > Jul  1 14:24:26 lserver3 nfs: Starting NFS services:  succeeded
> > Jul  1 14:24:26 lserver3 nfs: rpc.rquotad startup failed
> > Jul  1 14:25:41 lserver3 nfs: Starting NFS services:  succeeded
> > Jul  1 14:25:41 lserver3 nfs: rpc.rquotad startup failed
> > Jul  1 14:36:11 lserver3 nfsd[14439]: nfssvc: Address already in use
>
> <snip...>
>
> I did a quick Goolgle, and there are several threads about this error,
> although I didn't see anything explaining/resolving it. Might be worth
some
> 'quality time'.
>
> What does your /etc/exports file look like?
> What does 'exportfs -v' show? (if service nfs start works)
> --
> Pete Nesbitt, rhce
>
>
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list

--
Pete Nesbitt, rhce


-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

[Index of Archives]     [CentOS]     [Kernel Development]     [PAM]     [Fedora Users]     [Red Hat Development]     [Big List of Linux Books]     [Linux Admin]     [Gimp]     [Asterisk PBX]     [Yosemite News]     [Red Hat Crash Utility]


  Powered by Linux