This repository has been archived by the owner on Jan 15, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 151
Connection is initialized with nil host. #275
Comments
Looking into this issue further, I think it has to do with the issue Retry on SocketError when calling resolv() #265. It seems it takes down all the nodes if there are DNS issues. Somehow blank nodes end up in the pool and it blows up when trying to connect to one. I had changed my mongoid.yml file to static ips, but it seems Moped ends up using the data from the Replicaset, not the configuration file. |
Also affected by this issue. |
👍 |
Affected too |
closing this as #324 was merged and it should solve this issue |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
A connection is being initialized with a nil host. SSL with a 3 host replica set. I modified connection to spit out its options. I can't figure out how to actually reproduce it. Its very random.
"host: port: 27017 timeout: 5
options: {:ssl=>true, :read=>:primary_preferred, :instrumenter=>ActiveSupport::Notifications, :database=>:ptolts}
Completed 500 Internal Server Error in 24ms
TypeError (no implicit conversion of nil into String):"
The text was updated successfully, but these errors were encountered: