[SERVER-2345] Setting dbpath w/ --fork does not work as intended Created: 10/Jan/11  Updated: 12/Jul/16  Resolved: 25/Jan/11

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

Type: Bug Priority: Major - P3
Reporter: Suhail Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OSX


Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

Does not work:
bin/mongod --dbpath data/node --fork --logpath log/mongodb.node.log

Fixes:
bin/mongod --dbpath $PWD/data/node --fork --logpath log/mongodb.node.log

Folder structure:
data/node

Executing commands a level above data.

Chat log:

[11:30am] traceback0: I am doing bin/mongod --dbpath ./data/node but it claims it can't find that path
[11:30am] traceback0: doesn't look like it's relative?
[11:31am] mstearn: traceback0: does that path exist?
[11:31am] traceback0: mstearn: $pwd/data/node does
[11:31am] traceback0: mstearn: If I run it w/o --fork / --logpath it works
[11:32am] mstearn: hrm
[11:32am] traceback0: weird..
[11:32am] mstearn: try a non-relative path with fork
[11:33am] traceback0: mstearn: yeah if I tack on a $PWD/data/node – works fine
[11:34am] traceback0: looks like a bug
[11:34am] mstearn: traceback0: could you jira it?



 Comments   
Comment by auto [ 25/Jan/11 ]

Author:

{u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: fix --fork and relative --dbpath SERVER-2345
https://github.com/mongodb/mongo/commit/d1e0c5a47a5564e05bb0a3d118214e19f9e44751

Comment by Guanqun Lu [ 12/Jan/11 ]

simple fix for this problem:

https://github.com/guanqun/mongo/commit/0cc95094dd69f366c3d428a61f189c8dcb790e18

please review.
thanks.

Generated at Thu Feb 08 02:59:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.