-
Type:
Bug
-
Resolution: Incomplete
-
Priority:
Critical - P2
-
None
-
Affects Version/s: 2.4.1
-
Component/s: Stability
-
None
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
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).