[SERVER-9343] Mongo crashed Created: 12/Apr/13 Updated: 22/Jul/13 Resolved: 16/Apr/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Blocker - P1 |
| Reporter: | Alexander | Assignee: | Stennie Steneker (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Fri Apr 12 19:57:22.135 [initandlisten] MongoDB starting : pid=17744 port=27017 dbpath=/var/lib/mongodb 64-bit host=rymmedia |
||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Mongo crashed with message in log
Reporter: Alexander |
| Comments |
| Comment by Ian Whalen (Inactive) [ 22/Jul/13 ] |
|
vmattila, since this ticket has been closed it would be good if you could open a new ticket with the details of your problem (referencing this ticket if appropriate) so that we can continue the conversation and its resolution there. |
| Comment by Ville Mattila [ 18/Jul/13 ] |
|
Tonight the crash has been very frequent. I have a replica set setup with two nodes, both running locally on my development box. The primary is that crashes, the logged message is "Fatal error in v8::Context::New()". The seems to happen always after db.collection.remove() operation where I delete all records from the collection over PHP (mongo 1.4.1). The collection I clear contains only 20-30 small records, no indexes. |
| Comment by Ville Mattila [ 18/Jul/13 ] |
|
This error is still occassionally encountered on my local virtual machine with following config. $ uname -a $ ulimit -v $ mongod --version |
| Comment by Stennie Steneker (Inactive) [ 16/Apr/13 ] |
|
Hi Alexander, Thank you for confirming that the ulimit change worked. A virtual memory ulimit of 3327200 seems particularly low; it's probable that your mongod memory footprint has increased enough to tip you over that limit. Perhaps the limit had been previously adjusted but was reset on a reboot or upgrade. Per the Linux production notes in the MongoDB manual, the recommended setting for ulimit -v is unlimited. Limits that are set too low may cause operational or performance issues. Thanks, |
| Comment by Alexander [ 16/Apr/13 ] |
|
Yes. It seems to work fine after increasing the address space ulimit. But in previous version of mongo(2.0.1) it worked fine without any changes. |
| Comment by Stennie Steneker (Inactive) [ 16/Apr/13 ] |
|
Hi Alexander, Do you have any update after increasing the address space ulimit? Thanks, |
| Comment by Alexander [ 13/Apr/13 ] |
|
I'll try and then report if there'll be any changes |
| Comment by Daniel Pasette (Inactive) [ 13/Apr/13 ] |
|
can you set it to unlimited? |
| Comment by Alexander [ 13/Apr/13 ] |
|
Yes, I have: |
| Comment by Daniel Pasette (Inactive) [ 13/Apr/13 ] |
|
Do you have a limit on address space set (check with ulimit -v)? |
| Comment by Alexander [ 13/Apr/13 ] |
|
Working under system: > uname -a > php -v > php --ri mongo mongo MongoDB Support => enabled Directive => Local Value => Master Value |