[SERVER-62559] Core Dumps & Data Files not available in Antithesis Created: 12/Jan/22  Updated: 29/Oct/23  Resolved: 14/Jan/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.3.0

Type: Task Priority: Major - P3
Reporter: Tausif Rahman (Inactive) Assignee: Tausif Rahman (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: STM 2022-01-24
Participants:

 Description   

It looks like you can't kill PID 1 in Docker (https://unix.stackexchange.com/questions/457649/unable-to-kill-process-with-pid-1-in-docker-container), which is why core dumps weren't working. We need to change the docker-compose.yml entrypoint to be a shell script that starts `mongod` instead of directly starting `mongod` as the entrypoint. This makes it so that `mongod` is not PID 1. This is what we do with `mongos`, which is why the core dump for `mongos` worked as expected.

We also need to volume mount the data directory out of the images so that Antithesis can get us the data files for each node.



 Comments   
Comment by Githook User [ 14/Jan/22 ]

Author:

{'name': 'trahman1318', 'email': 'tausif.rahman@mongodb.com', 'username': 'trahman1318'}

Message: SERVER-62559: Core Dumps & Data Files not available in Antithesis
Branch: master
https://github.com/mongodb/mongo/commit/a1c1d800daca43a4f85f85b2bf9422beae0d9c66

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