You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Caused by: com.mongodb.MongoTimeoutException: Timed out after 10000 ms while waiting for a server that matches ReadPreferenceServerSelector{readPreference=primary}. Client view of cluster state is {type=UNKNOWN, servers=[{address=unifi-mongo:27017, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketOpenException: Exception opening socket}, caused by {java.net.SocketTimeoutException: Connect timed out}}]
NOTE: unifi-mongo is the old host
The text was updated successfully, but these errors were encountered:
NOTE: the host is defined in system.properties, updating that fixes the issue. I wonder if it's worth having a script that'll update that when the env var changes?
-e MONGO_HOST=unifi-db Mongodb Hostname. Only evaluated on first run.
Trying to substitute values in a live system.properties on every start is not worth the risk of breaking installs where people have done something unexpected, which is why we don't do it.
Is there an existing issue for this?
Current Behavior
Even after updating MONGO_HOST and restarting, the container continues to connect to the old MongoDB host, ignoring the new host specified.
Expected Behavior
After changing MONGO_HOST, the container should connect to the newly defined MongoDB host upon restart, rather than continuing to use the old one.
Steps To Reproduce
Environment
CPU architecture
arm64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: