-
Notifications
You must be signed in to change notification settings - Fork 62
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
can't save configuration
error on subsequent starts
#43
Comments
for use mongo 4.x you also need to change "healthcheck" command, try to this: |
Thanks @fb929. Unfortunately I'm seeing same issue after updating the command. |
can you show me output for rs.status() command?
|
|
Try running this command:
|
|
@greyivy Now everything should work. |
Thank you! It seems to be working correctly across restarts now. |
Container any-sync-dockercompose-any-sync-coordinator_bootstrap-1 service "any-sync-coordinator_bootstrap" didn't complete succes... |
@fb929 容器 any-sync-dockercompose-any-sync-coordinator_bootstrap-1 服务“any-sync-coordinator_bootstrap”未成功完成... |
obviously, you encountered an error at the configuration generation step. |
Have you read a contributing guide?
Current Behavior
Running
make start
works fine the first time. I then runmake stop
to cleanly shutdown and later,make start
again. The stack never comes back up due toany-sync-coordinator_bootstrap-1
. The only message in the logs is:Expected Behavior
The stack can be restarted after it is stopped.
Steps To Reproduce
MONGO_VERSION=4.4.29
in.env.override
make start
make stop
make start
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: