[SERVER-11226] Mongod cannot use relative file paths for keyFile if --fork is enabled Created: 16/Oct/13 Updated: 11/Jul/16 Resolved: 24/Oct/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security |
| Affects Version/s: | 2.4.6 |
| Fix Version/s: | 2.5.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kyle Erf | Assignee: | Matt Dannenberg |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
OSX 64, Linux 64 |
||
| Operating System: | Linux | ||
| Steps To Reproduce: | 1.) set up a keyfile and all other necessary directories to run mongod 2.) Run
3.) Now run
4.) Note that changing the myKeyFile path to be absolute allows mongod to start |
||
| Participants: |
| Description |
|
When running a mongod with a keyfile given on the command line, both full file paths and file paths relative to the working directory are acceptable input for the keyFile argument. That is, both keyFile /home/usr/keys/myKeyFile and keyFile myKeyFile should both work, assuming myKeyFile exists in the working directory. However, if one enables fork along with keyFile only the full directory path starting from root is acceptable. Using a local filepath from the working directory will result in error getting file myKeyFile: No such file or directory and cause mongo to fail on startup. |
| Comments |
| Comment by auto [ 24/Oct/13 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: |
| Comment by Daniel Pasette (Inactive) [ 17/Oct/13 ] |
|
same fix as |