Installation LoadRunner steps and problems encountered in Linux

Under Linux, the pressure test can only be installed under Linux---load-generator, and then through the local recording script, through LoadRunner controller scenario--"load generators Log in to the Linux server for stress testing under Linux.

Installation steps can be found on the Internet:

Installation Prerequisites: ① must be the root user of Linux, ② Select the appropriate load generator--HP, Linux, Solaris Three versions based on the platform

Installation steps:

start installing the client, unzip the installation file first   [email protected] lixin]# Unzip Linux_fuzai.zip

4. Go to the Linux folder and run the Setup program installer.sh [[Email protected] lixin]# CD Linux [email protected] linux]# sh installer.sh

This time will be an error, indicating that some script file permissions are insufficient, for the sake of convenience, one time to change the permissions of all files under Linux. [email protected] linux]# CD . [email protected] lixin]# chmod 777-r linux/

You can see the permissions are all changed. 5. Go to the Linux directory again and run the installation script  

This means to formally start the installation, first of all to indicate whether you need to continue the installation, enter ' n '

Hint you want to look at the authorization file and so on, do not look, direct agree bar.

Finally let you confirm whether you need to install, exit and so on, definitely choose ' I ', continue to install.

The installation is complete, ask if you want to end directly, or look at the log, too lazy to read, the direct ' F ' ends well.

By this step, the basic installation is over. 6, add an LR load end of the customer Higkoo [email protected] linux]# useradd-g 0-s/bin/csh higkooThis time has confirmed that the Higkoo user is the default shell for CSH. In this case, the shell is just a shell of Linux, each Linux will have a default shell program, under CentOS, the default shell should be bash, but the LR uses the CSH, which is essentially no different, but in the next configuration, There will be a little difference. You can use the command to see, Higkoo this user by default is CSH. [email protected] linux]# more/etc/passwd


7, modify the configuration of the partial LR. One difference between CSH and bash is that different configurations can be loaded when different shells are loaded. The default configuration for csh under/ETC/CSH.CSHRC, Bash's default configuration is/etc/profile.    In both of these configuration files, you can load some shell environment variables. LR defaults to the configuration file for an environment variable, and the file is/opt/hp/hp_loadgenerator/env.csh. As can be seen, *.csh such a configuration file is actually the CSH configuration file format, the default file content should be:

ENV.CSH This configuration has not been introduced into the CSH default configuration, we manually modify it, let it default to add environment variables, so it is very convenient. [email protected] hp_loadgenerator]# VI/ETC/CSH.CSHRCAdd SOURCE/OPT/HP/HP_LOADGENERATOR/ENV.CSH to the last line of the file so that the configuration of LR can be imported into the CSH default configuration. 8, switch to Higkoo users, verify that the program is installed successfully.   [email protected] hp_loadgenerator]# su higkoo [[email protected] hp_loadgenerator]$ env

Verify that the program is installed and the validator is/opt/hp/hp_loadgenerator/bin/verify_generator [email protected] bin]$ Cd/opt/hp/hp_loadgenerator/bin [email protected] bin]$./verify_generatorThe prompt page appears as follows:

Ask us to set a display variable, we directly modify the Env.csh file to resolve. First switch to root user, because two reasons: 1, env.csh file to Higkoo user is read-only, cannot modify 2, Modify the ENV.CSH user, equivalent to modify the configuration of CSH, this time need to re-enter the CSH, in order to take effect so we go back to root, modify the Env.csh file. [email protected] hp_loadgenerator]# vi/opt/hp/hp_loadgenerator/env.cshAdd setenv DISPLAY 0.0 directly to the last side of the file
Switch to the Higkoo user and run the validator again. [email protected] hp_loadgenerator]# su higkoo [email protected] hp_loadgenerator]$ Cd/opt/hp/hp_loadgenerator/bin [email protected] bin]$./verify_generator  
Very smooth, all through.9, start the LR load end. [email protected] bin]$ Cd/opt/hp/hp_loadgenerator/bin [[email protected] bin]$./m_daemon_setup startUnder normal circumstances, this time should be able to start, but I installed here when the error, see.

Check the Log,log. In the/TMP path, there is an error log, after checking that it is possible to obtain a host IP based on the host name of the program has a problem, unable to obtain the IP based on the host name. 27/08/2013 00:10:25 error:communication error:failed to get the server host IP by calling the GetHostByName function

Look at the environment variables under the current shell, find the host name is Bogon, and then ping the Bogon, unable to connect. Switch to root, change the hosts configuration, and Point Bogon to 127.0.0.1.

Switch to Higkoo again, run the startup program again and start normally. [email protected] hp_loadgenerator]# su higkoo [email protected] hp_loadgenerator]$ Cd/opt/hp/hp_loadgenerator/bin [[email protected] bin]$./m_daemon_setup start M_agent_daemon (26299), [[email protected] bin]$ PS aux | grep m_agent_daemon  

At this point, the Linux load-side installation of LR is complete.

Appendix: This installation is completed under CSH, if you want to install under Bash, you can set up a env.sh file under Hp_loadgenerator, the file content is as follows, then the file is introduced to the last line of/etc/profile, and finally modified/etc/ Higkoo in passwd is configured for bash, and you can use bash to install programs. The remaining steps are the same. #/bin/bashexport product_dir=/opt/hp/hp_loadgeneratorexport m_lroot= $PRODUCT _direxport LD_LIBRARY_PATH= $M _lroot/ Bin: $M _lroot/lib:/usr/libexport display= ' 0.0 ' export path= $PATH: $M _lroot/bin ===================================== ======================== after the installation is complete, fail is displayed for validation because of a lack of dependent package compat-libstdc++-33-3.2.3-47.3. i386 also in the installation of the package will prompt libc.so.6, the online solution is to install the dependency package, but the search found that some libraries on this machine have been installed. Like what libc.so.6。

A search is done online, and the workaround is to install the missing dependent libraries. But the search found that some of the libraries on this machine are already installed. For example libc.so.6 , the library corresponds to a package name of glibc .

[[email protected] RPM]# Yum list glibc* loaded plugins: Fastestmirror, Refresh-packagekit, securityloading mirror speedsFrom Cached Hostfile *base:mirrors.cug.edu.cn * extras:mirrors.cug.edu.cn * updates:mirrors.skyshe.cn installed packages glibc.x86_642.12-1.149.el6 @anaconda-centos-201410241409.x86_64/6.6glibc-common.x86_642.12-1.149.el6 @anaconda-centos-201410241409.x86_64/6.6glibc-devel.x86_642.12-1.149.el6 @anaconda-centos-201410241409.x86_64/6.6glibc-headers.x86_642.12-1.149.el6 @anaconda-centos- 201410241409.x86_64/6.6 installable packages glibc.i686 2.12-1.149.el6 base glibc-devel.i686 2.12-1.149.el6 base glibc-static.i686 2.12-1.149.el6 base glibc- static.x86_64 2.12-1.149.el6 Span class= "Hljs-keyword" >base glibc-utils.x86_64 2.12-1.149. El6 base 
           -----------------------------------------------------------------------------------------

So the question is, since it's already installed libc.so.6 , why are you missing the library? Continue to find Ah, Baidu search basically no fruit, can only send hope in Google. Finally, the science of Internet access, Google can go on, continue to search, focusing on English results. Finally, Stack Overflow find a similar question and answer, click here to see the original. Here are just a few key words to be extracted:

In Red Hat Enterprise Linux 5, if a package is available for both the main and the compatibility architectures, both arch Itectures of the were installed by default.
In Red Hat Enterprise Linux 6, only the primary architecture are installed by default.
To avoid problems during the Backup-archive client and API installation on a 64-bit machine, being sure to install libstdc++ and compat-libstdc++.

The main idea is that, from the Red Hat Enterprise Linux 6 beginning, the default is to install only the packages required by the master schema, not the compatible schema packages, that is, 64-bit systems will install only 64-bit packages by default. To avoid this problem, in a 64-bit system, install both 64-bit packages and 32-bit compatibility packs. CentOSand from Red Hat Enterprise Linux 6 the relationship will not need me to say, so I feel this answer is more reliable, quickly try it.

[Root@cSlave00 RPM]# yum Install glibc.i686 loaded plugins: Fastestmirror, Refresh-packagekit, security settings installation process ... Installed: glibc.i6860:2.12-1.149.el6 as dependency is installed: nss-softokn-freebl.i686 0:3.14.3-18.el6_6 as dependency is upgraded: nss-softokn-freebl.x86_64 0:3.14.3-18.el6_6 complete! [Root @cSlave00 rpm]# RPM-IVH cndrvcups-common-2.60-1.x86_ 64.rpm error:failed dependencies:libstdc++.so.6 is needed by cndrvcups-common-2.60-< Span class= "Hljs-number" >1.x86_64libstdc++.so.6 (cxxabi_1.3) is needed by cndrvcups-common-2.60-1.x86_64   

The result was satisfactory, and sure enough no longer prompted libc.so.6 . Continue to solve libstdc++.so.6 !

[Root@cSlave00 RPM]# Yum list libstdc++* loaded plugins: Fastestmirror, Refresh-packagekit, securityloading mirror speeds from cached Hostfile *base:ftp.sjtu.edu.cn *Extras:mirrors.163.com *updates:ftp.sjtu.edu.cn Installed Packages libstdc++.x86_644.4.7-11.el6@anaconda-centos-201410241409.x86_64/6.6 Installable Packages libstdc++.i6864.4.7-11.el6 Base libstdc++-devel.i6864.4.7-11.el6 Base libstdc++-devel.x86_644.4.7-11.el6 Base libstdc++-docs.x86_644.4.7-11.EL6 base [Root@cSlave00 RPM]# yum Install libstdc++.i686 loaded plugins: Fastestmirror, Refresh-packagekit, security settings installation process ... Installed: libstdc++.i6860:4.4.7-11.el6 as dependency is installed: libgcc.i686 0:4.4.7-11.el6 finished! [Root@cSlave00 RPM]# RPM-IVH cndrvcups-common-2.60-1.x86_64.rpm Preparing ... ########################################### [100%] 1:cndrvcups-common ########################################### [100%]    

the next step is to install compat-libstdc++-33-3.2.3-47.3.i386 successfully.

Installation LoadRunner steps and problems encountered in Linux