[CDRIVER-2783] test-valgrind-latest-sharded-auth-openssl cannot initialize MongoDB Created: 01/Aug/18 Updated: 28/Oct/23 Resolved: 06/Aug/18 |
|
| Status: | Closed |
| Project: | C Driver |
| Component/s: | tests |
| Affects Version/s: | 1.12.0 |
| Fix Version/s: | 1.13.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | A. Jesse Jiryu Davis | Assignee: | A. Jesse Jiryu Davis |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Description |
|
Seen here: Mongo Orchestration tries to start a sharded cluster of replica sets with SSL and auth. According to the log file in mongo-agxOY7/mongod.log, the replica on port 27219 seems to reject connection attempts from the other replicas:
The replica seems to accept connections from Mongo Orchestration itself, which uses PyMongo to connect. Later, it logs errors like:
I don't know whether the SSL error is the root cause, or a symptom, or doesn't matter. The AuthenticationFailed error seems crucial. The other replicas log similarly. mongos logs:
|
| Comments |
| Comment by Githook User [ 06/Aug/18 ] | |||
|
Author: {'name': 'A. Jesse Jiryu Davis', 'email': 'jesse@mongodb.com', 'username': 'ajdavis'}Message: Work around this Mongo Orchestration issue by using one-node replica https://github.com/10gen/mongo-orchestration/issues/251 | |||
| Comment by Githook User [ 06/Aug/18 ] | |||
|
Author: {'name': 'A. Jesse Jiryu Davis', 'email': 'jesse@mongodb.com', 'username': 'ajdavis'}Message: | |||
| Comment by Shane Harvey [ 06/Aug/18 ] | |||
|
This looks like it's caused by the same issue described in HELP-7061. MO attempts to shutdown the server on port 27218 (log file "/data/mci/4098235018245251bf48b09ce9d836b8/mongoc/MO/db/mongo-IegT5e/mongod.log") and the shutdown command fails on the server with:
Pymongo never gets a network/socket error and is stuck waiting for a response from the mongod. TCP keepalive should eventually cause a socket error but the curl times out first:
| |||
| Comment by A. Jesse Jiryu Davis [ 05/Aug/18 ] | |||
|
Part of the problem is that MongoDB requires shard servers to start with --keyFile if there are multiple servers per shard and auth is enabled, but Mongo Orchestration doesn't do that correctly: https://github.com/10gen/mongo-orchestration/issues/251 Until recently the C Driver's tests of a sharded cluster with OpenSSL and auth weren't running at all. Adding ASAN and Coverity tests happened to add new variants that do test a sharded cluster with OpenSSL and auth, and now we're seeing that our tests are misconfigured. |