Known issues for Controller

This section describes general troubleshooting and known issues for Controller.

Note: To troubleshoot error messages, see Troubleshooting Error Messages.

Vusers do not stop with scenario

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

Back to top

Secure communication with TLS (SSL)

LoadRunner Professional uses a version of OpenSSL that enforces additional constraints for secure communication.

OpenSSL (from 1.1.x) requires that CA certificates include the following basic constraint:CA (Certificate Authority)

Upgrade: If you are upgrading from a version earlier than 12.60, and your CA certificate was created in an earlier LoadRunner version using any of the LoadRunner tools, you can no longer use these certificates because they do not include the required constraints. Use the LoadRunner Professional tools to create and install a new CA certificate and new TLS certificates on each LoadRunner Professional machine. For details, see Secure Communication with TLS (SSL).

Organization's CA: If your CA certificate is provided by your organization, verify that the certificate includes the constraints described above. If the required constraints are not defined, your IT department should provide updated CA and TLS certificates to install on the LoadRunner Professional machines.

To verify on Windows:

  1. Double-click the CA certificate and select the Details tab.
  2. Select Extensions only from the Show list, then select Basic Constraints and check that the constraints are defined in the properties area.

To verify on Linux: Use the following command to view certificate information: openssl x509 -in <CA-filename> -noout -text.

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 Installation.

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/certThumbprint parameters
  • 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 Create custom image for load generators on the cloud.

  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

Scenario run automation

Problem: I set up the CLI tool to automate my scenario run but it did not run/is not running.

Possible solutions:

  • Only one instance of Controller can run at a time on the machine. Make sure that no instance of Controller is running on the machine.
  • Make sure the credentials of the admin user that will be used to run Controller are defined in the CLI tool. For details, see Run scenarios using the CLI tool.

See also: