Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
mongodb-user
Home
+ new post
About this group
Join this group
when analyzing the slow log: uncaught exception: error: { "$err" : "BSONElement: bad type 115", "code" : 10320 }
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   3 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Mark  
View profile  
 More options Nov 9 2012, 2:59 pm
From: Mark <markandmo...@gmail.com>
Date: Fri, 9 Nov 2012 11:59:36 -0800 (PST)
Local: Fri, Nov 9 2012 2:59 pm
Subject: when analyzing the slow log: uncaught exception: error: { "$err" : "BSONElement: bad type 115", "code" : 10320 }
Print | Individual message | Show original | Report this message | Find messages by this author

Hello,

I was upgrading to mongo 2.2.1 on a system, and for some of the databases I
get a weird error analyzing the profile.
db.system.profile.find({ millis : { $gt : 1000 } })
This gives out an error sometimes:
uncaught exception: error: { "$err" : "BSONElement: bad type 115", "code" :
10320 }

Its consistent for certain databases.
Weird.
Is this limited to mongo 2.2.1?
I was wondering if I need to clean out the profiling after the upgrade.

Also, this works fine:
db.system.profile.find()
Its just when I search by millis does it go bad.
Mark


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Mark  
View profile  
 More options Nov 9 2012, 3:05 pm
From: Mark <markandmo...@gmail.com>
Date: Fri, 9 Nov 2012 12:05:32 -0800 (PST)
Local: Fri, Nov 9 2012 3:05 pm
Subject: Re: when analyzing the slow log: uncaught exception: error: { "$err" : "BSONElement: bad type 115", "code" : 10320 }
Print | Individual message | Show original | Report this message | Find messages by this author


I found a solution. Just wipe it out.
 db.setProfilingLevel(0); db.system.profile.drop(); db.setProfilingLevel(2);
I was wondering, why was it failing in the first place?

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
David Hows  
View profile  
 More options Nov 22 2012, 11:14 pm
From: David Hows <david.h...@10gen.com>
Date: Thu, 22 Nov 2012 20:14:52 -0800 (PST)
Local: Thurs, Nov 22 2012 11:14 pm
Subject: Re: when analyzing the slow log: uncaught exception: error: { "$err" : "BSONElement: bad type 115", "code" : 10320 }
Print | Individual message | Show original | Report this message | Find messages by this author

Mark,

Sounds like it may have profiled something which 2.2.1 could not read
correctly.

Diagnostic steps would have been to rollback to your last version, run the
query, get the results and run again under 2.2.1 to find the specific
object which caused the error.

Cheers,

David


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google