[SERVER-7518] mongodump --dbpath /var/lib/mongodb/ assertion Created: 31/Oct/12  Updated: 08/Mar/13  Resolved: 03/Dec/12

Status: Closed
Project: Core Server
Component/s: Tools
Affects Version/s: 2.2.0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Peter Assignee: Stephen Lee
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:
  1. emerge --info
    Portage 2.2.0_alpha86 (default/linux/amd64/10.0, gcc-4.5.3, glibc-2.14.1-r2, 3.2.6-gentoo x86_64)
    =================================================================
    System uname: Linux-3.2.6-gentoo-x86_64-Intel-R-Xeon-R-_CPU_E31230@_3.20GHz-with-gentoo-2.1
    Timestamp of tree: Sun, 21 Oct 2012 00:45:01 +0000
    app-shells/bash: 4.2_p20
    dev-lang/python: 2.7.2-r3, 3.2.2
    dev-util/pkgconfig: 0.26
    sys-apps/baselayout: 2.1
    sys-apps/openrc: 0.9.9.3
    sys-apps/sandbox: 2.5
    sys-devel/autoconf: 2.68
    sys-devel/automake: 1.11.3
    sys-devel/binutils: 2.22-r1
    sys-devel/gcc: 4.5.3-r2
    sys-devel/gcc-config: 1.5-r2
    sys-devel/libtool: 2.4.2
    sys-devel/make: 3.82-r3
    sys-kernel/linux-headers: 3.2 (virtual/os-headers)
    sys-libs/glibc: 2.14.1-r2
    dev-libs/boost: 1.49.0-r1

Attachments: File mongodump.crash-dbpath    
Operating System: Linux
Participants:

 Description   

mongodump --dbpath /var/lib/mongodb/ issues assertion:
Assertion: 10320:BSONElement: bad type 86
0xa60a66 0x76ee86 0x553685 0x679baf 0x8cd98e 0x557cc6 0x55c815 0x55e906 0x75b10e 0x54df80 0x7f8aca17dfed 0x54dbe9
mongodump(_ZN5mongo15printStackTraceERSo+0x26) [0xa60a66]
mongodump(_ZN5mongo11msgassertedEiPKc+0x96) [0x76ee86]
mongodump(_ZNK5mongo11BSONElement4sizeEv+0x165) [0x553685]
mongodump(_ZN5mongo15BSONObjIterator4nextEv+0x4f) [0x679baf]
mongodump(_ZNK5mongo7BSONObj10jsonStringENS_16JsonStringFormatEi+0xce) [0x8cd98e]
mongodump(_ZN4Dump17writeMetadataFileESsN5boost11filesystem210basic_pathISsNS1_11path_traitsEEESt3mapISsN5mongo7BSONObjESt4lessISsESaISt4pairIKSsS7_EEESt8multimapISsS7_S9_SD_E+0x2c6) [0x557cc6]
mongodump(_ZN4Dump2goESsN5boost11filesystem210basic_pathISsNS1_11path_traitsEEE+0x1595) [0x55c815]
mongodump(_ZN4Dump3runEv+0x19c6) [0x55e906]
mongodump(_ZN5mongo4Tool4mainEiPPc+0x77e) [0x75b10e]
mongodump(main+0x30) [0x54df80]
/lib64/libc.so.6(__libc_start_main+0xfd) [0x7f8aca17dfed]
mongodump() [0x54dbe9]
assertion: 10320 BSONElement: bad type 86

What is this? Full log in attachment



 Comments   
Comment by Peter [ 06/Dec/12 ]

This also works with mongodb-linux-x86_64-2.3.1.

Comment by Stephen Lee [ 03/Dec/12 ]

Peter, I'm closing this for now. If you have a chance to look at this again, feel free to comment and reopen the ticket.

Comment by Stephen Lee [ 08/Nov/12 ]

Peter, I'm resolving this for now, but please reopen the ticket if you've had a chance to try the v2.0.7 mongodump and validate your collections.

Comment by Stephen Lee [ 01/Nov/12 ]

Peter,

First, can you try the same command + args using mongodump from v2.0.7? If this works, then there's an issue in mongodump v2.2.

Second, can you run db.coll.validate(true) from the mongo shell v2.2.0 on each collection across all your databases. This will walk through each document and inspect all data structures for corruption and validity. If a collection is large this may take a while and will cause effectively cause the system to wait to do anything (no writes will be allowed) until it is done.

-Stephen

Generated at Thu Feb 08 03:14:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.