The load generator is storing logs in the root directory instead of the /neo directory we have set up where the load generator is. This is causing the root to fill up and to throw errors. How can I stop the logs from being stored in the root?
The logs are stored under the profile of the user running the test, if your LG agent is started as root or uses sudo, logs are stored as root. You could create a special user for running the test. I'm not sure you can change the path though
I am running NeoLoad 6.3.1 on a Windows 2016 Server, so the built in WAN emulation does not work (known issue). To get around this I have two load generators installed on Linux...
During the initialization phase NeoLoad controller sends all the project information to the load generators including external files if any in multiple different steps.
Do you...
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...
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...
I got this error when using NeoLoadCmd.
Logging to /root/.neotys/neoload/v6.3/logs, as user: root
Loading project: /marche_expertise/Project_DARVA.nlp
Project...
