Troubleshoot on-premises load generators

This topic provides tips for troubleshooting your on-premises load generator.

Authentication failure

Problem: When trying to connect, you receive one of the following messages:

  • HTTP status code: 403
  • Failed fetching token, credentials failed
  • Incorrect password or user name

Reason: The configured username/password are incorrect, or the account may be locked.

Solution: Check your username/password or wait for your account to be unlocked.

Note: Federated accounts are not supported.

Back to top

Failed to connect to the connectivity testing service

Problem: In the load generator configuration tool, when you click Save & Test, the tool tries to connect to the network connectivity test service, https://oplg-test.loadrunner-cloud.com. If there is a connectivity problem, you receive a message "Failed to connect to the connectivity testing service".

Solution: Contact your network/security team to configure the firewall to whitelist the destination.

For more information, see On-premises load generators behind a firewall.

Back to top

Load generator cannot connect to LoadRunner Cloud

Problem: The load generator is unable to connect to LoadRunner Cloud.

Solution: Ask your network or security team to allow a secure (HTTPS) connection using port 443, to LoadRunner Cloud.

If the load generator needs to use a Web proxy to connect LoadRunner Cloud, enter the proxy details in the On-premises load generator configuration tool Misc tab.

Back to top

Failed to save configuration

Problem: The load generator configuration tool failed to save the configuration to a file.

Solution: Start the configuration tool as an administrator (right-click > Run as administrator) and then try saving it again.

Tip: In general we recommend starting the load generator configuration tool and load generator agent as an administrator.

Back to top

Certificate issues

Problem: When trying to connect, you receive one of the following messages:

  • Self-signed certificate in certificate chain
  • Unable to find local issuer certificate
  • Hostname/IP does not match certificate's altnames

Reason: These are the typical errors when the HTTPS connection is intercepted by the network/security infrastructure. This issue is apparent when you open LoadRunner Cloud in your browser on the on-premises load generator machine. Note that the certificate for “*.saas.microfocus.com” is issued by an internal certificate authority in your organization.

Solution: Contact your network/security team to whitelist the URL.

Alternatively, perform the following:

  1. Obtain the internal CA certificates (all intermediate and root CAs) in .pem format.
  2. Copy the .pem files into the %SRL_HOME%\certs folder.
  3. In the Options tab, add the SRL_AGENT_LOAD_EXTRA_CERTS parameter and set it to true.
  4. Save the configuration and restart the agent.

Back to top

Cannot connect to VTS server when proxy is configured

Problem: Vusers running on an on-premises load generator fails to connect to the VTS server when a proxy is configured. A typical error message is “lrvtc_connect: Failed to connect to the server”.

Solution: Perform the following actions:

  1. Set the no_proxy parameter to the IP address or domain name of the VTS server.

  2. Save the configuration and restart the agent.
  3. Optionally enter additional domains or IPs separated by commas. For example: 1.2.3.4, myvtsserver1, myvtsserver2.

Back to top

Test stuck in Initializing stage

Problem: The load generator is connected, but the tests are stuck in the Initializing stage.

Reason 1: The load generator is unable to connect to LoadRunner Cloud runtime control components.

Solution 1: Ask your network/security team to configure the firewall to whitelist the destination. For more information, see On-premises load generators behind a firewall.

Reason 2: Vusers are failing to start.

Solution 2: Manually run your script on load generator machine to see if it can be replayed successfully. For example: mdrv -usr MyScript.usr. Logs will be generated in current directory.

Reason 3: Some required script dependencies are missing.

Solution 3: Install and configure dependencies on the load generator machine according to the scripts' requirements. For example, to run SAP GUI scripts, the SAP GUI client must be installed and properly configured.

Back to top

Vuser logs

To collect Vusers logs from on-premises load generators, enable Collect Vuser logs from on-premises load generators in the test’s General page. Enable it for each load generator. For details, see Enable logs.

By default, Vuser logs are automatically deleted from the load generator machines after the test run. To configure your on-premises load generator to store Vuser logs from the latest test run locally, set a parameter in the Options tab.

To save the logs, set the SRL_AGENT_KEEP_VUSER_LOGS parameter to true.

The logs are stored in the %TEMP% folder on the load generator machine and start with inj_o_xx.

Back to top

Disk space issues

Problem: An error is displayed when installing an on-premises load generator indicating that there is not enough disk space, even though there is.

Solution 1:

Restart the machine and re-run the on-premises load generator installation.

Solution 2:

Download and run the latest version of the SetupOneLG.zip file.

  1. To download the setup file, go to LoadRunner Cloud Home page > Get tools > Agents > Get Load Generator.
  2. Extract the downloaded SetupOneLG.zip file. This extracts the SetupOneLG.exe file to a local folder.
  3. Using 7zip, extract the contents of SetupOneLG.exe. This creates a folder containing the setup.exe file.

  4. Run setup.exe.

Back to top

 

See also: