Share this page

# Known issues for Controller

This section describes general troubleshooting and known issues for Controller.

In this topic:

## Vusers do not stop with scenario

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

Back to top

## Secure communication with TLS (SSL)

OpenText Professional Performance Engineering uses a version of OpenSSL that enforces additional constraints for secure communication.

OpenSSL requires that CA certificates include the following basic constraint:CA (Certificate Authority)

Use the available tools to create and install a new CA certificate and new TLS certificates on each 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 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 Install.

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 protocol is 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 how 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. To apply the fix, update Bash to the 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.

3. Check the vulnerability again, as described in the first step.

Back to top

## Scenario run automation

Problem: The CLI tool is set up to automate the scenario run, but it did not run.

Possible solutions:

- Check that only one instance of Controller is running on the machine.
- Make sure the credentials of the admin user used to run Controller are defined in the CLI tool. For details, see Run scenarios using the CLI tool.

Back to top

## New Scenario dialog box does not close

If you open Controller by double-clicking an .lrs file, you may encounter an issue where the New Scenario dialog box shown at Controller startup cannot be closed.

Solution:

1. Open the file <installdir>/config/wlrun7.ini in a text editor.

2. In the General section of the file, change the value of NewScenarioWindowMode to 2 and save the file. When you open Controller by double-clicking an .lrs file, the New Scenario dialog box is not shown.

   Note: When NewScenarioWindowMode is set to 2, you cannot create a new Controller scenario from VuGen using the Integrations > Create Controller Scenario option in the VuGen toolbar.

Back to top

## Troubleshooting error messages

Each error message displayed in the Controller Output messages window has a message code.

For information about a message, search for the message code number in the Error Codes Guide.

Back to top

See also:

- Introducing Controller

https://admhelp.microfocus.com Professional Performance Engineering,VuGen 8942
Tips to improve your search results... OpenText™ Professional Performance Engineering Help Center OpenText™ Professional Performance Engineering Help 25.1-25.3 All View Local Help Center View Online Help Center Version: