Back to BlogBack to Blog
When LoadRunner Agents Crash
Posted on Aug, 2009 by Admin
The following files are helpful in debugging errors:
- Agent log file: agent.log or m_agent_daemon. This file is located in the temporary directory of the agent machine. It provides information about the connection errors.
- Bridge log file: lr_bridge.log. This file is located in the scenario’s temporary log directory (i.e brr_*\log). lr_bridge controls virtual users during scenario execution.
- Virtual user log files: ScriptName_VuserID.log.
This file is located inside log directory found in scenario result directory.
Here are some common steps to debug problems when LoadRunner Agent crashes:
- Look for specific times at which the LoadRunner Agent dies. If there were a specific time at which the Agent tends to crash, it would indicate that some process on the machine might start at that time interfering with the LoadRunner Agent.
- Check with Network Administrator if there is any port scanning software running on the network.
- Check if there is any antivirus software turned on or scheduled.
- The LoadRunner Agent uses port 50500 and 54345 on local machine. If any other application uses these ports, it may cause the Agent to crash.
- Check the Event Viewer for System logs and/or Application Logs to get details of the time of crashes, and look for accompanying events that might be related.
- If you recently installed any Service Packs for Windows Update for security updates, ensure that the Agent launches successfully after that and is stable.
- If you recently installed any Service Packs or updates on the Controller or Agent machine, make sure that you apply the same Service Packs and updates on all the LoadRunner machines.
- Right-click on the Satellite icon on the system tray and select “View Log” to ensure there are no errors once you launch the Agent.