Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
1.8.1
-
None
-
None
-
3 node replica set each running RHEL. One node is an 8 hour delay.
Description
I'm actually sure where to report this since I'm not completely sure if this is a driver problem. In our production environment, we are connecting to one particular database using a database user. The username is pretty simple and the password is a random string of upper/lowercase letters and numbers. When specifying all three nodes in the connection string and using a password that contains numbers we keep getting a timeout exception from the driver. The logs on the mongo server repeated report a key mismatch error. When we remove the numbers from the password, the connection succeeds. When we specify just the primary server in the connection string and connect using the password containing numbers, the connection succeeds. When we put the numbers back into password and again specify the 3 nodes in the connection string, the connection fails with a timeout exception and the mongo logs report a key mismatch. We've also tried creating another database with another user using the password random password with the same result. The strange thing is, we have a test environment setup the exact same way and we can't get replicate this issue.