[SERVER-6441] Assertion failure in bsonobjbuilder.h Created: 13/Jul/12  Updated: 11/Jul/16  Resolved: 18/Jul/12

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 2.2.0-rc0

Type: Bug Priority: Minor - P4
Reporter: Ian Whalen (Inactive) Assignee: Greg Studer
Resolution: Done Votes: 0
Labels: buildbot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-6894 RunOnAllShardsCommand() can receive a... Closed
is duplicated by SERVER-6745 Unhandled empty result in RunOnAllSha... Closed
Operating System: ALL
Participants:

 Description   

 m30999| Fri Jul 13 09:36:06 [conn1]   Assertion failure !e.eoo() src/mongo/s/../util/net/../../db/../bson/bsonobjbuilder.h 131
 m30999| Fri Jul 13 09:36:06 [conn1] ERROR: Future::spawnComand (part 2) exception:  :: caused by :: Error running command on server: localhost:30001
 m30999|  0   mongos                              0x000000010001447b _ZN5mongo15printStackTraceERSo + 43
 m30999|  1   mongos                              0x0000000100018919 _ZN5mongo12verifyFailedEPKcS1_j + 313
 m30999|  2   mongos                              0x00000001002ce55d _ZN5mongo15dbgrid_pub_cmds21RunOnAllShardsCommand3runERKSsRNS_7BSONObjEiRSsRNS_14BSONObjBuilderEb + 3389
 m30999|  3   mongos                              0x00000001002bbb0c _ZN5mongo7Command20runAgainstRegisteredEPKcRNS_7BSONObjERNS_14BSONObjBuilderEi + 1916
 m30999| 0x10001447b 0x100018919 0x1002ce55d 0x1002bbb0c 0x100420bf0 0x100233607 0x1002fd5fa 0x10003aecd 0x100050e2c 0x1002e9d93 0x7fff8a34efd6 0x7fff8a34ee89 
 m30999|  4   mongos                              0x0000000100420bf0 _ZN5mongo14SingleStrategy7queryOpERNS_7RequestE + 1376
 m30999|  5   mongos                              0x0000000100233607 _ZN5mongo13ShardStrategy7queryOpERNS_7RequestE + 2407
 m30999|  6   mongos                              0x00000001002fd5fa _ZN5mongo7Request7processEi + 474
 m30999|  7   mongos                              0x000000010003aecd _ZN5mongo21ShardedMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE + 109
 m30999|  8   mongos                              0x0000000100050e2c _ZN5mongo3pms9threadRunEPNS_13MessagingPortE + 1084
 m30999|  10  libSystem.B.dylib                   0x00007fff8a34efd6 _pthread_start + 331
 m30999|  9   mongos                              0x00000001002e9d93 thread_proxy + 163
 m30999|  11  libSystem.B.dylib                   0x00007fff8a34ee89 thread_start + 13

http://buildlogs.mongodb.org/build/5000223ed2a60f586800020b/test/5000223fd2a60f4d1b0003c5/



 Comments   
Comment by Ben Becker [ 30/Aug/12 ]

For easier JIRA searching, this issue is in RunOnAllShardsCommand.

Comment by auto [ 18/Jul/12 ]

Author:

{u'date': u'2012-07-13T09:56:03-07:00', u'email': u'greg@10gen.com', u'name': u'Greg Studer'}

Message: SERVER-6441 always check the output of runonallshards commands in case of empty response
Branch: master
https://github.com/mongodb/mongo/commit/c7d18420fbd1c718e545dcacbaf457537d4ca823

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