Joseph, On suse: driscoll>ps -ef | grep nfs root 11110 1 0 May18 ? 00:00:00 [nfsd] root 11111 1 0 May18 ? 00:00:00 [nfsd] root 11112 1 0 May18 ? 00:00:00 [nfsd] root 11113 1 0 May18 ? 00:00:00 [nfsd] driscoll 27487 27300 0 08:59 pts/497 00:00:00 grep nfs on hp: showmount -e suse showmount: suse: RPC: Rpcbind failure - RPC: Timed out suse exports file: driscoll>cat /etc/exports #/home/driscoll/Mail *(ro,no_root_squash,sync,no_auth_nlm,insecure_locks) /home/driscoll/Mail *(ro) All my hp boxes are both nfs servers and clients to each other without problems. They and suse are also nfs clients to a folder served via nfs on a windows server. And suse is a nfs client to directories severd by two differnt hp boxes. It is only getting suse to serve nfs to hp boxes that is not working. The commented out line on my /etc/exports is various settings I have tried. The second line is the simplest possible setting for test. Thus far nothing has worked. I suspect that this is a problem specific to the interaction between susenfs and hpuxnfs. I am trying to find either a magic word for this situation or some low-level debugging techniques that will let me track things step-by-step. Thanks, Dave On Wed, May 18, 2005 at 06:50:38PM -0700, Joseph Loo wrote:
Try it from your client. This will help to determine if the nfs mounts are being made available outside the machine. This will help you determine if there is something blocking it.
I need to explain my self a bit better what I am trying to do.
Assume that your client machine (not serer) is hpux and your serveris suse. On the client machine you execute the command showmount -e suse or your hupux variant. This will try to communicate with your nfs server and get back the exported files. If you do not get a replay, either the nfs server is not running or your firewall is blocking it.
To determine if your nfs server is gunning, run ps -ef | grep nfs If you are running the kernel nfs version, you should be receiving a whole bunch of nfsd processes running. If you are running the user base version, then it might return rpc.nfs or something like that.
If you do not get any of the above, then execute /etc/init.d/nfsserver start This should start your nfs server properly. Then try the showmount -e suse It should show up properly. If it does not try the ps command from the previous version
It now looks like either the firewall is blockig you or you need to change the /etc/exports configuration. I personally set my configuration up to be very machine specific.
loo@crab:~> more /etc/exports /export/home0 sirus(rw,sync) polaris(rw,sync)
Try it with a host or two.
Then it starts looking like your firewall is blocking you. I make my internal network completely open using YATS. Thus eth0 for me is internal and everything is open.
You need to start checking your firewall. When you use YAST you might want to try and see if you checked off the firewall configuration. That was causing me a whole bunch of problems before.
Dave Driscoll wrote:
To clarify: I have 3 machines. The others are both nfs servers and clients.The suse machine is currently an nfs client and I want it to be a server too. Showmout -e gives: suse:/home/driscoll # showmount -e Export list for suse: /home/driscoll/Mail * my /etc/exports: /home/driscoll/Mail *(ro,no_root_squash,sync,insecure_locks) But when I try to mount this directory from another machine running hpux, it reports an rpcbind failure and time out. I suspect the problem is something specific to the interaction between suse and hpux. The insecure_locks is from something I found while googling that said hpux needed it although it did not seem to help. I have already tried the obvious (I did RTFM). I am looking for some tips on debugging nfs when it doesn't work or maybe someone who has gotten hpux and suse to play nice together can tell me the magic word.
Thanks, Dave On Tue, May 17, 2005 at 05:58:33PM -0700, Joseph Loo wrote:
You might want to try two things: do a showmount -e yourserver both on your client and your server machine. This will tell you if the nfserver is even up and running. Did you make sure that the nfsserver is running. It seems SUSE does not enable the server explicitly (good thing). You need to make sure it is up and running.
I am not sure about 9.1 have you tried "/etc/init.d/nfsserver start"
mike wrote:
On Tuesday 17 May 2005 18:32, Dave Driscoll wrote:
Hi,
Trying to get nfs server working. Nfs client works but when I try to export a directory to the machine that serves nfs mounts to the suse machine it times out without connecting. I have opened up permissions (chmod 777) on the directory I want to export. I've tried to mount with both Yast and command line.
I'm not sure if I understand this. Are you trying to get a directory
from the server, or send one to it? I know it sounds funny, but that's
what I read. If that's the case, you don't export directories from a client. You export from the server.
I've tried variaous entries in /etc/exports. portmap and rpc.mountd are both running. rpc.nfsd does not seem to run as a daemon. I have tried rcnfsserver restart and running it directly from the command line and it appears to exit immediately with no error messages. Does anyone know the magic word or have some suggestions for how to trouble-shoot this?
in order, if you change the exports file, restart portmap, then rcnfsserver. That's the way I've always done it.
Mike
-- Joseph Loo jloo@acm.org
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Joseph Loo jloo@acm.org
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com