[SERVER-3907] Broken pipe of HTTP client lets mongod crash (Segmentation fault) Created: 20/Sep/11  Updated: 11/Jul/16  Resolved: 23/Sep/11

Status: Closed
Project: Core Server
Component/s: HTTP Console
Affects Version/s: 2.0.0
Fix Version/s: 2.0.1, 2.1.0

Type: Bug Priority: Critical - P2
Reporter: Benedikt Waldvogel Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File main.log     File main2.log    
Issue Links:
Depends
Duplicate
is duplicated by SERVER-3845 Process aborted on initial sync when ... Closed
Operating System: Linux
Participants:

 Description   

mongod suddenly crashed with a segmentation fault while a client (Firefox 6.0.2) was using the web console:
http://mongo1:28017/_replSetOplog?_id=0

See the attached logfile of the mongod.



 Comments   
Comment by auto [ 23/Sep/11 ]

Author:

{u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: try/catch around send in mini webserver SERVER-3907
Branch: v2.0
https://github.com/mongodb/mongo/commit/fad753ee002eb823426fa6d315e688364ed60a39

Comment by auto [ 23/Sep/11 ]

Author:

{u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: try/catch around send in mini webserver SERVER-3907
Branch: master
https://github.com/mongodb/mongo/commit/3c712b18936a7d3e2f74e7bb9c8d6cbbe076ba10

Comment by Benedikt Waldvogel [ 20/Sep/11 ]

One more note: It’s actually not a broken pipe of the HTTP Client (like Firefox) that causes the crash. It’s the mere call of the oplog page while having a lots of $unset field updates.

Comment by Benedikt Waldvogel [ 20/Sep/11 ]

I can even reproduce the crash. See the logfile of the 2nd crash.

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