You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I first started AMS, it worked fine:
But when I accidentally started it again:
There was a wrong judgment here. It deleted the pid file and tried to restart AMS but failed.
So I can no longer stop the AMS service via shell because it will always get the wrong PID:
I have to use some other method to find the process ID of the AMS that is still running and kill it manually.
What happened?
When I first started AMS, it worked fine:
But when I accidentally started it again:
There was a wrong judgment here. It deleted the pid file and tried to restart AMS but failed.
So I can no longer stop the AMS service via shell because it will always get the wrong PID:
I have to use some other method to find the process ID of the AMS that is still running and kill it manually.
Affects Versions
master
What engines are you seeing the problem on?
AMS
How to reproduce
./bin/ams.sh start
./bin/ams.sh start
./bin/ams.sh stop
Relevant log output
See "What happened?"
Anything else
No response
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: