[SERVER-20324] Assertion failure isABSONObj() src/mongo/bson/bsonelement.cpp 409 Created: 09/Sep/15  Updated: 10/Oct/15  Resolved: 10/Oct/15

Status: Closed
Project: Core Server
Component/s: Stability
Affects Version/s: 3.0.4
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Marcin Matyaszczyk Assignee: Ramon Fernandez Marina
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Debian 7.9


Attachments: Text File mongocrash.txt     File mongod.log.2015-09-09T01-43-01.gz    
Operating System: Linux
Participants:

 Description   

Since upgrade to 3.0 we see strange problems with mongod server. It happens once every few days. The strange thing is that when it happens we cannot connect from one host to mongod but another host has no problems. Yesterday during this situation we saw mongod crash during query from local console. Query which normally takes milliseconds was interrupted with ctrl-c and error from attachment has occured. We don't see any errors in mongod log. Our setup is replica set with 3 nodes (primary, secondary, arbiter). Can you tell me what you need to analize this problem?



 Comments   
Comment by Ramon Fernandez Marina [ 10/Oct/15 ]

matya, the server logs you uploaded show that the server does not crash, but is just reporting there was a socket exception while servicing this request:

2015-09-08T11:05:46.791+0000 I QUERY    [conn2207804] query base5.webhook_send query: { uid: "07363ead312dc7f1a9185e9ca484236b", event_type: "ok" } planSummary: IXSCAN { uid: 1.0, event_type: 1.0 } ntoreturn:0 ntoskip:0 nscanned:1 nscannedObjects:1 keyUpdates:0 writeConflicts:0 numYields:1 nreturned:1 reslen:405 locks:{ Global: { acquireCount: { r: 4 } }, Database: { acquireCount: { r: 2 } }, Collection: { acquireCount: { r: 2 } } } 29915ms
2015-09-08T11:05:46.791+0000 I NETWORK  [conn2207804] SocketException handling request, closing client connection: 9001 socket exception [SEND_ERROR] server [127.0.0.1:48655]

The most likely cause for this behavior is a transient network error.

Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group. See also our Technical Support page for additional support resources.

Regards,
Ramón.

Comment by Marcin Matyaszczyk [ 09/Sep/15 ]

logs uploaded

Comment by Ramon Fernandez Marina [ 09/Sep/15 ]

matya, the stack trace looks like coming from the shell, not from the server. Can you please upload logs for the mongod process that you say crashed at the time of the crash?

Thanks,
Ramón.

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