[SERVER-2514] MongoD started with --fork crashes when initiating a replica set Created: 10/Feb/11 Updated: 12/Jul/16 Resolved: 12/Feb/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 1.7.5 |
| Fix Version/s: | 1.7.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Brendan W. McAdams | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Mac OS 10.6.6 , 64 bit MongoDB 1.7.5 |
||
| Attachments: |
|
| Operating System: | OS X |
| Participants: |
| Description |
|
Started up 2 local mongodb instances on my laptop, they work fine to initiate a replica set if started in the foreground. However, if I start them with --fork, upon initiating the replica set the mongod instance I was connected to when initiating crashes with: Wed Feb 9 19:11:43 [conn2] replSet replSetInitiate all members seem up Wed Feb 9 19:11:43 Backtrace: Startup commands for mongod are mongod --port 27018 --replSet test --logpath test1.log --dbpath rs1 --fork Replica set config { , { "_id" : 1, "host" : "localhost:27019" } ] The shell session looks like this: > rs.initiate(config) , { _id: 1.0, host: "localhost:27019" } ] } } to: 127.0.0.1:27018 Log file attached for both servers. This does not occur when --fork is not used. |
| Comments |
| Comment by auto [ 12/Feb/11 ] |
|
Author: {u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: need to run unit tests after fork so system state is stable |