-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
Labels:
-
ALL
See
http://mci.10gen.com/ui/task/mongodb_mongo_master_cxx11_ubuntu1204_64_730c2513f4f0af9068ce7ba0852cb63db56d2c99_13_11_27_18_28_06_ssl_ubuntu1204
http://mci.10gen.com/ui/task/mongodb_mongo_master_enterprise_ubuntu1204_64_730c2513f4f0af9068ce7ba0852cb63db56d2c99_13_11_27_18_28_06_ssl_ubuntu1204
The logs for the individual tests within above tasks are very short because it looks as if the initial connection attempt fails - for instance, the entire log for disable_x509.js for the first one is
MongoDB shell version: 2.5.5-pre-
connecting to: 127.0.0.1:27999/test
2013-11-27T20:29:31.051+0000 warning: SSL peer certificate validation failed:certificate has expired
2013-11-27T20:29:31.051+0000 warning: The server certificate does not match the host name 127.0.0.1
2013-11-27T20:29:31.051+0000 DBClientCursor::init call() failed
2013-11-27T20:29:31.052+0000 Error: DBClientBase::findN: transport error: 127.0.0.1:27999 ns: admin.$cmd query: { whatsmyuri: 1 } at src/mongo/shell/mongo.js:148
exception: connect failed