[SERVER-11269] Assertion failure is stopping mongorestore Created: 18/Oct/13 Updated: 10/Dec/14 Resolved: 22/Oct/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Tools |
| Affects Version/s: | debugging with submitter |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pawe? Smoli?ski | Assignee: | Shaun Verch |
| Resolution: | Done | Votes: | 0 |
| Labels: | crash | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux 64-bit. |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
When I'm trying to restore DB backup, I'm getting assertion failure message. Backup has been made by mongobackup ver. 2.4.4 (in production env) and I've tried to restore both using 2.4.4 and 2.4.6. In all cases I'm getting following error messages, after which mongorestore stops working (flags: --journal --directoryperdb --dbpath): MongoDB 2.4.4: MongoDB 2.4.6: |
| Comments |
| Comment by Rajesh Mandot [ 14/Nov/14 ] |
|
I am getting the same error while restoring the dump with noobjcheck option for one of the collection. What was the resolution? Is the backup file corrupted? Can this file be checked somehow - if its corrupted? |
| Comment by Daniel Pasette (Inactive) [ 22/Oct/13 ] |
|
Looks as if your backups are corrupted. If you find that is not the case, please re-open this issue. |
| Comment by Shaun Verch [ 21/Oct/13 ] |
|
Hi Pawel, The assertion means that mongorestore found a document with a bad size field. If you provide the following information it will help us diagnose the issue: 1. Do you see this assertion when you try to restore any backup, or just one? Thanks, |
| Comment by Pawe? Smoli?ski [ 19/Oct/13 ] |
|
OK, I've found that it may be related to not-working mongobackup, as backup files are sth about 20-30% smaller than they should: |