Neotys.com

Unanswered question

Neoload Load generator Issue

Hi,
I usually face issue with Neoload Load Generator availability.Even though it is available at the point of time ,it may throw errror like "Load Generators are unavailable". This issue comes while running the test in jenkins as well. And in next 2 -3 try ,i usually able to run the test. I think if i see the green status of LGs in neoload controller, it means it is available.

Please let me know what else i have to check before running the test so that i can avoid the error.

Abhishek K.
Abhishek K.

Abhishek K.

Level
0
98 / 100
points
Answer count
2 answers
Category
NeoLoad Runtime
Author name
Abhishek K.
Date
March 28, 2019
over 5 years ago
Hits
viewed 1428 times
question
q

Answers

Nouredine A.

Nouredine A.

Level
4
5000 / 5000
points
Team

The green status means that the Load generator agent is available. But when you start your test the agent will start the load generator process. It's that process that seems to not start or to make to much time to start.

When you start your test you can check your task manager if a new java.exe process is able to start. If yes then maybe the issue is only that it takes too much time. There's a 20s timeout for the LG to start otherwise the controller will give up and you will get that error message.

So again if you do see that java.exe process you should check if you do not have any anti-virus that could slow down the starting process. You can try to increase the timeout in case the issue is just a matter of time but normally 20s is far enough.

This can be configured in the <install_dir>\conf\agent.properties of your load generator. It's that key: lg.start.delay=20000 in millisecond

 

Author name
Nouredine A.
Date
answer
a
Abhishek K.
Abhishek K.

Abhishek K.

Level
0
98 / 100
points

Hi Nouredine,

After doing the above suggested changes, i did not get the issue since then for onprem load generators.

But this availability issue i am also facing with kubernetes load generators sometimes even though load generator has been successfully spawned using the neoload loadgenerator official image from the docker hub.

In that case when controller which is also in kubernetes tries to initialize the load generator, i get message like load generator is not available.

So do i need to implement the same setting for the kubernetes load generators as well?

Thanks,
Abhishek

Author name
Abhishek K.
Date
answer
a