[SERVER-10847] Segmentation Fault - TTLMonitor Created: 23/Sep/13  Updated: 11/Jul/16  Resolved: 21/Oct/13

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

Type: Bug Priority: Major - P3
Reporter: Matthieu Lelard-Blayac Assignee: Unassigned
Resolution: Done Votes: 0
Labels: crash
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

SmartOS


Issue Links:
Related
is related to SERVER-8795 remapPrivateView: Solaris mmap() is n... Closed
Operating System: Solaris
Participants:

 Description   

MongoDB crashes from time to time, see logs below.

Versions & platform

[root@mongodb /opt/local/bin]# uname -a
SunOS mongodb 5.11 joyent_20130419T073558Z i86pc i386 i86pc Solaris

[root@mongodb /opt/local/bin]# pkgin list | grep mongo
mongodb-2.2.2nb1 NOSQL distributed document-oriented database

Thu Sep 5 08:52:14 Invalid access at address: 0xfffffd7c210280b0 from thread: TTLMonitor

Thu Sep 5 08:52:14 Got signal: 11 (Segmentation Fault).

Thu Sep 5 08:52:14 Backtrace:
0xb331b8 0x7bd48b 0x7bd695 0xfffffd7fff1bd0d6 0xfffffd7fff1aff2b 0x9ff980 0x873f13 0x873fcb 0x975e69 0xa6990d 0xa6a1bf 0xb04fbe 0xb0672f 0xfffffd7ffce1364c 0xfffffd7fff1bccfa 0xfffffd7fff1bd010
/opt/local/bin/mongod'_ZN5mongo15printStackTraceERSo+0x28 [0xb331b8]
/opt/local/bin/mongod'_ZN5mongo10abruptQuitEi+0x11b [0x7bd48b]
/opt/local/bin/mongod'_ZN5mongo24abruptQuitWithAddrSignalEiP7siginfoPv+0x125 [0x7bd695]
/lib/amd64/libc.so.1'__sighndlr+0x6 [0xfffffd7fff1bd0d6]
/lib/amd64/libc.so.1'call_user_handler+0x1db [0xfffffd7fff1aff2b]
/opt/local/bin/mongod'_ZNK5mongo6Record5touchEb+0x0 [0x9ff980]
/opt/local/bin/mongod'_ZN5mongo12ClientCursor5yieldEiPNS_6RecordE+0x63 [0x873f13]
/opt/local/bin/mongod'_ZN5mongo12ClientCursor14yieldSometimesENS0_11RecordNeedsEPb+0x6b [0x873fcb]
/opt/local/bin/mongod'_ZN5mongo13deleteObjectsEPKcNS_7BSONObjEbbbPNS_11RemoveSaverE+0x6c9 [0x975e69]
/opt/local/bin/mongod'_ZN5mongo10TTLMonitor10doTTLForDBERKSs+0x16fd [0xa6990d]
/opt/local/bin/mongod'_ZN5mongo10TTLMonitor3runEv+0x1df [0xa6a1bf]
/opt/local/bin/mongod'_ZN5mongo13BackgroundJob7jobBodyEN5boost10shared_ptrINS0_9JobStatusEEE+0xbe [0xb04fbe]
/opt/local/bin/mongod'_ZN5boost6detail11thread_dataINS_3_bi6bind_tIvNS_4_mfi3mf1IvN5mongo13BackgroundJobENS_10shared_ptrINS7_9JobStatusEEEEENS2_5list2INS2_5valueIPS7_EENSD_ISA_EEEEEEE3runEv+0x7f [0xb0672f]
/opt/local/lib/libboost_thread.so.1.49.0'thread_proxy+0x6c [0xfffffd7ffce1364c]
/lib/amd64/libc.so.1'_thrp_setup+0x8a [0xfffffd7fff1bccfa]
/lib/amd64/libc.so.1'_lwp_start+0x0 [0xfffffd7fff1bd010]



 Comments   
Comment by Matthieu Lelard-Blayac [ 21/Oct/13 ]

Hi David,

Sorry for late answer - we upgraded to v.2.4.6 a month ago and have not faced the issue since, so this seems to indeed be SERVER-8795

Thanks for the support.

Regards,
Matthieu

Comment by David Hows [ 21/Oct/13 ]

Hi Matthieu,

I'm marking this issue as closed as we have not heard back from you.

If there is further we can do for you on this issue please feel free to re-open it with details.

Regards,
David

Comment by Tad Marshall [ 24/Sep/13 ]

Hi Matthieu,

This is probably SERVER-8795, which is fixed in version 2.4.6.

Can you try that version and see if you still see the problem?

Tad

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