nfsmnthelp 1831-019

Hi Folks,

What's wrong here?

NFS mount fails as shown.
Hosts can dig each other and dig -x each other's IPs.
They are in each other's hosts files.

Other tests shown...

Many thanks,


EDIT:  Great, lost entire code section during post. Redoing...
host1:/ >mount host2:/usr/feeders /usr/feeders
nfsmnthelp: 1831-019 host2: System call error number -1.

mount: 1831-008 giving up on:
host2:/usr/feeders
System call error number -1.

host1:/ >ping host2
PING host2.blah.blah.com: (host2IP): 56 data bytes
64 bytes from host2IP: icmp_seq=0 ttl=255 time=0 ms
----host2.blah.blah.com PING Statistics----
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0/0/0 ms

host1:/ >showmount -e host2IP
export list for host2IP:
/usr/feeders (everyone)

host1:/ >lssrc -g nfs
Subsystem         Group            PID          Status
 biod             nfs              4255778      active
 nfsd             nfs              1069248      active
 rpc.mountd       nfs              4276336      active
 rpc.statd        nfs              794654       active
 rpc.lockd        nfs              561214       active
 nfsrgyd          nfs                           inoperative
 gssd             nfs                           inoperative

host1:/ >rpcinfo -p host2IP
   program vers proto   port  service
    100000    4   udp    111  portmapper
    100000    3   udp    111  portmapper
    100000    2   udp    111  portmapper
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    2   tcp    111  portmapper
    200006    4   udp   2049
    200006    4   tcp   2049
    100068    2   udp  32846  cmsd
    100068    3   udp  32846  cmsd
    100068    4   udp  32846  cmsd
    100068    5   udp  32846  cmsd
    100083    1   tcp  32777  ttdbserverd
1342177279    4   tcp  39897
1342177279    1   tcp  39897
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    200006    1   udp   2049
    200006    1   tcp   2049
    100005    1   tcp  47190  mountd
    100005    2   tcp  47190  mountd
    100005    3   tcp  47190  mountd
    100005    1   udp  39731  mountd
    100005    2   udp  39731  mountd
    100005    3   udp  39731  mountd
    400005    1   udp  39732
    100024    1   tcp  47191  status
    100024    1   udp  39733  status
    100133    1   tcp  47191
    100133    1   udp  39733
    200001    1   tcp  47191
    200001    1   udp  39733
    200001    2   tcp  47191
    200001    2   udp  39733
    100021    1   udp  39759  nlockmgr
    100021    2   udp  39759  nlockmgr
    100021    3   udp  39759  nlockmgr
    100021    4   udp  39759  nlockmgr
    100021    1   tcp  47211  nlockmgr
    100021    2   tcp  47211  nlockmgr
    100021    3   tcp  47211  nlockmgr
    100021    4   tcp  47211  nlockmgr

host1:/ >rlogin host2
*******************************************************************************
*                                                                             *
*                                                                             *
*  Welcome to AIX Version 5.3!                                                *
*                                                                             *
*                                                                             *
*  Please see the README file in /usr/lpp/bos for information pertinent to    *
*  this release of the AIX Operating System.                                  *
*                                                                             *
*                                                                             *
*******************************************************************************
...
host2:/ # lssrc -g nfs
Subsystem         Group            PID          Status
 biod             nfs              942184       active
 nfsd             nfs              544778       active
 rpc.mountd       nfs              1159398      active
 rpc.statd        nfs              659486       active
 rpc.lockd        nfs              1572982      active
 nfsrgyd          nfs                           inoperative
 gssd             nfs                           inoperative

host2:/ # ls -l /usr | grep feeders
drwxrwxrwx   18 root     system         4096 05 Mar 12:47 feeders

host2:/ # grep host1 /etc/hosts
host1IP     host1.blah.blah.com host1

host2:/ # share
/usr/feeders -vers=2:3:4,sec=sys:krb5p:krb5i:krb5:dh,rw

host2:/ >ping host1
PING host1.blah.blah.com: (host2IP): 56 data bytes
64 bytes from host2IP: icmp_seq=0 ttl=255 time=0 ms
----host2.blah.blah.com PING Statistics----
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0/0/0 ms

host2:/ # exit

host1:/ >mount host2:/usr/feeders /usr/feeders
nfsmnthelp: 1831-019 host2: System call error number -1.

mount: 1831-008 giving up on:
host2:/usr/feeders
System call error number -1.

Open in new window

unixanalystAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

woolmilkporcCommented:
Hi,
try restarting the nfs services on host2 and  re-export.
stopsrc -g nfs
startsrc -g nfs
exportfs -a
Then retry from host1.
wmp
0
unixanalystAuthor Commented:
Thanks for the suggestion but I'm getting the same result I'm afraid.
0
woolmilkporcCommented:
What if you try mounting by IP address instead of hostname?
0
Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

unixanalystAuthor Commented:
I did try that, identical result.
0
unixanalystAuthor Commented:
Just tried mounting the exported directory from a different box, no good.
Then tried mounting a test directory, exported from host2 to host1, no good.
Then tried mounting a test directory, exported from host1 to host2, that worked.

So it looks like there's an issue with the way host2 is exporting or responding to requests to mount.
0
carlmdCommented:
Take a look at the following, especially the second part.

http://www.redbooks.ibm.com/abstracts/TIPS0403.html?Open

Although this is old, and refers to a particular IBM NAS, it might also be your problem.
0
woolmilkporcCommented:
Hi,
This doesn't seem to be a name resolution problem or anything related, although one can never be sure.
I assume we will have to clean up host2 in regard to NFS.
What you could do -
1) stopsrc -g nfs (as you did above)
2) stopsrc -s  portmap (attention - this will probably interrupt more operations than just NFS)
3) rm /etc/rmtab /etc/xtab  (and maybe rm /etc/sm  /etc/sm.bak /etc/state - but these files are most probably not present)
4) startsrc -s portmap
5) startsrc -g nfs
6) exportfs -a
7) refresh -s inetd
Your system should now be as clean as can be regarding portmapper and NFS.
If still no luck, you should indeed re-examine all your /etc/hosts or maybe DNS settings concerning host2.
Or is there a misconfigured firewall inbetween, allowing the relevant traffic in one direction only?
Another question, yet a bit late - Did it ever work?
wmp

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
unixanalystAuthor Commented:
Trying to get permission to risk interrupting the service to try the above. Thanks for the suggestions.

Have also been running a tcpdump and found the following:

-Network File System, Null Reply
           NFS V3 NULL Reply

I'm guessing this is my problem.
0
carlmdCommented:
With later versions of AIX the NFS software allows for V1, V2, V3 versions of the exported directory where each has different configurations. Take a look at the attributes of the exported directory and make sure that the "hosts allowed access" is filled in correctly, and the security methods match.

Did this ever work? If so, what has changed?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Server Software

From novice to tech pro — start learning today.