[SERVER-4416] Assertion failure !loc.isNull() db/pdfile.cpp 1881 Created: 02/Dec/11 Updated: 17/Sep/12 Resolved: 04/Dec/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code, Stability |
| Affects Version/s: | 2.0.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | György Nagy | Assignee: | Aaron Staple |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | assertion, server | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Build info: Linux bs-linux64.10gen.cc 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_41 |
||
| Issue Links: |
|
||||||||||||
| Operating System: | Linux | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
We have a server with mongodb and apache2. Yesterday started to log these assertations that mainly occurs when in rockmongo i want to get the one of the db's collections, but i see in the log files that its occurs on 'normal' connections. Fri Dec 2 08:44:07 [conn1631] authenticate: { authenticate: 1, user: "--", nonce: "--", key: "--" }Fri Dec 2 08:44:08 [conn1631] authenticate: { authenticate: 1, user: "--", nonce: "--", key: "--" }Fri Dec 2 08:44:08 [conn1631] command local.$cmd command: { $eval: CodeWScope( function () { return db.getCollectionNames(); }, {}), args: {} } ntoreturn:1 reslen:50 16msFri Dec 2 08:44:08 [conn1631] profile: warning ns local.system.profile does not exist Fri Dec 2 08:44:08 [conn1631] command admin.$cmd command: { $eval: CodeWScope( function (){ return db.getCollectionNames(); } , {}), args: {} } ntoreturn:1 reslen:92 15ms , {}), args: {} } ntoreturn:1 reslen:864 16ms . Fri Dec 2 08:52:30 [conn1611] authenticate: { authenticate: 1, user: "--", nonce: "--", key: "--" }Fri Dec 2 08:52:33 [conn1611] authenticate: { authenticate: 1, user: "--", nonce: "--", key: "--" }Fri Dec 2 08:52:33 [conn1611] command tuner_db.$cmd command: { authenticate: 1, user: "--", nonce: "--", key: "--" } ntoreturn:1 reslen:37 17ms The differencies in mongodb.conf are the followings: Its a single mongodb instance, no relicas or sharding. |
| Comments |
| Comment by György Nagy [ 05/Dec/11 ] |
|
Thank you. |
| Comment by Aaron Staple [ 04/Dec/11 ] |
|
Yep, this is happening because system.profile is not capped. I've filed |
| Comment by György Nagy [ 04/Dec/11 ] |
|
"Can you provide more information on one of the operations that triggered this failure" The db.system.profile.stats() output: , ""couldn't make room for new record" ..." |
| Comment by Aaron Staple [ 03/Dec/11 ] |
|
Hi György, Can you provide more information on one of the operations that triggered this failure, and also run db.system.profile.stats() and send us the output? Also, can you look back in your logs and see if there are any messages like this: "couldn't make room for new record" ... Thanks, |
| Comment by György Nagy [ 02/Dec/11 ] |
|
After turned profiling off, no assertation occured. |
| Comment by György Nagy [ 02/Dec/11 ] |
|
One of the assert that occured on an insert: Thu Dec 1 09:51:13 [conn737] authenticate: { authenticate: 1, user: "--", nonce: "--", key: "--" }Thu Dec 1 09:51:13 [conn737] insert tuner_db.friend_action 68ms |