Shulou(Shulou.com)06/03 Report--

Install the rstatd daemon on the server

Installation steps:

1. Download rstatd from the Internet

two。 Put the file in the / home/user directory

3. Chmod 777 rpc.rstatd---- changes the read and write permissions of the file and has all permissions.

4. Chmod 777 configure-ditto

5. / configure-configuration

6. Make-compilation

7. Make install-installation

8. Rpc.rstatd-start the rstatd process

Second, configure in lr

Add measurement from LR, fill in the IP of the linux machine, and all unix/linux counters appear, including cpu's, mem's, and disk,network 's. Introduce several commonly used ones:

Average load: average load in the past 1 minute

Cpu utilization: usage of cpu

Disk traffic: disk transfer rate

Paging rate: the number of memory pages read from disk to physical memory or written from physical memory to pagefile per second

Swap-in rate: the number of processes swapped to memory per second

Swap-out rate: processes swapped out of memory per second

Add some common problems and solutions:

1. A prompt for "denied permissions" appears during the execution of the configuration or installation command

Answer: it is caused by the permission of the file. The "777" permission of all files should be given to the current user, that is, full control.

2. After installation, no information can be seen from LoadRunner, but there is no error report.

A: it is possible that the returned information value is relatively small, so you can hardly see it in the figure. For example, if the program is not running, the utilization rate of CPU is close to 0, so you cannot see the change in the monitor view. It is also possible that the sampling frequency is too large, which can be set in the chart to get the information every second, so that the interface will be refreshed in time.

3. After monitoring for a period of time, the LoadRunner indicates that there is an error and cannot continue to monitor the information.

A: it may be that the CPU is in a high load state for a long time, which causes the system to shut down the service automatically. You can re-add the counter in LoadRunner and set the sampling time a little longer to avoid this situation.

4. In the past, monitoring with LoadRunner was successful, but no information was found again.

A: it is possible that the rstatd daemon was not opened due to a system reboot. You can reopen it manually, using the command "rpc.rstatd", and you can use the "rpcinfo-p" command to see if the current system has started the rstatd daemon.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.