[SERVER-482] terminate called recursively; when bad paths are given to both log and dbpath Created: 13/Dec/09 Updated: 08/Feb/23 Resolved: 14/Dec/09 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 1.2.0 |
| Fix Version/s: | 1.3.0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Daniel Lo | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
snow leapord. Mac OS X version 10.6.2. Processor: 2.4 GHz intel core 2 duo. 2gb ram. MacBookPro4,1 |
||
| Participants: |
| Description |
|
When I start mongodb with bad paths, it "terminates recursively" /Users/daniello/projects/mongodb_1.2.0>bin/mongod --dbpath=/tmp/this_is_a_bad_path --fork --logpath=/tmp/this_is_a_bad_path/logs.txt terminate called recursively |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 31/Mar/10 ] |
|
marcus: that would have been fixed by the same change. |
| Comment by Marcus van Houdt [ 30/Mar/10 ] |
|
If I start the server (version 1.2.1) using a log directory, instead of a file path, the server works fine for a short while but then stops working at which point queries simply do not return (probably at the point where it actually tries to log something but fails), and I have to kill the server and restart it for it to start functioning again. |
| Comment by auto [ 14/Dec/09 ] |
|
Author: {'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: better handling of invalid logpath setting |