Controller terminated during the test run

[sandeep pachipulusu]

Hi,

I started a test run in controller for 4 hrs duration.After 2 hours of the test run,controller got crashed and suddenly closed.Is there any possibility of extracting the results from the raw data obtained from the results file.

can someone help on this issue if u faced earlier.

Thanks,

Sandeep

[Manik Sikka]

Open the controller again and manually collate the resutls...

Controller menu bar-> Results -> Collate Results -> Collate Results

That should work for you...

Thank you,

Manik

--
You received this message because you are subscribed to the Google "LoadRunner" group.
To post to this group, send email to LR-Loa...@googlegroups.com
To unsubscribe from this group, send email to
LR-LoadRunne...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/LR-LoadRunner?hl=en

--
Thanks & Regards,
Manik Sikka
(718) 775 7022

[vivek]

Make sure you have enough memory in the machine for the specified number of Vusers you run in a scenario. Finding the foot print for a single Vuser would help greatly when specifying number of Vusers. The Loadrunner vusers are run by a process called 'mdrv.exe'. Whenever this process encounters errors due to various reasons controller may terminate. Make use of the below suggestions to overcome this issue.

1) The Host machine ( Load generator) is running too many Vusers as a result of which it system resources are being maximized. ( i.e. Consistent over 90% CPU and Memory utilization). The mdrv process does not get enough resources to process the request as a result it fails

 

2) If you have Custom C coding, there is a possibility of allocated memory not being freed or memory violation errors which can lead to 'mdrv process termination'.

 

3) Replay the script with think time.

 

4) Turn off extended log when running the script in the controller.

 

5) Do not use the controller itself as the loadgenerator. i.e. have a remote LoadGenerator.

 

6) Introduce iteration pacing, if running more than one iteration each vuser.

 

7) Open the file C:\WinNT\wlrun7.ini in a text editor, modify the entry from: AgentMaxThreadsPerDriver=50 to AgentMaxThreadsPerDriver=20 or 10

 

8) Run Agent as process instead of service Launch command prompt and navigate to C:\Program Files\Mercury\Loadrunner\Launch_service\bin and run the command magentserive -remove. This will remove the agent. Now run the command magentproc -install This will install the agent as a process.

 

9) Run vusers as process instead of threads.Please go to Runtime Settings > Miscellaneous > Multithreading > RunVuser as a process.



Good Luck.

--

[Kumar Chalamala]

Did you turn on log while running on controller?
this kills harddisk and eventually chances of controller getting crashed are more.

Never ever turn on Logs (except for send when error occurs) while running a test on Controller.

It is okay to have them on for script validations but not for running tests.

Thanks
Ajay

--

You received this message because you are subscribed to the Google "LoadRunner" group.
To post to this group, send email to LR-Loa...@googlegroups.com
To unsubscribe from this group, send email to
LR-LoadRunne...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/LR-LoadRunner?hl=en

--
Thanks & Regards
Ajay