[SERVER-16249] mongodb 2.4.1 crashed after segfault Created: 20/Nov/14  Updated: 21/Nov/14  Resolved: 21/Nov/14

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

Type: Bug Priority: Critical - P2
Reporter: Hans Emmanuel Assignee: Ramon Fernandez Marina
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

In a year its third our mongodb crashes after segfault. This is the log at the time of crash .

Thu Nov 20 11:05:08.095 [initandlisten] connection accepted from 192.4.4.12:58648 #266335 (18 connections now open)
Thu Nov 20 11:05:08.095 [initandlisten] connection accepted from 192.4.4.12:58649 #266336 (19 connections now open)
Thu Nov 20 11:05:08.099 Invalid access at address: 0x7f3146f4dff0 from thread: conn266335
 
Thu Nov 20 11:05:08.099 Got signal: 11 (Segmentation fault).
 
Thu Nov 20 11:05:08.107 Invalid access at address: 0x7f3147a7fff0 from thread: conn266336
 
Thu Nov 20 11:05:08.107 Got signal: 11 (Segmentation fault).
 
Thu Nov 20 11:05:08.108 [initandlisten] connection accepted from 192.4.4.12:58652 #266337 (20 connections now open)
Thu Nov 20 11:05:08.109 Invalid access at address: 0x7f3137ec3ff0 from thread: conn266337
 
Thu Nov 20 11:05:08.109 Got signal: 11 (Segmentation fault).
 
Thu Nov 20 11:05:08.119 [initandlisten] connection accepted from 192.4.4.12:58655 #266338 (21 connections now open)
Thu Nov 20 11:05:08.120 Invalid access at address: 0x7f4c48c9aff0 from thread: conn266338
 
Thu Nov 20 11:05:08.120 Got signal: 11 (Segmentation fault).
 
Thu Nov 20 11:05:08.122 [initandlisten] connection accepted from 192.4.4.12:58657 #266339 (22 connections now open)
Thu Nov 20 11:05:08.125 Invalid access at address: 0x7f314797eff0 from thread: conn266339
 
Thu Nov 20 11:05:08.125 Got signal: 11 (Segmentation fault).



 Comments   
Comment by Ramon Fernandez Marina [ 21/Nov/14 ]

Understood, thanks for letting us know hansemmanuel. Opening new tickets is indeed the way to go if you run into any issues with 2.4.12.

Comment by Hans Emmanuel [ 21/Nov/14 ]

Hi Ramon , Thanks for your quick responce. We have decided to upgrade to 2.4.12 and will open new case if we still face issues. Thanks.

Comment by Ramon Fernandez Marina [ 20/Nov/14 ]

hansemmanuel, can you please upload the full logs? I'm looking for at least a stack trace that may gives us more information, as the log lines above are not sufficient to investigate the cause of the issue.

Note also that 2.4.1 is very old at this stage and there have been numerous bug fixes and improvements to MongoDB since, so I'd recommend you upgrade at least to the latest version in the 2.4 series (2.4.12 right now).

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