statd(8c)statd(8c)Name
statd - network status monitor daemon
Syntax
/usr/etc/statd
Description
The daemon monitors the status of the client and server sites in response to a request made by the local daemon. When a site failure is
detected, notifies the local daemon, which then processes the recovery of the locked files or file regions.
Restrictions
The crash of a site is only detected on its recovery.
FilesSee Alsostatmon(5), lockd(8c)statd(8c)
Check Out this Related Man Page
rpc.statd(8) System Manager's Manual rpc.statd(8)NAME
rpc.statd, statd - Network status monitor daemon
SYNOPSIS
/usr/sbin/rpc.statd [-c]
OPTIONS
Available only on TruCluster Server systems. This option starts the clusterwide network status daemon, which helps provide highly available
NFS service. Do not use -c directly. Highly available NFS service is configured by default and typically does not require intervention. If
you do need to start the clusterwide network status daemon, use the CAA command, caa_start cluster_lockd.
For more information, see the TruCluster Server Administration manual.
DESCRIPTION
The rpc.statd daemon monitors the status of the client and server sites in response to a request made by the local rpc.lockd daemon. When
a site failure is detected, the rpc.statd daemon notifies the local rpc.lockd daemon, which then processes the recovery of the locked files
or file regions.
RESTRICTIONS
The crash of a site is only detected on its recovery.
FILES
A directory created by the statd daemon. Each file name in the directory is the host name of a client or server that the statd daemon will
notify upon its recovery. A backup directory created by the statd daemon. A file created by the statd daemon to store its state number.
SEE ALSO
Daemons: rpc.lockd(8)
Files: statmon(4)rpc.statd(8)
We are trying to implement a NAS solution with UNIX servers and multiple networks, and I've heard that NFS has security issues with lockd and statd.
The security issue as it was explained to me is that these services are subject to vulnerabilities/exploits, and that users who connect to Unix... (1 Reply)
I am trying to set up a SunOS 4.1.3 system on our local ethernet. This system had been previously installed on another network. When I boot the system, I get an error saying "rpc.statd cannot talk to statd on". I configured the IP address according to our network scheme (192.9.200.x) and rewrote... (2 Replies)
Hi,
I'm working with Mercury tools: Loadrunner, and I'm trying to monitor a unix server by rstatd, and I got next error:
Mar 4 11:25:56 sacindt rpc.rstatd: incompatible to /proc. Could not read disk_io: data
does any one have an idea about this..
regards (0 Replies)
Hi,
I'm working with Mercury tools: Loadrunner, and I'm trying to monitor a unix/linux box, the Loadrunner tool uses the rstatd, and I got next error:
Mar 4 11:25:56 sacindt rpc.rstatd: incompatible to /proc. Could not read disk_io: data
I'm trying to start that deamon, and I use the RUP to... (1 Reply)
Hi, I am new in AIX. Here is a problem I have now:
I've got an error in console saying: "statd -a can't get ip configuration: A file or directory in the path name does not exist."
How can I troubleshoot the issue? Where should a get start from?
Thank you in advance!
---------- Post... (1 Reply)
guy's
How to start rstatd Daemon on AIX 6.1
as I enable it from etc/inetd.conf
then I refreshed it by this command refresh -s inetd but stil is not Active !
can some one advice in this ! (7 Replies)
Hi there,
I'm trying to use loadrunner with freebsd system monitoring tools like rstatd/rup/rsysinfo, but I keep getting this error from loadrunner:
Monitor name :UNIX Resources. Internal rpc error (error code:4). Machine: 192.168.1.15. Hint: Check that RPC on this machine is up and running.... (0 Replies)
Hi
I am currently testing SCOM2012 on my AIX systems for monitoring. I tested it on 3 systems and immediately i got the following errors:
Alert: Network Status Monitor daemon (rpcstat) is not running
Source: AIX 7.1
Path: (left blank)
Last modified by: (left blank)
Last modified time:... (3 Replies)