Troubleshooting and Limitations for Controller

Vusers do not stop with scenario

If your script contains code that is not part of the LoadRunner API, the Vusers may not stop running immediately after you stop the scenario.

Linux Machine Issues

This section describes how to troubleshoot problems with a test run on a Linux machine. For more information, see the Linux section in the LoadRunner Installation Guide.

Error when running Load Generator on RedHat Enterprise Linux 5.x with SELinux enabled

During use of the Load Generator on RHEL 5.x, you might receive the following error:

"m_agent_daemon: error while loading shared libraries: /opt/HP/HP_LoadGenerator/bin/ cannot restore segment prot after reloc: Permission denied."

This problem occurs because SELinux is installed and enabled on the machine. SELinux is preventing the specified shared library from loading.


There are two possible workarounds:

  1. Before using the Load Generator, disable SELinux using the command "setenforce 0".

  2. If you want to keep SELinux enabled, you can change the security context of all problematic libraries (for example, <Path_to_LoadGenerator>/bin/*.so" to "textrel_shlib_t").
    To do this, execute the command: "chcon -t textrel_shlib_t <Path_to_LoadGenerator>/bin/*.so"

Linux system limits exceeded

Each VUser may open many files and TCP connections during a run. When running many VUsers, a run may fail because Linux system-wide limits are exceeded. To address this, you can adjust Linux settings. For example:

  • You can increase the soft and hard file limits in /etc/security/limits.conf.
    The following values are recommended, but you should experiment to find the best values for your needs.

    • soft: 65535

    • hard: 131070
  • You can expand the port range. The recommended maximum range is: 
    sysctl -w net.ipv4.ip_local_port_range="1024 65535"
  • You can also increase available ports by decreasing the minimum time that a socket remains in TIME_WAIT state. (Default: net.ipv4.tcp_fin_timeout = 60)

Using Web-based protocols on Linux

When running web-based scripts on Linux, considering the following:

  • WinInet replay does not support Linux
  • You cannot use Windows native NTLM authentication
  • The web_set_certificate_ex does not work with the certIndex parameter
  • When working with Click and Script protocols, ActiveX and Applets are not supported.
  • The web_set_certificate function is not supported.
  • BinaryXML DFE is not supported.
  • RDP and Silverlight protocols are not supported.
  • Other web-based protocols have the same limitations as described above for Web.

Back to top

Shellshock Vulnerability

This section describes how to check if your load generator machine is vulnerable to the Shellshock issue, and guides you high to apply a fix.

This fix applies to Linux load generator machines, and Azure cloud machines, for which you create custom images. For details, see Custom Cloud Images for LoadRunner in the HPLN LoadRunner File Repository.

  1. Check the machine for vulnerability

    Run the following command:

    env 'VAR=() { :;}; echo Bash is vulnerable!' 'FUNCTION()=() { :;}; echo Bash is vulnerable!' bash -c "echo Bash Test"

    • If the result is: Bash is vulnerable!, then you need to apply the fix.
    • If the result is: Bash Test, your machine is not vulnerable, and no further action is required.
  2. Apply the fix

    To apply the fix, you update Bash to latest version. Run the following command:

    apt-get:sudo apt-get update && sudo apt-get install --only-upgrade bash

    • If the result is: Bash is vulnerable!, then you need to apply the fix.
    • If the result is: Bash Test, your machine is not vulnerable, and no further action is required.

    For more information about the affected releases, see the following websites:

  3. Recheck the vulnerability

    Check the vulnerability again as described in the first step

Back to top