mongodb / mongodb/support-tools
global_mongodb_conf does not grab the config for mongods under automation
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 140
- Forks
- 154
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 2
Description
global_mongodb_conf only gets the config file information for mongod processes that being run manually. It only looks for two file names, /etc/mongodb.conf and /etc/mongod.conf, and does not look for any files that are owned by an Automation Agent.
This can solved by adding one line and modifying one other. This is on line 228 of mdiag.sh:
automation_conf=`ps aux | awk '/automation-mongod.conf/ && !/awk/ { print $NF}'`
section global_mongodb_conf getfiles /etc/mongodb.conf /etc/mongod.conf $automation_conf
I've tested this locally and it works fine on Ubuntu Linux, even on hosts running multiple mongod processes with automation.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at line 228 of mdiag.sh and inspect how global_mongodb_conf gathers configuration paths from running mongod processes. Verify the behavior on Ubuntu hosts with Automation Agent-managed mongod processes, including hosts running multiple mongod instances. Done means the automation-owned configuration is included alongside the existing configuration paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- awk, linux, shell
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100