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

[Bug]: The startup script has a judgment error #2006

Closed
1 of 2 tasks
Tracked by #1930
HuangFru opened this issue Sep 20, 2023 · 0 comments · Fixed by #2016
Closed
1 of 2 tasks
Tracked by #1930

[Bug]: The startup script has a judgment error #2006

HuangFru opened this issue Sep 20, 2023 · 0 comments · Fixed by #2016
Labels
type:bug Something isn't working

Comments

@HuangFru
Copy link
Contributor

What happened?

When I first started AMS, it worked fine:
POPO20230920-170105
But when I accidentally started it again:
POPO20230920-170231
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:
POPO20230920-170259
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?

  • Yes I am willing to submit a PR!

Code of Conduct

  • I agree to follow this project's Code of Conduct
@HuangFru HuangFru added the type:bug Something isn't working label Sep 20, 2023
@wangtaohz wangtaohz mentioned this issue Sep 25, 2023
56 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant