when analyzing the slow log: uncaught exception: error: { "$err" : "BSONElement: bad type 115", "code" : 10320 }

[Mark]

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

[Mark]

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?

[David Hows]

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