Sponsored Content
Full Discussion: Mountd problem in 5.3
Operating Systems AIX Mountd problem in 5.3 Post 302911835 by MariusM on Monday 4th of August 2014 01:47:46 AM
Old 08-04-2014
Mountd problem in 5.3

Dear all,

I'm troubleshooting some problem with NFS server, mountd to be precise. Server is running AIX 5.3. When NFS starts, mountd listens both on TCP and UDP ports:
Code:
rpcinfo -p | grep mountd
    100005    1   tcp   6666  mountd
    100005    2   tcp   6666  mountd
    100005    3   tcp   6666  mountd
    100005    1   udp   6666  mountd
    100005    2   udp   6666  mountd
    100005    3   udp   6666  mountd

Port 6666 is fixed in /etc/services. After the start server works fine, clients can mount exported directories without any issues. After some time (not sure how long, perhaps after some idle period) mountd stops listening on TCP and only UDP remains:
Code:
 rpcinfo -p | grep mountd
    100005    1   udp   6666  mountd
    100005    2   udp   6666  mountd
    100005    3   udp   6666  mountd

The problem is that clients still try to contact TCP port first, despite the fact (I can see that in network trace) that portmap says TCP program is not available. Such requests are retransmitted until they timeout and there is 2 min delay in service because of such retransmits. After timeout client tries UDP port and everything goes fine. Roughly speaking, network conversation goes like this:
Code:
Client: GETPORT Call MOUNT TCP
Server: GETPORT Reply PROGRAM_NOT_AVAILABLE
Client: GETPORT Call MOUNT UDP
Server: GETPORT Reply Port: 6666
<...some communication ongoing...>
Client: sends SYN to TCP port 6666
Client: resend SYN
Client: resend SYN
....
Timeout
Client: GETPORT Call MOUNT UDP
Server: GETPORT Reply Port: 6666
Client: MNT Call
...and everything goes ok...

Any ideas why mountd stops listening on TCP? Of course, there is another issue with clients who insist on TCP and ignores answers from portmap, but I thought I'll start with server side. In fact, I tried to read a bit about such client behaviour, too, but found nothing.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

problem with dd command or maybe AFS problem

Hi, folks. Sorry for bothering, but maybe someone could help me please. The problem is the following: there is some script that copies files from local file system to AFS. The copying is performed with dd command. The script copies data into some AFS volumes. The problem appeared with one... (0 Replies)
Discussion started by: Anta
0 Replies

2. Shell Programming and Scripting

ssh script problem problem

Hi Please help me with the following problem with my script. The following block of code is not repeating in the while loop and exiting after searching for first message. input_file ========== host001-01 host001-02 2008-07-23 13:02:04,651 ConnectionFactory - Setting session state... (2 Replies)
Discussion started by: pcjandyala
2 Replies

3. AIX

user login problem & Files listing problem.

1) when user login to the server the session got colosed. How will resolve? 2) While firing the command ls -l we are not able to see the any files in the director. but over all view the file system using the command df -g it is showing 91% used. what will be the problem? Thanks in advance. (1 Reply)
Discussion started by: pernasivam
1 Replies

4. Red Hat

Mail Problem. Maybe, it is a DNS Problem!

Hi, i've a redhat linux 9 upadated by redhat from 7 version to 9 version. A couple of days ago i was a problem with my mail, in other words i'm not able to get any email nor to send any email. I've a proxy configuration and i tried to set iptables in order to verify the port. The 110,255 and 995... (1 Reply)
Discussion started by: pintalgi
1 Replies

5. UNIX for Dummies Questions & Answers

DHCP problem and eth1 problem

At work I am trying to get this one Linux machine (let's call it ctesgm07) to behave like another Linux machine that we have (let's call it test007). test007 returns the following version info: cat /etc/debian_version: lenny/sid uname -a: Linux test007 2.6.27-7-generic #1 SMP Tue Nov 4... (0 Replies)
Discussion started by: sllinux
0 Replies

6. AIX

AIX OS problem? network problem?

Dear ALL. I installed AIX OS on customer sites. but Only one site is too slow when I connected telnet, ftp.. Ping is too fast. but telnet and FTP is not connected.. of course i check the configuration file on aix but it's normal. Do any Idea?? thanks in advance. - Jun - (3 Replies)
Discussion started by: Jeon Jun Seok
3 Replies

7. Homework & Coursework Questions

about mountd daemon ?

Manually we can stop the daemon by stopsrc command other-than this In which case mountd daemon will crash automatically. (1 Reply)
Discussion started by: t.balamurugan
1 Replies

8. IP Networking

Problem with forwarding emails (SPF problem)

Hi, This is rather a question from a "user" than from a sys admin, but I think this forum is apropriate for the question. I have an adress with automatic email forwarding and for some senders (two hietherto), emails are bouncing. This has really created a lot of problems those two time so I... (0 Replies)
Discussion started by: carwe
0 Replies

9. UNIX for Dummies Questions & Answers

sed Or Grep Problem OR Terminal Problem?

I don't know if you guys get this problem sometimes at Terminal but I had been having this problem since yesterday :( Maybe I overdid the Terminal. Even the codes that used to work doesn't work anymore. Here is what 's happening: * I wanted to remove lines containing digits so I used this... (25 Replies)
Discussion started by: Nexeu
25 Replies

10. IP Networking

Router problem or ISP problem ?

Hi everyone, I am experiencing discontinuity of Internet service, this started 1 month ago. Everything worked very well for 1 year of intensive use, but now, I have problems reaching my gateway. The gateway is not my router but a node belonging to my ISP and I share the same public IP with... (3 Replies)
Discussion started by: remic
3 Replies
rpc.mountd(8)						      System Manager's Manual						     rpc.mountd(8)

NAME
rpc.mountd - NFS mount daemon SYNOPSIS
/usr/sbin/rpc.mountd [options] DESCRIPTION
The rpc.mountd program implements the NFS mount protocol. When receiving a MOUNT request from an NFS client, it checks the request against the list of currently exported file systems. If the client is permitted to mount the file system, rpc.mountd obtains a file handle for requested directory and returns it to the client. Exporting NFS File Systems Making file systems available to NFS clients is called exporting. Usually, a file system and the hosts it should be made available to are listed in the /etc/exports file, and invoking exportfs -a whenever the system is booted. The exportfs(8) command makes export information available to both the kernel NFS server module and the rpc.mountd daemon. Alternatively, you can export individual directories temporarily using exportfs's host:/directory syntax. The rmtab File For every mount request received from an NFS client, rpc.mountd adds an entry to the /var/lib/nfs/rmtab file. When receiving an unmount request, that entry is removed. user level part of the NFS service. However, this file is mostly ornamental. One, the client can continue to use the file handle even after calling rpc.mountd 's UMOUNT proce- dure. And two, if a client reboots without notifying rpc.mountd , a stale entry will remain in rmtab. OPTIONS
-d kind or --debug kind Turn on debugging for kind. -F or --foreground Run in foreground (do not daemonize) -f or --exports-file This option specifies the exports file, listing the clients that this server is prepared to serve and parameters to apply to each such mount (see exports(5)). By default, export information is read from /etc/exports. -h or --help Display usage message. -o num or --descriptors num Set the limit of the number of open file descriptors to num. The default is 256. -N or --no-nfs-version This option can be used to request that rpc.mountd do not offer certain versions of NFS. The current version of rpc.mountd can sup- port both NFS version 2 and the newer version 3. If the NFS kernel module was compiled without support for NFSv3, rpc.mountd must be invoked with the option --no-nfs-version 3 . -n or --no-tcp Don't advertise TCP for mount. -P Ignored (compatibility with unfsd??). -p or --port num Force rpc.mountd to bind to the specified port num, instead of using the random port number assigned by the portmapper. -V or --nfs-version This option can be used to request that rpc.mountd offer certain versions of NFS. The current version of rpc.mountd can support both NFS version 2 and the newer version 3. -v or --version Print the version of rpc.mountd and exit. TCP_WRAPPERS SUPPORT This rpc.mountd version is protected by the tcp_wrapper library. You have to give the clients access to rpc.mountd if they should be allowed to use it. To allow connects from clients of the .bar.com domain you could use the following line in /etc/hosts.allow: mountd: .bar.com You have to use the daemon name mountd for the daemon name (even if the binary has a different name). For further information please have a look at the tcpd(8) and hosts_access(5) manual pages. SEE ALSO
rpc.nfsd(8), exportfs(8), exports(5), rpc.rquotad(8). FILES
/etc/exports, /var/lib/nfs/xtab. AUTHOR
Olaf Kirch, H. J. Lu, G. Allan Morris III, and a host of others. 25 Aug 2000 rpc.mountd(8)
All times are GMT -4. The time now is 01:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy