[SERVER-68111] backtraceLogFile parameter is not recognized Created: 18/Jul/22  Updated: 18/Jul/22  Resolved: 18/Jul/22

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

Type: Bug Priority: Trivial - P5
Reporter: Steve Tarzia Assignee: Steve Tarzia
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

It looks like recent master builds of mongod are not respecting the backtraceLogFile parameter and this is causing some js tests to fail:

% ./build/install/bin/mongod --setParameter backtraceLogFile=/dev/null
{"t":{"$date":"2022-07-18T16:06:43.508Z"},"s":"F",  "c":"CONTROL",  "id":20574,   "ctx":"main","msg":"Error during global initialization","attr":{"error":{"code":2,"codeName":"BadValue","errmsg":"Unknown --setParameter 'backtraceLogFile'"}}}

In the resmoke js-test context:

% python buildscripts/resmoke.py run -j4 --installDir=~/mongo/build/debug/install/bin  jstests/sharding/allow_partial_results.js
...
[js_test:allow_partial_results] c20043| 2022-07-18T11:11:29.688-0500 F  CONTROL  [main] Failed global initialization: BadValue: Unknown --setParameter 'backtraceLogFile'
[js_test:allow_partial_results] d20041| 2022-07-18T11:11:29.703-0500 F  CONTROL  [main] Failed global initialization: BadValue: Unknown --setParameter 'backtraceLogFile'
[js_test:allow_partial_results] c20042| 2022-07-18T11:11:29.705-0500 F  CONTROL  [main] Failed global initialization: BadValue: Unknown --setParameter 'backtraceLogFile'
[js_test:allow_partial_results] d20040| 2022-07-18T11:11:29.715-0500 F  CONTROL  [main] Failed global initialization: BadValue: Unknown --setParameter 'backtraceLogFile'

In jira I only saw BF-25861 that is indirectly tracking this.



 Comments   
Comment by Steve Tarzia [ 18/Jul/22 ]

Actually, this was not a bug but user error on my part.  There was a mismatch between what I was building and what I was testing.  In other words, I was building to build/install/debug/bin but testing build/install/bin.

Sorry for the noise!

Comment by Billy Donahue [ 18/Jul/22 ]

FTR this feature was introduced by Security team. Service arch had nothing to do with it.

Comment by Steve Tarzia [ 18/Jul/22 ]

Actually, based on feedback in a slack thread, I think this is just happening in my environment, not universally.  I am lowering the priority and assigning to myself.

Comment by Steve Tarzia [ 18/Jul/22 ]

I saw this on commit f14733fccae6676c1871bf0565ebff9a441f9640

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