[SERVER-38101] Secondary Crashing with "aborting after fassert() failure" error Created: 13/Nov/18 Updated: 16/Nov/21 Resolved: 13/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sree Himakunthala | Assignee: | Kelsey Schubert |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | N/A |
||||||||
| Participants: | |||||||||
| Description |
|
I upgraded this test mongodb replica set from 3.4.x to 3.6.7 about 2 weeks back.
Today, i experienced a secondary mongod crashing with the following errors: Secondary Crashing with "aborting after fassert() failure" error Mongod Log extracts:
2018-11-12T17:16:13.664-0800 I NETWORK [thread28] Successfully connected to 10.10.190.6:27017 (49250 connections now open to xxx with a 0 second timeout) , os: { type: "Linux", name: "Linux 4.2.0-42-generic #49~14.04.1-Ubuntu SMP Wed Jun 29 20:22:11 UTC 2016", architecture: "x86_64", version: "4.2.0-42-generic" }, platform: ".NET Core 4.6.26328.01" } , lastUse: new Date(1542071829043) } } on: { ts: Timestamp(1542071829, 1), t: 27, h: -7111336552031876369, v: 2, op: "i", ns: "config.system.sessions", ui: UUID("6e46dffd-9a3c-496c-81b9-3a7cfa4f1ac6"), wall: new Date(1542071829042), o: { _id: { id: UUID("85cc8499-8b2c-4b4f-a871-5b4fc8358968"), uid: BinData(0, E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855) }, lastUse: new Date(1542071829043) } } , lastUse: new Date(1542071829043) } } at src/mongo/db/repl/sync_tail.cpp 1209 ***aborting after fassert() failure
I tried to restart and am getting the same error with the mongod crashing. Also, after the upgrade, i did modify the featureCompatibilityVersion to 3.6 { "_id" : "featureCompatibilityVersion", "version" : "3.6" } |
| Comments |
| Comment by Kelsey Schubert [ 13/Nov/18 ] |
|
Hi sreek95051, Thanks for your report. Would you please upgrade to latest version of MongoDB 3.6 to take advantage of Thank you, |