[SERVER-1532] Errors not logged if exit and --fork --logpath Created: 01/Aug/10 Updated: 12/Jul/16 Resolved: 02/Aug/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 1.5.7 |
| Fix Version/s: | 1.5.8 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | David Mytton | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
Reproduce steps: mongodb-linux-x86_64-1.5.7/bin/mongod --shardsvr --dbpath data/ --replSet set1 This is deliberately incorrect. Actual output: all output going to: mongodb.log
Expected output: Sun Aug 1 04:05:45 MongoDB starting : pid=1091 port=27018 dbpath=data/ 64-bit
Sun Aug 1 04:05:45 db version v1.5.7, pdfile version 4.5 Sun Aug 1 04:05:45 [initandlisten] shutdown: going to close listening sockets... Sun Aug 1 04:05:45 [initandlisten] shutdown: removing fs lock... Problem The log file is not created because of the error, and since the process is forked before the error occurs, the process fails silently. |
| Comments |
| Comment by auto [ 02/Aug/10 ] |
|
Author: {'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: fix relative logpath args and test logpath before forking |
| Comment by David Mytton [ 02/Aug/10 ] |
|
Using /tmp/x as the --logpath works fine for me too. However, it doesn't work if I use my current directory (/root). I am logged in as root mongod --shardsvr --replSet set1 --fork --logpath log |
| Comment by Eliot Horowitz (Inactive) [ 02/Aug/10 ] |
|
This seems to be working for me... I do: ./mongod --shardsvr --replSet set1 --fork --logpath /tmp/x In /tmp/x i get the error about bad --replSet parameter. Do you not get that? |