We have an admin who is running Mecury LoadRunner. One part of it
load to our Solaris 10 Web and Application servers (SPARC), and the
collects performance statistics via the Solaris RPC "rstatd"
Now, randomly, and independent of the load placed on the Solaris Web/
servers (it doesn't matter), the Windows LoadRunner program that
connects to those
servers to collect performance data, via the rstatd interface, dies
following error message (I believe performance collector program is
written in Java):
Monitor name :UNIX Resources. Internal rpc error (error code:2).
Hint: Check that RPC on this machine is up and running. Check that
on this machine is up and running (use rpcinfo utility for this
Details: RPC: RPC call failed.
RPC-TCP: recv()/recvfrom() failed.
RPC-TCP: Timeout reached. (entry point: Factory::CollectData).
Now "rpcinfo -p" and "svcs -a" show that the rstatd daemon is running,
and I can
connect to it via rup/rusers/telnet to the port it is listening on
(this has been the
case along - this has not changed).
This just started happening when we moved the Solaris web/app machines
another network (but all that was changed were their IP addresses, and
else). The load generator servers themselves as well as the LoadRunner
data collector servers were not moved to other networks.
We think its network related but are not sure - it could be the
LoadRunner rstat data
collector program itself (written probably in java and running a PC)
I've done tcpdumps and looked ... and the rstat calls look totally
Anyone seen this / have advice?
||8/23/2007 11:41:15 AM