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

Starting Mongo failed: connection() error occurred during connection handshakeBug #1075

Closed
billyxiong opened this issue Sep 14, 2023 · 20 comments
Labels
bug Categorizes issue or PR as related to a bug.

Comments

@billyxiong
Copy link

What happened?

image
image

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

```console # On Linux: $ cat /etc/os-release # paste output here $ uname -a # paste output here # On Windows: C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture # paste output here ```

Install tools

@billyxiong billyxiong added the bug Categorizes issue or PR as related to a bug. label Sep 14, 2023
@skiffer-git
Copy link
Member

How is the configuration information modified?

@billyxiong
Copy link
Author

use the default configuration

@skiffer-git
Copy link
Member

docker ps

@kubbot
Copy link
Contributor

kubbot commented Sep 14, 2023

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


docker ps

@billyxiong
Copy link
Author

image

@kubbot
Copy link
Contributor

kubbot commented Sep 14, 2023

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


image

@billyxiong
Copy link
Author

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?"

@kubbot
Copy link
Contributor

kubbot commented Sep 14, 2023

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


branch 3.3?

@skiffer-git
Copy link
Member

release-v3.3 ?

@billyxiong
Copy link
Author

3.3.1 , the lastest release

@skiffer-git
Copy link
Member

It's possible that you have previously set a password for Mongo. It is recommended to delete the components and restart the container

@skiffer-git
Copy link
Member

docker compose down;
rm components -rf;
docker compose up -d;

@skiffer-git
Copy link
Member

Usually, the password in the .env file and the password in the config/config.yaml are not consistent."

@billyxiong
Copy link
Author

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.

@skiffer-git
Copy link
Member

Have you executed 'make init'?

@billyxiong
Copy link
Author

of course

@billyxiong
Copy link
Author

it works after
export PASSWORD="openIM123"

@skiffer-git
Copy link
Member

Check the configuration for Mongo in the config.yaml file.

@kubbot
Copy link
Contributor

kubbot commented Nov 14, 2023

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.

@kubbot
Copy link
Contributor

kubbot commented Nov 22, 2023

This issue was closed because it has been stalled for 7 days with no activity.

@kubbot kubbot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

3 participants