-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Starting Mongo failed: connection() error occurred during connection handshakeBug #1075
Comments
How is the configuration information modified? |
use the default configuration |
docker ps |
docker ps |
I pulled the code successfully last week, but today, when I tried to pull the code on a different machine, it didn't work. Could someone have made changes to the code?" |
branch 3.3? |
release-v3.3 ? |
3.3.1 , the lastest release |
It's possible that you have previously set a password for Mongo. It is recommended to delete the components and restart the container |
docker compose down; |
Usually, the password in the .env file and the password in the config/config.yaml are not consistent." |
The result is still the same, and I haven't modified any configuration settings. Everything was installed with default settings, and the image and components should be the same as before. It's likely that someone made changes to the installation script in the last couple of days. |
Have you executed 'make init'? |
of course |
it works after |
Check the configuration for Mongo in the config.yaml file. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This issue was closed because it has been stalled for 7 days with no activity. |
What happened?
What did you expect to happen?
i want to execute start_all.sh successfully , but failed to connect mongodb , it seems the pasword is incorrect ,but i have nerver change any configuration
How can we reproduce it (as minimally and precisely as possible)?
to execute /scripts/start_all.sh
Anything else we need to know?
No response
version
V3
Cloud provider
OS version
Install tools
The text was updated successfully, but these errors were encountered: