Page 1 of 2 12 LastLast
Results 1 to 10 of 18

Thread: SLES 9,1 NFS issue

  1. #1

    Angry SLES 9,1 NFS issue

    Hello everyone,

    First let me preface by saying, I know this is very old, and if I did not need the server to continue, I would scrap it and install a fresh new OS. However, that being the case, I am stuck with it for now.

    I have everyone working like I would expect, except NFS. For some reason when I use the mount -t nfs server:/share/123 /mnt/share it gives me an error:

    mount server reported tcp not available, falling back to udp
    mount: RPC: Program not registered

    I have other linux servers that can access it just fine. Here is the weird part...it was working before. We needed to reboot the server, and when we did, it just stopped working. /etc/fstab has not changed, but for some reason it will not mount the NFS share any longer.

    Things I have tried:

    stoping/restarting/rebooting portmap, nfs, nfsboot, nfslock
    Messing about with the firewall - currently shut off
    creating new local folders to try and mount it there
    checked and rechecked /etc/exports on the nfs server
    tried mounting via IP rather than name
    checked /etc/hosts.allow /hosts.deny
    Verified that the NFS server is hosting NFS 4,3,2

    I am able to ping by name and IP. I can SSH and SCP.

    Is there something I am missing? Normally setting up NFS is super fast and easy...

    Appreciate any help you can give.

    All the best,

    kreb

  2. Re: SLES 9,1 NFS issue

    Quote Originally Posted by krebstar3 View Post
    Hello everyone,

    First let me preface by saying, I know this is very old, and if I did not need the server to continue, I would scrap it and install a fresh new OS. However, that being the case, I am stuck with it for now.

    I have everyone working like I would expect, except NFS. For some reason when I use the mount -t nfs server:/share/123 /mnt/share it gives me an error:

    mount server reported tcp not available, falling back to udp
    mount: RPC: Program not registered

    I have other linux servers that can access it just fine. Here is the weird part...it was working before. We needed to reboot the server, and when we did, it just stopped working. /etc/fstab has not changed, but for some reason it will not mount the NFS share any longer.

    Things I have tried:

    stoping/restarting/rebooting portmap, nfs, nfsboot, nfslock
    Messing about with the firewall - currently shut off
    creating new local folders to try and mount it there
    checked and rechecked /etc/exports on the nfs server
    tried mounting via IP rather than name
    checked /etc/hosts.allow /hosts.deny
    Verified that the NFS server is hosting NFS 4,3,2

    I am able to ping by name and IP. I can SSH and SCP.

    Is there something I am missing? Normally setting up NFS is super fast and easy...

    Appreciate any help you can give.

    All the best,

    kreb
    Hi and welcome to the Forum
    Sure it's not a routing problem, gateway changed etc?
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  3. Re: SLES 9,1 NFS issue

    Hi kreb,

    please give it a try with "mount -t nfs -o proto=udp,mountproto=udp server:/share/123 /mnt/share" and / or specifying "vers=3" if that fails, just for checks.

    My guess is that an update of the tirpc package on the client machine might have changed things, but that's just a "pain in the bones, might be that rain's coming up" type of feeling

    Regards,
    J
    From the times when today's "old school" was "new school"

    If you find this post helpful and are logged into the web interface, show your appreciation and click on the star below...

  4. #4

    Question Re: SLES 9,1 NFS issue

    Thanks for the tips.

    @MalcomLewis

    I am not entirely certain it is a routing problem, however they are not routing as they are on the same network and plugged into the same switch.

    @JMozden

    Those options don't work either:

    # mount -t nfs -o proto=udp,vers=3 server:/share /mnt/share
    mount server reported tcp not available, falling back to udp
    mount: RPC: Program not registered


    Any other ideas?

  5. Re: SLES 9,1 NFS issue

    Had you tested "mountproto=udp" as well?

    What does "rpcinfo -p <server>" (<server> as specified in your mount command) return? "RPC program not registered" is meant to mean that the (NFS) client requested a specific "program, version, protocol" info from the portmapper running on the server (see the output from rpcinfo for a list of all currently registered prog/vers/proto combos) and received a reply from the server's portmapper service, that no according program was registered.

    Regards,
    J
    From the times when today's "old school" was "new school"

    If you find this post helpful and are logged into the web interface, show your appreciation and click on the star below...

  6. #6

    Re: SLES 9,1 NFS issue

    @jmozden

    Thank you for the reply! I just found some pertinent information!

    I just noticed this:

    On server 1 (the server I am trying to connect to) I get this:

    # rpcinfo -p server1
    program vers proto port
    100000 4 tcp 111 portmapper
    100000 3 tcp 111 portmapper
    100000 2 tcp 111 portmapper
    100000 4 udp 111 portmapper
    100000 3 udp 111 portmapper
    100000 2 udp 111 portmapper
    100024 1 udp 46075 status
    100024 1 tcp 50007 status


    On another server that we have, I get this (Mapping works fine)

    # rpcinfo -p server2
    program vers proto port
    100000 2 tcp 111 portmapper
    100000 2 udp 111 portmapper
    100024 1 udp 838 status
    100024 1 tcp 841 status
    100011 1 udp 773 rquotad
    100011 2 udp 773 rquotad
    100011 1 tcp 776 rquotad
    100011 2 tcp 776 rquotad
    100003 2 udp 2049 nfs
    100003 3 udp 2049 nfs
    100003 4 udp 2049 nfs
    100003 2 tcp 2049 nfs
    100003 3 tcp 2049 nfs
    100003 4 tcp 2049 nfs
    100021 1 udp 32768 nlockmgr
    100021 3 udp 32768 nlockmgr
    100021 4 udp 32768 nlockmgr
    100021 1 tcp 32773 nlockmgr
    100021 3 tcp 32773 nlockmgr
    100021 4 tcp 32773 nlockmgr
    100005 1 udp 789 mountd
    100005 1 tcp 792 mountd
    100005 2 udp 789 mountd
    100005 2 tcp 792 mountd
    100005 3 udp 789 mountd
    100005 3 tcp 792 mountd


    I am not seeing nfs on server1 for some reason. However, if I jump on another linux box, and point it at server1 they showup just fine

    #rpcinfo -p server1
    program vers proto port service
    100000 4 tcp 111 portmapper
    100000 3 tcp 111 portmapper
    100000 2 tcp 111 portmapper
    100000 4 udp 111 portmapper
    100000 3 udp 111 portmapper
    100000 2 udp 111 portmapper
    100024 1 udp 662 status
    100024 1 tcp 662 status
    100011 1 udp 875 rquotad
    100011 2 udp 875 rquotad
    100011 1 tcp 875 rquotad
    100011 2 tcp 875 rquotad
    100005 1 udp 892 mountd
    100005 1 tcp 892 mountd
    100005 2 udp 892 mountd
    100005 2 tcp 892 mountd
    100005 3 udp 892 mountd
    100005 3 tcp 892 mountd
    100003 2 tcp 2049 nfs
    100003 3 tcp 2049 nfs
    100003 4 tcp 2049 nfs
    100227 2 tcp 2049 nfs_acl
    100227 3 tcp 2049 nfs_acl
    100003 2 udp 2049 nfs
    100003 3 udp 2049 nfs
    100003 4 udp 2049 nfs
    100227 2 udp 2049 nfs_acl
    100227 3 udp 2049 nfs_acl
    100021 1 udp 32769 nlockmgr
    100021 3 udp 32769 nlockmgr
    100021 4 udp 32769 nlockmgr
    100021 1 tcp 32803 nlockmgr
    100021 3 tcp 32803 nlockmgr
    100021 4 tcp 32803 nlockmgr

    I checked and the firewall is turned off, what am I doing wrong?

  7. Re: SLES 9,1 NFS issue

    Hm, sounds strange indeed. My first guess would have been a name resolution issue - but you mentioned that you had tried mounts via IP already.

    I remember having had difficulties between an old portmapper and a new libtirpc client... iirc it had to do with trying tcp instead of udp (hence my first suggestions). But that's years back. Could you please also try with "-o udp" (as an alternative to "-o proto=udp"), just for completeness' sake?

    You'll find someone with the same symptoms here http://misc.openbsd.narkive.com/AsKK...not-registered, and that's from 2002... but then, the thread opener resorted to upgrading

    Regards,
    J
    From the times when today's "old school" was "new school"

    If you find this post helpful and are logged into the web interface, show your appreciation and click on the star below...

  8. #8

    Re: SLES 9,1 NFS issue

    # mount -t nfs -o udp server:/share /mnt/share
    mount server reported tcp not available, falling back to udp
    mount: RPC: Program not registered

    I am just not certain if this is a RedHat issue (NFS server) or a SUSE (Client). Other RedHat servers can use the rpcinfo command and see NFS.

  9. Re: SLES 9,1 NFS issue

    > I am just not certain if this is a RedHat issue (NFS server) or a SUSE (Client). Other RedHat servers can use the rpcinfo command and see NFS.

    I wouldn't point at any of the two - it's more that they're probably years apart (assuming that the NFS server is an up-to-date machine), implementation-wise - SLES 9 SP1 is ancient and some "interesting" changes took place in the TIRPC stack, in the recent years.

    What I originally didn't recognize is that the *client* is the old machine, I (for whatever reason) assumed that the NFS server was old. It may well be that you'll have to open up things at the NFS server to allow for such old clients (protocol-wise) and that also explains why all those options for the mount did no good - they're to assist new clients accessing old servers

    Maybe you might ask some RH support what you'd need to do to support old clients - or try to open a service request with SUSE, if you're under support there. SUSE has an own offering to support RHES systems during migration, so they might have come across such version combinations already.

    Regards,
    J
    From the times when today's "old school" was "new school"

    If you find this post helpful and are logged into the web interface, show your appreciation and click on the star below...

  10. #10

    Re: SLES 9,1 NFS issue

    Weird, it just started working. So I snapshotted it, and left it alone. Was just planning on leaving it for now. However, it literally stopped working on its own...

    I have created a support case with RHEL to see if they can help. Also, is there a process to do an in place upgrade of SUSE 9?

    kreb

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •