<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 03:13:15 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[SERVER-6963] : -286331391 (0x01EEEEEE) first element: ^A: ?type=108</title>
                <link>https://jira.mongodb.org/browse/SERVER-6963</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;We encountered the following errors a couple of times on PRIMARY master of each of our replication set.&lt;/p&gt;

&lt;p&gt;Mon Sep  3 11:02:17 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn38&amp;#93;&lt;/span&gt; Assertion: 10334:Invalid BSONObj size: -286331391 (0x01EEEEEE) first element: ^A: ?type=108&lt;/p&gt;

&lt;p&gt;When this happened, the SECONDARY take over. Starting PRIMARY again will yield the same error. We have to remove all data files and have former PRIMARY re-replicate from current PRIMARY.&lt;/p&gt;

&lt;p&gt;Note that, this problem never occured before. &lt;/p&gt;

&lt;p&gt;Attach are log files from 2 of our PRIMARY servers.&lt;/p&gt;</description>
                <environment>Mix CentOS 5.8,6.2, and 6.3. All Mongo upgraded from 2.0.6 to 2.2.0 via RPM(YUM). &lt;br/&gt;
There are 2 sharded replication sets with 3 configd servers. Each replication set has 3 servers. Mongos run in each client (web server). All client connect to localhost to use MongoDB.&lt;br/&gt;
(NOTE: When upgraded from 2.0.6, We didn&amp;#39;t run mongod --upgrade since it&amp;#39;s not instructed in Changelog)</environment>
        <key id="49677">SERVER-6963</key>
            <summary>: -286331391 (0x01EEEEEE) first element: ^A: ?type=108</summary>
                <type id="1" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14703&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="9">Done</resolution>
                                        <assignee username="matulef">Kevin Matulef</assignee>
                                    <reporter username="somsak">Somsak Sriprayoonsakul</reporter>
                        <labels>
                    </labels>
                <created>Fri, 7 Sep 2012 06:08:16 +0000</created>
                <updated>Mon, 11 Jul 2016 17:57:04 +0000</updated>
                            <resolved>Fri, 28 Dec 2012 19:33:27 +0000</resolved>
                                    <version>2.2.0</version>
                                                                        <votes>0</votes>
                                    <watches>5</watches>
                                                                                                                <comments>
                            <comment id="226290" author="matulef" created="Fri, 28 Dec 2012 19:33:15 +0000"  >&lt;p&gt;Somsak, I&apos;m going to close out this ticket since we believe it&apos;s been fixed in 2.2.2. If you encounter the problem again though, please let us know. &lt;/p&gt;</comment>
                            <comment id="182431" author="matulef" created="Mon, 5 Nov 2012 12:09:52 +0000"  >&lt;p&gt;Hi Somsak, as Tad mentioned this seems to be caused by the same bug as &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-7206&quot; title=&quot;potential mongod crash in profiling, 2.2&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-7206&quot;&gt;&lt;del&gt;SERVER-7206&lt;/del&gt;&lt;/a&gt;.  We believe we&apos;ve identified the problem there and it should be fixed for 2.2.2. Once we check in a patch, it&apos;d be great if you can test out the nightly build to see if it fixes this issue. Stay tuned.  &lt;/p&gt;</comment>
                            <comment id="182414" author="tad" created="Mon, 5 Nov 2012 10:39:11 +0000"  >&lt;p&gt;This seems to be the same profiling crash as &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-7206&quot; title=&quot;potential mongod crash in profiling, 2.2&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-7206&quot;&gt;&lt;del&gt;SERVER-7206&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="182391" author="somsak" created="Mon, 5 Nov 2012 07:20:41 +0000"  >&lt;p&gt;The problem still persists, the system still crashed from time to time, so we decided to do full migrate (dump everything with mongoexport, redo everything and re-import the .json files)&lt;/p&gt;

&lt;p&gt;What we found is that, if we turned on profiling (profile = 2), even with single replication set without any sharding, MongoDb crashed with the same exception during import. Note that this is a very freshly created replication set with latest stable MongoDB 2.2.1 release.&lt;/p&gt;</comment>
                            <comment id="165999" author="somsak" created="Wed, 19 Sep 2012 15:00:48 +0000"  >&lt;p&gt;It seems that this problem might relate to query profiler.&lt;/p&gt;

&lt;p&gt;3-4 days ago, after we found out that system.profile was corrupted, we decided to stop query logging (setProfilingLevel(0, 5000)) on all databases. After that, the rate that problem arise greatly decreased. We only found the problem twice during these 3 days, and one of that occurred with &quot;local&quot; database. Another occurred on a rarely use database. We did the same, resync the whole database to fix it.&lt;/p&gt;

&lt;p&gt;Note that the problem will only occurred on PRIMARY. It never occurred on SECONDARY (not until it became PRIMARY).&lt;/p&gt;</comment>
                            <comment id="164691" author="somsak" created="Sat, 15 Sep 2012 03:59:06 +0000"  >&lt;p&gt;We found some other might-be-related error in the log file&lt;/p&gt;

&lt;p&gt;Sat Sep 15 07:33:23 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn6630&amp;#93;&lt;/span&gt; problem detected during query over obecaoc.system.profile : &lt;/p&gt;
{ $err: &quot;BSONElement: bad type -114&quot;, code: 10320 }

&lt;p&gt;There are quite a few error like above in our mongod.log. It didn&apos;t crashed our system though.&lt;/p&gt;
</comment>
                            <comment id="163840" author="somsak" created="Thu, 13 Sep 2012 09:40:10 +0000"  >&lt;p&gt;Could you suggest what we should do next?&lt;/p&gt;

&lt;p&gt;We still have no luck on reproducing the problem. The problem occurred from time to time but we don&apos;t sure what&apos;s the cause (This is a live system where client is a web-site). &lt;/p&gt;

&lt;p&gt;Right now we are waiting for the next round that the problem occur, this time we will keep the corrupted data file and see what we can do with it.&lt;/p&gt;</comment>
                            <comment id="163766" author="somsak" created="Thu, 13 Sep 2012 03:34:22 +0000"  >&lt;p&gt;Yesterday, for some reason, the bricked database appear to be &quot;repairable&quot;, so we decided to rolling-repair all mongod servers one by one.&lt;/p&gt;

&lt;p&gt;However, in this morning, one of mongod start spitting out the same exception again and crashed. We noticed that there are also type=24 exception around type=108 exceptions.&lt;/p&gt;

&lt;p&gt;We still trying to figure out how to reproduce the bug systemetically. Anyway it seems --repair could not solve our issue here.&lt;/p&gt;</comment>
                            <comment id="162971" author="somsak" created="Tue, 11 Sep 2012 14:46:01 +0000"  >&lt;p&gt;Sorry to mention, yes these servers experience quite a few hard shutdown (electricity problem). And we are running with journaling on.&lt;/p&gt;

&lt;p&gt;The problem just appeared today in one of a server. Starting the server with --repair flag yield the same error.&lt;/p&gt;

&lt;p&gt;Tue Sep 11 21:42:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; MongoDB starting : pid=30960 port=27017 dbpath=/data/mongo/mongo2 64-bit host=my.host.name&lt;br/&gt;
Tue Sep 11 21:42:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt;&lt;br/&gt;
Tue Sep 11 21:42:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; ** WARNING: You are running on a NUMA machine.&lt;br/&gt;
Tue Sep 11 21:42:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; **          We suggest launching mongod like this to avoid performance problems:&lt;br/&gt;
Tue Sep 11 21:42:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; **              numactl --interleave=all mongod &lt;span class=&quot;error&quot;&gt;&amp;#91;other options&amp;#93;&lt;/span&gt;&lt;br/&gt;
Tue Sep 11 21:42:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt;&lt;br/&gt;
Tue Sep 11 21:42:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; db version v2.2.0, pdfile version 4.5&lt;br/&gt;
Tue Sep 11 21:42:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; git version: f5e83eae9cfbec7fb7a071321928f00d1b0c5207&lt;br/&gt;
Tue Sep 11 21:42:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; build info: Linux ip-10-2-29-40 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_49&lt;br/&gt;
Tue Sep 11 21:42:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; options: &lt;/p&gt;
{ config: &quot;/etc/mongod.conf&quot;, dbpath: &quot;/data/mongo/mongo2&quot;, fork: &quot;true&quot;, logappend: &quot;true&quot;, logpath: &quot;/var/log/mongo/mongod.log&quot;, maxConns: 24000, profile: 2, repair: true, replSet: &quot;rs2&quot;, slowms: 500, syncdelay: 60.0 }
&lt;p&gt;Tue Sep 11 21:42:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; Assertion: 10334:Invalid BSONObj size: -286331391 (0x01EEEEEE) first element: ^A: ?type=-24&lt;br/&gt;
0xade6e1 0x8036eb 0x80386c 0x571bc7 0xadf73d 0x7474e4 0xa61af4 0x62dc57 0x62dc98 0x73954c 0x70f40f 0xb5db70 0xb5e963 0x6f698d 0xa90c3a 0xb506b6 0x55a4cd 0x55c6c8 0x55d2dd 0x563dbe&lt;br/&gt;
 /usr/bin/mongod(_ZN5mongo15printStackTraceERSo+0x21) &lt;span class=&quot;error&quot;&gt;&amp;#91;0xade6e1&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongod(_ZN5mongo11msgassertedEiPKc+0x9b) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x8036eb&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongod &lt;span class=&quot;error&quot;&gt;&amp;#91;0x80386c&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongod(_ZNK5mongo7BSONObj14_assertInvalidEv+0x497) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x571bc7&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongod(_ZN5mongo13unindexRecordEPNS_16NamespaceDetailsEPNS_6RecordERKNS_7DiskLocEb+0x11d) &lt;span class=&quot;error&quot;&gt;&amp;#91;0xadf73d&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongod(_ZN5mongo11DataFileMgr12deleteRecordEPKcPNS_6RecordERKNS_7DiskLocEbbb+0x204) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x7474e4&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongod(_ZN5mongo16NamespaceDetails11cappedAllocEPKci+0x4b4) &lt;span class=&quot;error&quot;&gt;&amp;#91;0xa61af4&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongod(_ZN5mongo16NamespaceDetails6_allocEPKci+0x27) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x62dc57&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongod(_ZN5mongo16NamespaceDetails5allocEPKciRNS_7DiskLocE+0x38) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x62dc98&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongod(_ZN5mongo11DataFileMgr17fast_oplog_insertEPNS_16NamespaceDetailsEPKci+0x6c) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x73954c&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongod(_ZN5mongo7profileERKNS_6ClientERNS_5CurOpE+0x95f) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x70f40f&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE+0xec0) &lt;span class=&quot;error&quot;&gt;&amp;#91;0xb5db70&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongod(_ZN5mongo14DBDirectClient4callERNS_7MessageES2_bPSs+0x93) &lt;span class=&quot;error&quot;&gt;&amp;#91;0xb5e963&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongod(_ZN5mongo14DBClientCursor4initEv+0xbd) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x6f698d&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongod(_ZN5mongo12DBClientBase5queryERKSsNS_5QueryEiiPKNS_7BSONObjEii+0xea) &lt;span class=&quot;error&quot;&gt;&amp;#91;0xa90c3a&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongod(_ZN5mongo14DBDirectClient5queryERKSsNS_5QueryEiiPKNS_7BSONObjEii+0x56) &lt;span class=&quot;error&quot;&gt;&amp;#91;0xb506b6&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongod(_ZN5mongo19clearTmpCollectionsEv+0x23d) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x55a4cd&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongod(_ZN5mongo14_initAndListenEi+0x458) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x55c6c8&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongod(_ZN5mongo13initAndListenEi+0x1d) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x55d2dd&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongod &lt;span class=&quot;error&quot;&gt;&amp;#91;0x563dbe&amp;#93;&lt;/span&gt;&lt;br/&gt;
Tue Sep 11 21:31:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; exception in initAndListen: 10334 Invalid BSONObj size: -286331391 (0x01EEEEEE) first element: : ?type=-24, terminating&lt;br/&gt;
Tue Sep 11 21:31:14 dbexit:&lt;br/&gt;
Tue Sep 11 21:31:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; shutdown: going to close listening sockets...&lt;br/&gt;
Tue Sep 11 21:31:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; shutdown: going to flush diaglog...&lt;br/&gt;
Tue Sep 11 21:31:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; shutdown: going to close sockets...&lt;br/&gt;
Tue Sep 11 21:31:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; shutdown: waiting for fs preallocator...&lt;br/&gt;
Tue Sep 11 21:31:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; shutdown: lock for final commit...&lt;br/&gt;
Tue Sep 11 21:31:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; shutdown: final commit...&lt;br/&gt;
Tue Sep 11 21:31:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; shutdown: closing all files...&lt;br/&gt;
Tue Sep 11 21:31:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; closeAllFiles() finished&lt;br/&gt;
Tue Sep 11 21:31:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; journalCleanup...&lt;br/&gt;
Tue Sep 11 21:31:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; removeJournalFiles&lt;br/&gt;
Tue Sep 11 21:31:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; shutdown: removing fs lock...&lt;br/&gt;
Tue Sep 11 21:31:14 dbexit: really exiting now&lt;/p&gt;</comment>
                            <comment id="162813" author="somsak" created="Tue, 11 Sep 2012 03:50:43 +0000"  >&lt;p&gt;You could be right. May be thes are 2 separated problems.&lt;/p&gt;

&lt;p&gt;About repairDatabase(), we did try starting mongod with --repair option but it still crash. We didn&apos;t keep the error log though (I think it crashed with the same error so we didn&apos;t bother keeping the log). Next time we will try again and keep the log.&lt;/p&gt;

&lt;p&gt;We are trying to reproduce this in a testbed system, that&apos;s why we found out that mongodump &amp;amp; restore is also not working. I will post it here again if we could find someway to reproduce the problem.&lt;/p&gt;

&lt;p&gt;You are right about metadata.json. If I removed the file the mongorestore command works (Sorry, we never thought that by specifying studentfamily.bson it will still looking for studentfamily.metadata.json). Could you tell us what&apos;s wrong with the metadata.json file?&lt;/p&gt;</comment>
                            <comment id="162755" author="matulef" created="Tue, 11 Sep 2012 00:37:04 +0000"  >&lt;p&gt;Hi Somsak,&lt;/p&gt;

&lt;p&gt;The &quot;invalid BSONObj size&quot; error you experienced earlier looks a lot like data corruption.  Did the old primary ever experience a hard shutdown?  I assume you are running with journaling on? &lt;/p&gt;

&lt;p&gt;Also, before you erased the old primary&apos;s data and resynced it, did you try running &quot;repairDatabase()&quot; or starting it up with the &quot;--repair&quot; option?  &lt;/p&gt;

&lt;p&gt;I&apos;ve looked at the dumps you&apos;ve given.  The assertion seems to be coming from the metadata.json files, rather than the data itself (mongorestore works for me if I use the &quot;studentfamily.bson&quot; file without the &quot;studentfamily.metadata.json&quot; file).  I expect that error is an issue with mongodump.  &lt;/p&gt;

&lt;p&gt;Best,&lt;br/&gt;
-Kevin&lt;/p&gt;</comment>
                            <comment id="162310" author="somsak" created="Mon, 10 Sep 2012 11:30:27 +0000"  >&lt;p&gt;We managed to find something. If we dump the data into json with mongoexport, the restored data would have different number of document in collection. &lt;/p&gt;

&lt;p&gt;So we map reduce to find which group of data is missing and found out a small set (66 documents) which may be the cause of this problem.&lt;/p&gt;

&lt;p&gt;Attached are the mongodump&apos;ed BSON of these data. Each contains only single document. When trying to restored with mongorestore it yielded the same assertion as commented above.&lt;/p&gt;</comment>
                            <comment id="162019" author="somsak" created="Sun, 9 Sep 2012 03:43:42 +0000"  >&lt;p&gt;We found that a collection might be the cause of this problem. When we dumped the collection with mongodump and tried to restore it on another stand-alone Mongod 2.2.0, montorestore crashed immediately.&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;root@sql1-dr obecaoc&amp;#93;&lt;/span&gt;# mongorestore -h localhost -d xxx -c studentfamily studentfamily.bson  --objcheck --verbose&lt;br/&gt;
Sun Sep  9 10:35:56 creating new connection to:localhost:27017&lt;br/&gt;
Sun Sep  9 10:35:56 BackgroundJob starting: ConnectBG&lt;br/&gt;
Sun Sep  9 10:35:56 connected connection!&lt;br/&gt;
connected to: localhost&lt;br/&gt;
Sun Sep  9 10:35:56 studentfamily.bson&lt;br/&gt;
Sun Sep  9 10:35:56     going into namespace &lt;span class=&quot;error&quot;&gt;&amp;#91;xxx.studentfamily&amp;#93;&lt;/span&gt;&lt;br/&gt;
Sun Sep  9 10:35:56   Assertion failure b.empty() src/mongo/db/json.cpp 645&lt;br/&gt;
0xad2211 0x67fced 0xa7daa5 0x56aa20 0x56db4a 0xb3b078 0xb41712 0x553f92 0x34e9c1ecdd 0x553e09 &lt;br/&gt;
 mongorestore(_ZN5mongo15printStackTraceERSo+0x21) &lt;span class=&quot;error&quot;&gt;&amp;#91;0xad2211&amp;#93;&lt;/span&gt;&lt;br/&gt;
 mongorestore(_ZN5mongo12verifyFailedEPKcS1_j+0xfd) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x67fced&amp;#93;&lt;/span&gt;&lt;br/&gt;
 mongorestore(_ZN5mongo8fromjsonEPKcPi+0x585) &lt;span class=&quot;error&quot;&gt;&amp;#91;0xa7daa5&amp;#93;&lt;/span&gt;&lt;br/&gt;
 mongorestore(_ZN7Restore9drillDownEN5boost11filesystem210basic_pathISsNS1_11path_traitsEEEbbb+0xff0) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x56aa20&amp;#93;&lt;/span&gt;&lt;br/&gt;
 mongorestore(_ZN7Restore5doRunEv+0xdda) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x56db4a&amp;#93;&lt;/span&gt;&lt;br/&gt;
 mongorestore(_ZN5mongo8BSONTool3runEv+0x448) &lt;span class=&quot;error&quot;&gt;&amp;#91;0xb3b078&amp;#93;&lt;/span&gt;&lt;br/&gt;
 mongorestore(_ZN5mongo4Tool4mainEiPPc+0x1712) &lt;span class=&quot;error&quot;&gt;&amp;#91;0xb41712&amp;#93;&lt;/span&gt;&lt;br/&gt;
 mongorestore(main+0x32) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x553f92&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /lib64/libc.so.6(__libc_start_main+0xfd) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x34e9c1ecdd&amp;#93;&lt;/span&gt;&lt;br/&gt;
 mongorestore(__gxx_personality_v0+0x421) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x553e09&amp;#93;&lt;/span&gt;&lt;br/&gt;
assertion: 0 assertion src/mongo/db/json.cpp:645&lt;/p&gt;

&lt;p&gt;Note that, exporting the collection into json (with mongoexport) and restore back yielded no problem. &lt;/p&gt;</comment>
                            <comment id="161537" author="somsak" created="Fri, 7 Sep 2012 06:57:43 +0000"  >&lt;p&gt;I forgot to mentioned one important thing. If this problem occurred, mongod will crash and it will never possible to start again (yielded the same error everytime it started). That&apos;s why we need to purge everything and re-replicate data.&lt;/p&gt;</comment>
                            <comment id="161533" author="somsak" created="Fri, 7 Sep 2012 06:39:34 +0000"  >&lt;p&gt;This java_exception.txt occurred in our web client. Might not related but I post it just in case.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="51924">SERVER-7206</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                                        </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="19826" name="faildata1.tar.gz" size="684" author="somsak" created="Mon, 10 Sep 2012 11:30:27 +0000"/>
                            <attachment id="19827" name="faildata2.tar.gz" size="699" author="somsak" created="Mon, 10 Sep 2012 11:30:27 +0000"/>
                            <attachment id="19775" name="java_exception.txt" size="7329" author="somsak" created="Fri, 7 Sep 2012 06:39:34 +0000"/>
                            <attachment id="19774" name="mongodb-dbm1.log.gz" size="19558560" author="somsak" created="Fri, 7 Sep 2012 06:08:16 +0000"/>
                            <attachment id="19773" name="mongodb-dbm2.log.gz" size="16366723" author="somsak" created="Fri, 7 Sep 2012 06:08:16 +0000"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>15.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Tue, 11 Sep 2012 00:37:04 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        11 years, 7 weeks, 5 days ago
    
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18254" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Dependencies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[]]></customfieldvalue>


                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10057" key="com.atlassian.jira.toolkit:lastusercommented">
                        <customfieldname>Last comment by Customer</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>true</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10056" key="com.atlassian.jira.toolkit:lastupdaterorcommenter">
                        <customfieldname>Last commenter</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>ramon.fernandez@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            11 years, 7 weeks, 5 days ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10000" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Old_Backport</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10000"><![CDATA[No]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10032" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Operating System</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10020"><![CDATA[Linux]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>matulef</customfieldvalue>
            <customfieldvalue>somsak</customfieldvalue>
            <customfieldvalue>tad</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hrnpl3:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hrguwn:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>11969</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_23361" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Requested By</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10053" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>Time In Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_22870" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Triagers</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_14350" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>serverRank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hrizdb:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>