[SERVER-12202] Cannot fork with auditing file relative path Created: 24/Dec/13 Updated: 11/Jul/16 Resolved: 13/Jan/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Andy Schwerin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | Error case:
Successful case (note command line params):
|
||||||||
| Participants: |
| Description |
|
When it fails, it successfully opens the server log file, but the auditing log file does not get created. The server log file is empty. I can successfully start the server by using & instead of --fork, and everything appears to work properly, including both log files. Therefore, I suspect the problem lies in the interaction of the --fork code with the logging infrastructure code. |
| Comments |
| Comment by Githook User [ 13/Jan/14 ] |
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@10gen.com'}Message: Also, improve error reporting. |
| Comment by Githook User [ 13/Jan/14 ] |
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@10gen.com'}Message: |
| Comment by Andy Schwerin [ 26/Dec/13 ] |
|
Relative paths need to work. |
| Comment by Eric Milkie [ 24/Dec/13 ] |
|
It's breaking because the audit log path is relative, not absolute. We should fix this to produce a proper error message, or fix it so that relative paths work. |