Details
-
Bug
-
Resolution: Cannot Reproduce
-
Critical - P2
-
None
-
2.6.3
-
None
-
ALL
Description
We have a 3 member replica set, and since upgrading to 2.6.3 a few weeks ago, at least two of the three members have experiencing this error on two separate occasions:
init: mongod main process (28391) killed by SEGV signal
|
A mongo restart fixes it.
The mongo logs simply show nothing between the time this error occurred the syslog, and the time we restarted mongo.
2014-07-22T06:56:37.343+0000 [initandlisten] connection accepted from 10.93.168.17:58455 #457833 (1073 connections now open)
|
2014-07-22T07:05:14.485+0000 ***** SERVER RESTARTED *****
|
2014-07-22T07:05:14.490+0000 [initandlisten] MongoDB starting : pid=20739 port=27017 dbpath=/data 64-bit host=mongo4
|
This has happenned too many times now. Can anyone help please or give me some ideas as to where to look for more data? thx