-
Type:
Improvement
-
Resolution: Won't Do
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Shell, Testing Infrastructure
-
Labels:
-
Server Development Platform
-
3
An example message + stack:
[js_test:backup_restore_stop_start] 2020-05-18T21:35:52.494+0000 | 2020-05-18T21:35:52.398Z I - 22821 [js] "shell: stopped mongo program on port {port}","attr":{"port":20021}
[js_test:backup_restore_stop_start] 2020-05-18T21:35:52.948+0000 uncaught exception: StopError: MongoDB process stopped with exit code: -9 :
[js_test:backup_restore_stop_start] 2020-05-18T21:35:52.948+0000 StopError: MongoDB process stopped with exit code: -9
[js_test:backup_restore_stop_start] 2020-05-18T21:35:52.948+0000 MongoRunner.StopError@src/mongo/shell/servers.js:924:44
[js_test:backup_restore_stop_start] 2020-05-18T21:35:52.948+0000 MongoRunner.stopMongod@src/mongo/shell/servers.js:1028:15
[js_test:backup_restore_stop_start] 2020-05-18T21:35:52.948+0000 ReplSetTest/this.stop<@src/mongo/shell/replsettest.js:2984:19
[js_test:backup_restore_stop_start] 2020-05-18T21:35:52.948+0000 _nodeParamToConn/<@src/mongo/shell/replsettest.js:226:57
[js_test:backup_restore_stop_start] 2020-05-18T21:35:52.948+0000 _nodeParamToSingleNode/<@src/mongo/shell/replsettest.js:260:45
While the port is often all that's needed to identify the node in question, things can be tricky because a port is used across restarts. Other information I use to identify process lifetimes that should be included if available:
- The process id
- The dbpath being used
- The binary name (e.g: mongo, mongos, mongobridge, mongod, mongod-4.4)