Troubleshooting

This topic lists troubleshooting issues and possible solutions, by application area.

Monitoring

The following tables list troubleshooting issues for monitoring.

General

Problem Possible solution

I am running/ran a load test, but my monitor is not displaying any measurements

Check if your monitor or monitoring tool is up and running and that LoadRunner Cloud is connected to it.

I cannot monitor CPU usage on my application.

Verify that the systat package is deployed on the monitored application.

To install the package, run the following command:

apt-get install sysstat

SiteScope

Problem Possible solution

I enabled SiteScope data integration but I am not receiving any SiteScope data on my SiteScope on-premises monitor.

If you selected the Disable integration check box in the SiteScope configuration, but the agent continues to behave as it did before you made the change, restart the SiteScope service.

I disabled SiteScope data integration but I am still receiving SiteScope data on my SiteScope on-premises monitor.

If you cleared the Disable integration check box in the SiteScope configuration, but the agent continues to behave as it did before you made the change, restart the SiteScope service.

The SiteScope on-premises monitor is displaying a monitor that I didn't select. Stop the load test and reset the SiteScope agent and the SiteScope service.
SiteScope was unable to send data to the LoadRunner Cloud agent. Check the data integration log file generated under SiteScope\log folder.

Dynatrace

Problem Possible solution
I am not receiving any data on my Dynatrace monitor. Check that Dynatrace is receiving data from your AUT. If it is not, then the issue is with your AUT.

Back to top

Scripts

The following table lists troubleshooting issues for scripts.

Problem Possible solution

When I run my load test, I am getting load generator alerts.

As a general practice, if your test has multiple scripts it is recommended to check which scripts are causing the load generator alerts and then focus on optimizing the relevant scripts.

My Vusers report out of memory errors so I want to run the Vusers as a process. Enable this feature in LoadRunner Cloud by opening a support ticket.

Back to top

Agents

The following table lists troubleshooting issues for agents.

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

Possible solution 1:

Try restarting the machine and running the on-premises load generator installation again.

Possible solution 2:

  1. Extract the downloaded SetupOneLG.zip file. This extracts the SetupOneLG.exe file to a local folder.

  2. Using 7zip, extract the SetupOneLG.exe file (its archived .exe). This creates a folder containing the setup.exe file.

  3. Run setup.exe.

Back to top

Tests

The following table lists troubleshooting issues for tests.

Problem Possible solution

A test result is marked as archived and cannot be accessed.

By default, results that are older than 18 months are archived. To request retrieval of archived results, open a support ticket.

Back to top

Logs

The following table lists troubleshooting issues for logs.

Problem Possible solution
General

Performance issues when running a load test.

Check to see if Extended Logging is enabled. After the initial debugging run, extended logging is not recommended for a load test.

Back to top

Help Center

The following table lists troubleshooting issues for the Help Center.

Problem Possible solution

Saved links to help pages from previous versions of the Help Center result in a 404 (page not found) error.

  • From the 404 page, click Home Page to access the Home page of the current Help Center.

  • Replace the version number in the saved link with Latest. For example, change the URL:

    https://admhelp.microfocus.com/srl/en/3.4/Content/Resources/_TopNav/_TopNav_Home.htm

    to

    https://admhelp.microfocus.com/srl/en/Latest/Content/Resources/_TopNav/_TopNav_Home.htm

Back to top