-
Notifications
You must be signed in to change notification settings - Fork 37
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
Error: Server is unavailable #62
Comments
Same issue, just updated to Node: v17.4.0. |
Same issue here, with node |
Same here. Downgraded node to v15 and it worked. |
Same issue on |
You probably already tried but switching to node 16 works. |
I created a docker image to run mongodb 5.0.9 with run-rs |
I have the same error on node v19.6.0.
|
It's possible that your environment or system settings do not support IPv6 or are not configured to work with "::1" - the IPv6 loopback address. Therefore, explicitly specifying -h 127.0.0.1 allows for successful connection to the MongoDB server using only IPv4. |
I am getting error while try to start run-rs. When I check data folder, folder 27017 contain some files, but 27018 and 27019 are empty. MongoDB is running at 27017, but it looks like that it wont start servers at 27018 and 27019.
OS: archlinux 5.10.83-1-lts
Node: v17.1.0.
npm: 8.1.3
Purging database... Running '/usr/lib/node_modules/run-rs/4.0.12/mongod' [ 27017, 27018, 27019 ] Starting replica set... Error: Server is unavailable at /usr/lib/node_modules/run-rs/node_modules/mongodb-topology-manager/lib/utils.js:79:40 at Socket.<anonymous> (/usr/lib/node_modules/run-rs/node_modules/mongodb-topology-manager/lib/utils.js:43:5) at Socket.emit (node:events:390:28) at emitErrorNT (node:internal/streams/destroy:164:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at processTicksAndRejections (node:internal/process/task_queues:83:21)
The text was updated successfully, but these errors were encountered: