[SERVER-48299] Provide more detail in "error stopping mongod" test errors Created: 19/May/20  Updated: 27/Oct/23  Resolved: 27/Oct/23

Status: Closed
Project: Core Server
Component/s: Shell, Testing Infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
Resolution: Won't Do Votes: 0
Labels: tig-qwin-eligible
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Server Development Platform
Participants:
Story Points: 3

 Description   

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)


 Comments   
Comment by Steve Gross [ 28/Aug/23 ]

Per backlog review w/ alex.neben@mongodb.com : this is still a good idea. Keeping open.

Comment by Robert Guo (Inactive) [ 01/Jul/22 ]

Putting this on SDP's radar as a pain point with resmoke's primitive process management.

Comment by Steven Vannelli [ 10/May/22 ]

Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions.

Generated at Thu Feb 08 05:16:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.