mongo - v2.6 error

[mongodb-user] mongod shutdown itself unexpectedly after upgrade to version 2.6

 

	Tma995
	Apr 10, 2014 at 4:58 pm

Hi all,

We have upgrade mongodb to version 2.6 yesterday afternoon. Unfortunately
it shut down unexpectedly early this morning with below logs:

2014-04-10T02:45:04.086+0800 [conn952] SEVERE: Got signal: 6 (Aborted).
Backtrace:0x11bd301 0x11bc6de 0x3355832960 0x33558328e5 0x33558340c5
0x335582ba0e 0x335582bad0 0xac7944 0xaca025 0xaa6f8f 0xaa082c 0xaaaa81
0xac3661 0xd44534 0xd44f89 0xd47b8a 0xd4acf8 0xb96382 0xb98962 0x76b76f
  ./mongod(_ZN5mongo15printStackTraceERSo+0x21) [0x11bd301]
  ./mongod() [0x11bc6de]
  /lib64/libc.so.6() [0x3355832960]
  /lib64/libc.so.6(gsignal+0x35) [0x33558328e5]
  /lib64/libc.so.6(abort+0x175) [0x33558340c5]
  /lib64/libc.so.6() [0x335582ba0e]
  /lib64/libc.so.6(__assert_perror_fail+0) [0x335582bad0]
  ./mongod(_ZN5mongo9SortStage11addToBufferERKNS0_16SortableDataItemE+0x454)
[0xac7944]
  ./mongod(_ZN5mongo9SortStage4workEPm+0x865) [0xaca025]
  ./mongod(_ZN5mongo7OrStage4workEPm+0x12f) [0xaa6f8f]
  ./mongod(_ZN5mongo18KeepMutationsStage4workEPm+0x3c) [0xaa082c]
  ./mongod(_ZN5mongo15ProjectionStage4workEPm+0x51) [0xaaaa81]
  ./mongod(_ZN5mongo9SkipStage4workEPm+0x61) [0xac3661]
  ./mongod(_ZN5mongo15MultiPlanRunner12workAllPlansEPNS_7BSONObjE+0x1b4)
[0xd44534]
  ./mongod(_ZN5mongo15MultiPlanRunner12pickBestPlanEPmPNS_7BSONObjE+0xa9)
[0xd44f89]
  ./mongod(_ZN5mongo15MultiPlanRunner7getNextEPNS_7BSONObjEPNS_7DiskLocE+0x3fa)
[0xd47b8a]
  ./mongod(_ZN5mongo11newRunQueryERNS_7MessageERNS_12QueryMessageERNS_5CurOpES1_+0x958)
[0xd4acf8]
  ./mongod() [0xb96382]
  ./mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE+0x442)
[0xb98962]
  ./mongod(_ZN5mongo16MyMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE+0x9f)
[0x76b76f]

Please help.
Thanks.

TMA
- Show quoted text -

reply

Search Discussions

 

 All Groups  MongoDB  mongodb-user

2 responses

NestedOldest

• Charlie Page

  at Apr 11, 2014 at 12:34 am

  ⇧

  This looks like it is probably related to SERVER-13516, which is scheduled
  be fixed in 2.6.1. This appears to be the query running checking all
  plans. Would you share a sample document and the query?
  - Show quoted text -

  reply | permalink

• Jason Rassi

  at Apr 11, 2014 at 2:34 am

  ⇧

  Charlie: no, this is unrelated to SERVER-13516; it's an issue with the
  query sort stage.
  
  TMA: I see you also filed a ticket at
  <https://jira.mongodb.org/browse/SERVER-13537>, thank you! Please reply on
  that ticket when you are next able to.
  - Show quoted text -

  reply | permalink

Related Discussions

• [mongodb-user] Upgrading mongodb from 2.4.10 to 2.6
• [mongodb-user] upgrade to 2.6 caused rapid increase of non-mapped virtual memory
• [mongodb-user] [Balancer] Assertion: 13110:HostAndPort: host is empty
• [mongodb-user] How to choose the mongodb driver correctly when upgrade the mongodb?
• [mongodb-user] latest git: building mongoclient as dll with def-file on windows
• [mongodb-user] Unable to run mongos with --upgrade
• [mongodb-user] Version 1.8.3 of the C#/.NET driver is now available.
• [mongodb-user] PyMongo 2.6.1 Released
• [mongodb-user] Best practices to upgrade production cluster without downtime
• [mongodb-user] Mongos upgrade failed. Errmsg: "unauthorized"

source - http://grokbase.com/t/gg/mongodb-user/144avedxjz/mongod-shutdown-itself-unexpectedly-after-upgrade-to-version-2-6