Neotys.com

Unanswered question

neoload.agent.Agent: Failed to start and register Load Generator?

Hello!

We are able to start the load generator initially as we see this in the logs :

INFO - neoload.agent.Agent: Agent started

On the controller machine also I am able to see the green colored icon next to the Load Generator IP. But when I try to check the user path using this load generator machine, I get the message in the GUI on the controller saying that 'load generator is unavailable'. And simultaneously I see this in the load generator logs as well :

ERROR - neoload.agent.Agent: Failed to start and register Load Generator: Load Generator off: process created but not registered after waiting delay (key "lg.start.delay" in agent.properties).

AND

[Transport_ThreadPool_Listener_Executor-10] ERROR com.neotys.communication.endpoint.EndPointsRegistryImpl - com.neotys.nl.agent.transport.AgentService.startAndRegisterLoadGenerator(f0d50597-65be-475a-91ef-d90619215dfb) error:
com.neotys.nl.controller.L: Failed to start Load Generator on 0.0.0.0. The Load Generator process has been created but has not registered after waiting delay (key "lg.start.delay" in agent.properties). : an error occurred while communicating with '0.0.0.0'
at com.neotys.nl.agent.transport.AgentServiceImpl.handleLgResponseCode(AgentServiceImpl.java:233)

How am I getting a start delay message after 30 minutes when I can see the green colored icon next to the load generator when I start the load generator process?

What does this failed to register' message mean?

The controller is a windows machine and the load generator is a linux machine.

Can anyone help me with resolving this issue?

Gautam B.
Gautam B.

Gautam B.

Level
0
1 / 100
point
Answer count
1 answer
Category
NeoLoad Runtime
Author name
Gautam B.
Date
January 15, 2019
over 5 years ago
Hits
viewed 837 times
question
q

Answers

Nouredine A.

Nouredine A.

Level
4
5000 / 5000
points
Team

The green colour in your NeoLoad controller for your load generator is the agent. When you start a check virtual user or a test that agent will spawn another java.exe process which is the load generator process.

The error raised on controller side is more a consequence rather than the root cause. You need to check the log files located in your load generator.

They are located under $HOME/.neotys/neoload/<version>/logs. Check all the logs and especially the loadgenerator***log files.

Author name
Nouredine A.
Date
answer
a