[SERVER-19881] WiredTiger library panic after checkpoint server error Created: 12/Aug/15 Updated: 13/Jun/16 Resolved: 06/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage, WiredTiger |
| Affects Version/s: | 3.0.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | white_li | Assignee: | David Hows |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
log context and trace
|
| Comments |
| Comment by Ramon Fernandez Marina [ 13/Jun/16 ] |
|
Thanks for the update DrIanSharp@gmail.com, and glad to hear the documentation helped with this matter. |
| Comment by Ian Sharp [X] [ 12/Jun/16 ] |
|
getting this error checkpoint-server: the process must exit and restart: WT_PANIC: WiredTiger library panic Following directions at: https://docs.mongodb.com/ecosystem/platforms/amazon-ec2/ solved it for me. mongod -version db version v3.2.5 df -h i start my mongod in a replicaset with sudo mongod --fork --port 27017 --replSet go --logpath ~/log/mongo.log |
| Comment by David Hows [ 06/Oct/15 ] |
|
Marking as "Cannot Reproduce" |
| Comment by David Hows [ 28/Sep/15 ] |
|
Hi swordsmanli, Sorry for the long time between responses here. Assuming your system has not been restarted, can you please post the full dmesg log for this system, not just the grep for "error". Not all system error messages contain this word and we will need to review the whole system log. If the system has been rebooted, have you seen this error subsequently? If not, it may not be possible to gather the necessary information required to find root cause here. Thanks, |
| Comment by white_li [ 28/Aug/15 ] |
|
hi Ramon ulimit limits core file size (blocks, -c) 0 only error info in dmesg |
| Comment by Ramon Fernandez Marina [ 25/Aug/15 ] |
|
swordsmanli, can you post the output of ulimit -a on this system? Also, are there any quotas? Finally, can you check your system logs for storage errors? These are three possible culprits for this behavior at this stage. Thanks, |
| Comment by white_li [ 12/Aug/15 ] |
|
hello Michael disk is not full wt file stats it seems i can not write to 0--2932365438447056541.wt |
| Comment by Michael Cahill (Inactive) [ 12/Aug/15 ] |
|
swordsmanli, that error indicates that writing to a file has failed. In this case, the write apparently failed because the disk was full (one collection grew to almost 500GB, I can't tell how much data is in other collections). What is your request: an explanation, a clearer error message, more graceful handling of out-of-space errors, or something else? |