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

can't save configuration error on subsequent starts #43

Closed
3 tasks done
greyivy opened this issue May 3, 2024 · 11 comments
Closed
3 tasks done

can't save configuration error on subsequent starts #43

greyivy opened this issue May 3, 2024 · 11 comments
Assignees
Labels
bug Something isn't working

Comments

@greyivy
Copy link

greyivy commented May 3, 2024

Have you read a contributing guide?

  • I have read CONTRIBUTING.md
  • I have searched the existing issues and didn't find any that were similar
  • I have considered creating a pull request with fixes instead of a bug report and want to proceed

Current Behavior

Running make start works fine the first time. I then run make stop to cleanly shutdown and later, make start again. The stack never comes back up due to any-sync-coordinator_bootstrap-1. The only message in the logs is:

DEBUG	app	all components started	{"total": 0}
FATAL	main	can't save configuration	{"error": "server selection error: server selection timeout, current topology: { Type: Unknown, Servers: [{ Addr: mongo-1:27001, Type: RSGhost, Average RTT: 1076463 }, ] }"}

Expected Behavior

The stack can be restarted after it is stopped.

Steps To Reproduce

  1. Set MONGO_VERSION=4.4.29 in .env.override
  2. make start
  3. Add a user, populate a space
  4. make stop
  5. make start

Environment

- OS: Linux 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) x86_64 GNU/Linux

Anything else?

No response

@greyivy greyivy added the bug Something isn't working label May 3, 2024
@fb929
Copy link
Collaborator

fb929 commented May 3, 2024

for use mongo 4.x you also need to change "healthcheck" command, try to this:
#29 (comment)

@greyivy
Copy link
Author

greyivy commented May 3, 2024

Thanks @fb929. Unfortunately I'm seeing same issue after updating the command.

@fb929
Copy link
Collaborator

fb929 commented May 4, 2024

Thanks @fb929. Unfortunately I'm seeing same issue after updating the command.

can you show me output for rs.status() command?

docker compose exec mongo-1 mongosh --port 27001 --eval 'rs.status()'

@greyivy
Copy link
Author

greyivy commented May 5, 2024

MongoDB shell version v4.4.29
connecting to: mongodb://127.0.0.1:27001/?compressors=disabled&gssapiServiceName=mongodb
Implicit session: session { "id" : UUID("77f21989-0dd7-4cda-a019-1f78605790a6") }
MongoDB server version: 4.4.29
{
	"ok" : 0,
	"errmsg" : "Our replica set config is invalid or we are not a member of it",
	"code" : 93,
	"codeName" : "InvalidReplicaSetConfig"
}

@fb929
Copy link
Collaborator

fb929 commented May 5, 2024

Try running this command:

 docker compose exec mongo-1 mongo --port 27001 --eval 'rs.reconfig({_id: rs.conf()._id, members: [{ _id: 0, host: "mongo-1:27001" }]}, {force: true});'

@fb929 fb929 self-assigned this May 5, 2024
@greyivy
Copy link
Author

greyivy commented May 7, 2024

MongoDB shell version v4.4.29
connecting to: mongodb://127.0.0.1:27001/?compressors=disabled&gssapiServiceName=mongodb
Implicit session: session { "id" : UUID("7510fc2e-c1ef-463d-a8fc-89ca509539ee") }
MongoDB server version: 4.4.29
{
        "ok" : 1,
        "$clusterTime" : {
                "clusterTime" : Timestamp(1715091024, 1),
                "signature" : {
                        "hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
                        "keyId" : NumberLong(0)
                }
        },
        "operationTime" : Timestamp(1715091024, 1)
}

@fb929
Copy link
Collaborator

fb929 commented May 8, 2024

@greyivy Now everything should work.

@greyivy
Copy link
Author

greyivy commented May 8, 2024

Thank you! It seems to be working correctly across restarts now.

@greyivy greyivy closed this as completed May 8, 2024
@879258354
Copy link

Container any-sync-dockercompose-any-sync-coordinator_bootstrap-1 service "any-sync-coordinator_bootstrap" didn't complete succes...
can't open network configuration file {"error": "open /etc/any-sync-coordinator/network.yml: no such file or directory"}

@879258354
Copy link

@fb929 容器 any-sync-dockercompose-any-sync-coordinator_bootstrap-1 服务“any-sync-coordinator_bootstrap”未成功完成...
无法打开网络配置文件 {“error”: “open /etc/any-sync-coordinator/network.yml: no such file or directory”}

@fb929
Copy link
Collaborator

fb929 commented Jun 26, 2024

Container any-sync-dockercompose-any-sync-coordinator_bootstrap-1 service "any-sync-coordinator_bootstrap" didn't complete succes... can't open network configuration file {"error": "open /etc/any-sync-coordinator/network.yml: no such file or directory"}

obviously, you encountered an error at the configuration generation step.
please show the full output of the make start command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants