Sponsored Content
Top Forums UNIX for Advanced & Expert Users NFS server <servername> not responding still trying Post 302525286 by Create on Thursday 26th of May 2011 09:32:21 AM
Old 05-26-2011
Are the mounts that are failing on the same network/subnet? You may find that you are having some issues with the network and not really the client. Have you tried mounting these via TCP instead of UDP? If the TCP stops the alerts, I would take a look at the network.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

NFS SERVER.....not responding

Hi i am using HPUX11.00 and i am facing a starnge problem after some time when i log on a message is coimng NFS server not responding still trying....and it keps on coming there is no other way but to log out..form the server and start once again... there is no file system exported or NFS... (3 Replies)
Discussion started by: Prafulla
3 Replies

2. UNIX for Dummies Questions & Answers

Solaris 9 server not responding

I'm in panic mode. This isn't a production server, however, is very vital to office. Sun V240 with Solaris 9, stopped accepting ftp sessions. When I tried to remote into box, it didn't respond. I have tried rebooting to boot in single user mode, no luck. I can see that it is ON but I can't get it... (3 Replies)
Discussion started by: mkeis1144
3 Replies

3. Solaris

Locate NFS "not responding still trying" application on client

At times I have unknown applications that hang for long periods of time over and over again after a network glitch. These are sometimes nfs4 but usually nfs3 clients and are always solaris10 systems. nfs: NFS server hostname not responding still trying nfs: NFS server hostname ok nfs: NFS... (1 Reply)
Discussion started by: HPAVC
1 Replies

4. Solaris

Solaris 9 as a nfs client -- centos as a nfs server.

Hello, I have a centos as nfs server, its name is centos_A. After I finish the setup of the nfs server, the other linux can access this nfs server immediately via /net/centos_A/* But, My solaris 9 can not access /net/centos_A/* immediately. I have to leave /net/centos_A, and wait for about... (1 Reply)
Discussion started by: bruceharbin
1 Replies

5. Red Hat

After umount -lf: kernel: nfs: server HOSTNAME not responding, timed out

Greetings! I'm testing a failover solution for NFSv4 on RHEL6 with latest updates. My script umounts (umount -lf /share) the faulty NFS share if it sees that's hanging on the client (the NFS daemon is down on the NFS server) and it mounts the share from another healthy NFS server. Sometimes... (4 Replies)
Discussion started by: Arsene Lupen
4 Replies

6. Red Hat

RHEL5 Server not responding

I have RHEL5 server Sometimes ping timeout occured and i can not access server from any tool or ILOM Any ideas how to solve this? (5 Replies)
Discussion started by: rafat_nasar2010
5 Replies

7. UNIX for Dummies Questions & Answers

Server with OpenVZ virtualisation is not responding but VMs are OK

Server is accessible only via IPMI. SSH and web control panel is timeout. Takes several hours. Server dont have high load or suspicious processes. I checked /etc/hosts.deny and restarted ssh, but nothing :( (0 Replies)
Discussion started by: postcd
0 Replies

8. AIX

AIX NFS Server and NFS Client

Hi 2 ALL, try to run NFS Server in AIX 7.1 : 1. Step by step on NFS Server node mkdir /tmp/test chgrp staff /tmp/test chmod 775 /tmp/test-- create export directory (fs) mknfsexp -d /tmp/test -t ro exportfs -va show mount -e :/# exportfs -av exports: 1831-187 re-exported /tmp/test... (4 Replies)
Discussion started by: penchev
4 Replies

9. UNIX for Beginners Questions & Answers

NFS server xxxxx not responding still trying

Hello, I got the below error on my AIX system when doing a df command NFS server xxx not responding still trying We check and know that the NFS server is not available anymore. So we would like to unmount it, but no help. / > umount /mountpoint/ umount: Could not find anything to... (4 Replies)
Discussion started by: Phat
4 Replies
nfsd(1M)																  nfsd(1M)

NAME
nfsd - NFS daemon SYNOPSIS
#_conn] listen_backlog] protocol] device] [nservers] DESCRIPTION
is the daemon that handles client file system requests. Only users with sufficient privileges can run this daemon. The daemon is automatically invoked if and in the file. By default, starts over the TCP and UDP transports for version 2 and version 3, and over TCP for version 4, if NFS version 4 is enabled. One can change this with the option. A previously invoked daemon started with or without options must be stopped before invoking another command. Administrators wanting to change startup parameters for should make changes (as root user) to the NFS default file (see nfs(4)). Adminis- trators can either edit this file or use the command to make changes. Options The following options are supported: Start a NFS daemon over all available connectionless and connection-oriented transports, including UDP and TCP. Equivalent to set- ting the parameter to in the NFS default file. This sets the maximum number of connections allowed to the NFS server over connection-oriented transports. By default, the number of connections is unlimited. Equivalent to the parameter in the NFS default file. Set connection queue length for the NFS TCP over a connection-oriented transport. The default value is 32 entries. Equivalent to the parameter in the NFS default file. Start a NFS daemon over the specified protocol. Equivalent to the parameter in the NFS default file. Start a NFS daemon for the transport specified by the given device. Equivalent to the parameter in the NFS default file. Operands The following operands are supported: This sets the maximum number of concurrent NFS requests that the server can handle. This concurrency is achieved by up to nservers threads created as needed in the kernel. nservers should be based on the load expected on this server. 16 is the usual number of nservers. If nservers is not specified, the maximum number of concurrent NFS requests will default to 1. Changing the value of nservers requires stopping and restarting Equivalent to the parameter in the NFS default file. Notes A directory service that provides service name data base support must have the following service entries in its database: If the kernel tunable (see nfs_portmon(5)) is set to 1, then clients are required to use privileged ports (ports < IPPORT_RESERVED) to receive NFS services. This tunable is set to 0 by default. Use (see kctune(1M)) to set this tunable. By default, the NFS version 4 server is disabled. In order to enable it you must stop the NFS server. As root, either use the command (see setoncenv(1M)) or edit to set the parameter to 4. EXIT STATUS
Daemon started successfully. Daemon failed to start. WARNINGS
Manually starting and restarting is not recommended. If it is necessary to do so, use the NFS server start/stop script FILES
client machine pointer to an open-but-unlinked file. shell script for starting startup parameters for directories used by the server to manage client state information; these directories should not be removed. AUTHOR
was developed by Sun Microsystems, Inc. SEE ALSO
kctune(1M), mountd(1M), setoncenv(1M), getservent(3N), nfs(4), nsswitch.conf(4), services(4), sharetab(4), nfs_portmon(5). nfsd(1M)
All times are GMT -4. The time now is 05:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy