Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to shut down? #7

Closed
hyder opened this issue May 23, 2019 · 4 comments
Closed

How to shut down? #7

hyder opened this issue May 23, 2019 · 4 comments

Comments

@hyder
Copy link

hyder commented May 23, 2019

Following the guide works fine. But when I try to run my own test plan, I get the following:

Engine is busy - please try later Engine is busy - please try later Engine is busy - please try later Engine is busy - please try later Engine is busy - please try later Remote engines have been started Waiting for possible Shutdown/StopTestNow/Heapdump message on port 4445

How do I shutdown a test?

@infinitydon
Copy link
Collaborator

You can try by doing a kubectl exec into the master pod (in another shell) and use the following command:

/jmeter/apache-jmeter-5.0/bin/stoptest.sh

@hyder
Copy link
Author

hyder commented May 24, 2019

Thanks!

@rupesh2310
Copy link

You can try by doing a kubectl exec into the master pod (in another shell) and use the following command:
/jmeter/apache-jmeter-5.0/bin/stoptest.sh

above command is run properly but for the next test facing same error again

Starting the test @ Thu Jan 05 06:40:50 UTC 2023 (1672900850822)
Engine is busy - please try later
Remote engines have been started
Waiting for possible Shutdown/StopTestNow/Heapdump message on port 4445

how to fix?

@manitgupta
Copy link

This happens when the slave pods are still executing a test from the previous command. You need to restart the JMeter server in the slaves for them to start accepting requests from the master

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants