Sponsored Content
Operating Systems HP-UX Tru64 How to identify what causes the server to go down? Post 302236951 by fpmurphy on Tuesday 16th of September 2008 04:41:14 PM
Old 09-16-2008
Probably due to network or NFS server problems

Do a "rpcinfo -u your-nfs-server status." If "rpcinfo" times out with "cannot contact", then on your nfs server do the following:
- kill the /usr/sbin/rpc.statd and /usr/sbin/rpc.lockd processes
- delete all files in /etc/sm.bak
- restart the two daemons
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to identify who rebooted the linux server

Hi All, Since server is located at remote place so how to identify which user rebooted the server. Is there any way to identify the user. Thanks in advance, Reg, Bache Gowda (1 Reply)
Discussion started by: bache_gowda
1 Replies

2. HP-UX

User unlock problem in Tru64 4.0F Server

Hi Friends We have two node trucluster Tru64 4.0F Alpha Servers,In one of Tru64 4.0F Unix Server I am unable to unlock users, when I issue usermod command I will get following error /usr/sbin/usermod -x administrative_lock_applied=0 username account manager has exited unexpectedly - please... (0 Replies)
Discussion started by: madanmb
0 Replies

3. AIX

How to identify which HDD is allocated to VIO server

Hello All, I am new to AIX VIO LPAR server. We have VIO 1.5 server installed with few logical valumes and 3-4 Virtual machines running. I wanted to restructer the space allocation to logical values. but don't know which harddisk, hold VIO server installation. Can someone please help to me... (8 Replies)
Discussion started by: kishorbhede
8 Replies

4. UNIX for Dummies Questions & Answers

identify a customer under a UNIX server

Like many UNIX users, there is a small team that is connected to UNIX (under the same UNIX user) via putty from a Windows PC. Is there a way, once under UNIX, to know the address of the originating computer or anything that can differentiate initial users ? (7 Replies)
Discussion started by: popescu1954
7 Replies

5. UNIX and Linux Applications

Identify server.database connection

Good afternoon i need your help, i am new at unix, in a ETL scenario like datastage is , there are a bunch of procesess (script shells) conecting to hetereogenius database source servers in order to extract information. Ive got 2 questions 1. Using unix how can i identify exactly the... (1 Reply)
Discussion started by: alexcol
1 Replies

6. Solaris

identify server type from ufsdump

Hi guys I have a little problem. I need to identify the server type from some ufsdumps. How can i do that? I grepped with: grep Sun messages* but with this command, if there server was never rebooted, i cannot recognize the server type. any other idea? thx in advance Ivan (5 Replies)
Discussion started by: beta17
5 Replies

7. UNIX for Advanced & Expert Users

How to identify the blade from VIO server?

Hello, I would like to identify the blade or/and bladecenter from the hosted VIO server. I prefer the "command line" solution. May be kdb. Like, I want to ask the child about his father. Thank you (1 Reply)
Discussion started by: x41
1 Replies
statd(1M)						  System Administration Commands						 statd(1M)

NAME
statd - network status monitor SYNOPSIS
/usr/lib/nfs/statd DESCRIPTION
statd is an intermediate version of the status monitor. It interacts with lockd(1M) to provide the crash and recovery functions for the locking services on NFS. statd keeps track of the clients with processes which hold locks on a server. When the server reboots after a crash, statd sends a message to the statd on each client indicating that the server has rebooted. The client statd processes then inform the lockd on the client that the server has rebooted. The client lockd then attempts to reclaim the lock(s) from the server. statd on the client host also informs the statd on the server(s) holding locks for the client when the client has rebooted. In this case, the statd on the server informs its lockd that all locks held by the rebooting client should be released, allowing other processes to lock those files. lockd is started by automountd(1M), mount_nfs(1M), and share(1M) if NFS automounts are needed. FILES
/var/statmon/sm lists hosts and network addresses to be contacted after a reboot /var/statmon/sm.bak lists hosts and network addresses that could not be contacted after last reboot /var/statmon/state includes a number which changes during a reboot /usr/include/rpcsvc/sm_inter.x contains the rpcgen source code for the interface services provided by the statd daemon. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWnfscu | +-----------------------------+-----------------------------+ SEE ALSO
svcs(1), automountd(1M), lockd(1M), mount_nfs(1M), share(1M), svcadm(1M), attributes(5), smf(5) System Administration Guide: IP Services NOTES
The crash of a server is only detected upon its recovery. The statd service is managed by the service management facility, smf(5), under the service identifier: svc:/network/nfs/status Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser- vice's status can be queried using the svcs(1) command. If it is disabled, it will be enabled by mount_nfs(1M), share_nfs(1M), and automountd(1M) unless its application/auto_enable prop- erty is set to false. SunOS 5.10 18 Nov 2004 statd(1M)
All times are GMT -4. The time now is 03:39 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy