"Ubuntu" Task Manager Loadruner

　　

Linux
1 Preparatory work
There are two ways to verify that the RSTATD daemon is configured on the server:
① uses RUP commands, which are used to report various statistical information about a computer, including configuration information for RSTATD. Using the command Rup 10.130.61.203, here 10.130.61.203 is the IP of the Linux/unix server to monitor if the command returns relevant statistics. Indicates that the RSTATD daemon has been configured and activated, that if no meaningful statistics are returned, or an error report appears, the RSTATD daemon has not been configured or has a problem.
② using the Find command
#find/-name rpc.rstatd, which is used to find out if a rpc.rstatd file exists in the system, and if not, the RSTATD daemon is not installed.
If the RSTATD program is not installed on the server (generally Linux is not installed), you need to download a package to have this service, the package name is rpc.rstatd-4.0.1.tar.gz. This is a source code, need to compile, download and install RSTATD (can be downloaded at http://sourceforge.net/projects/rstatd this address)
After downloading, start the installation, the installation steps are as follows:
TAR-XZVF rpc.rstatd-4.0.1.tar.gz
CD RPC.RSTATD-4.0.1/
./configure-Configuration Actions
make-to compile
Make install-start Installation
Rpc.rstatd-starting the RSTATD process

2) After the installation is complete, configure the rstatd target daemon xinetd, its main configuration file is/etc/xinetd.conf, it contains some of the following basic information:
#
# xinetd.conf
#
# Copyright (c) 1998-2001 SuSE GmbH Nuernberg, Germany.
# Copyright (c) 2002 SuSE Linux AG, Nuernberg, Germany.
#
Defaults
{
Log_type = File/var/log/xinetd.log
log_on_success = HOST EXIT DURATION
Log_on_failure = HOST attempt
# only_from = localhost
instances = 30
CPS = 50 10
#
# The specification of an interface is interesting, if we be on a firewall.
# For example, if you are want to provide services from an internal
# network interface, may specify your internal interfaces ip-address.
#
# interface = 127.0.0.1
}
Includedir/etc/xinetd.d

We need to modify the/etc/xinetd.d/under the three conf file Rlogin, rsh,rexec the three configuration files, three files in the Disable = yes changed to disable = no (disabled used in the default {} prohibited Service) or the # Default:off is set to on this means that the default is to start the above three services at xinetd startup!
Description: When I configure myself, without disable = yes, I will change # Default:off to: Default:on, after reboot (cd/etc/init.d/./xinetd restart) via Netstat-an |grep 514 views, no return. Then I manually add the last line in the three files disable = no, then restart xinetd, then use Netstat-an |grep 514 view, get TCP 0 0 0.0.0.0:514 0.0.0.0:* Listen results, Indicates that the RSH server has been started.

Just make sure there are rstatd and xinetd in the process on the Linux machine, and the two services can be monitored with LR.
Two Little tricks:
① Check whether the startup: Rsh listens on TCP is 514.
[Email protected] root]# Netstat-an |grep 514
TCP 0 0 0.0.0.0:514 0.0.0.0:* LISTEN
If you can see 514 in the Listener instructions The RSH server has been started.
② Check if start: rstatd
Input command: rpcinfo-p
If you can see a message similar to the following:
Program Version Protocol port
100001 5 UDP 937 RSTATD
100001 4 UDP 937 RSTATD
100001 3 UDP 937 RSTATD
100001 2 UDP 937 RSTATD
100001 1 UDP 937 RSTATD
That means the RSTATD service is up and (of course, it can be replaced with PS Ax)
③ re-xinetd method:
On SuSE Linux, do the following:
cd/etc/init.d/
./xinetd Restart
See some places on the Internet that use the following command:
# Service XINETD Reload
#/sbin/service xinetd Rstart
I don't know what the system is for.
④ installation of rsh, and rsh-server two service pack methods
A. Uninstalling Rsh
# rpm–q rsh----------View version number
# RPM-E Version number---------Uninstall this version.
b Installation
# RPM–IVH rsh-0.17-14.i386.rpm rsh-server-0.17-14.i386.rpm
⑤ When starting RPC.RSTATD, will error "Cannot register service:RPC:Unable to receive; errno = Ction refused ".
Here's how to fix it:
#/ETC/INIT.D./portmap start
#/ETC/INIT.D./nfs start

sudo apt-get install Portmap
Then start the rpc.rstatd again. Server

Finally, in the controller, drag and drop the UNIX resources into the right window, right-click the mouse to select Add measurements, add the IP address of the monitored Linux, and then select the metrics to be monitored.

"Ubuntu" Task Manager Loadruner