Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-41784

file:WiredTiger.wt, WT_SESSION.checkpoint: E:\Database10\mongo\data\db\WiredTiger.turtle.set to E:\Database10\mongo\data\db\WiredTiger.turtle: file-rename: MoveFileExW: Access is denied.

    XMLWordPrintableJSON

Details

    • Icon: Question Question
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • 3.2.18
    • None
    • None
    • Production

    Description

      We are using Mongo version 3.2.18-3-g53adeef and it is a replica set of 3 servers.

      Mongo version is : 3.2.18-3-g53adeef

      At times, mongo dB errors out with the below issue.. This is bring down the entire cluster i.e. all the three servers are becoming unresponsive.

       

      2019-06-13T11:42:13.431+0200 E STORAGE  [thread2] WiredTiger (0) [1560418933:431135][1912:140719557709952], file:WiredTiger.wt, WT_SESSION.checkpoint: E:\Database10\mongo\data\db\WiredTiger.turtle.set to E:\Database10\mongo\data\db\WiredTiger.turtle: file-rename: MoveFileExW: Access is denied.

       

      2019-06-13T11:42:13.432+0200 E STORAGE  [thread2] WiredTiger (0) [1560418933:432132][1912:140719557709952], file:WiredTiger.wt, WT_SESSION.checkpoint: WiredTiger.turtle: encountered an illegal file format or internal value

      2019-06-13T11:42:13.432+0200 E STORAGE  [thread2] WiredTiger (-31804) [1560418933:432132][1912:140719557709952], file:WiredTiger.wt, WT_SESSION.checkpoint: the process must exit and restart: WT_PANIC: WiredTiger library panic

      2019-06-13T11:42:13.433+0200 I -        [conn159429] Fatal Assertion 28559

      2019-06-13T11:42:13.433+0200 I -        [conn159515] Fatal Assertion 28559

      2019-06-13T11:42:13.433+0200 I -        [conn159429]

       

      ***aborting after fassert() failure

       

       

      2019-06-13T11:42:13.433+0200 I -        [conn159515]

       

      ***aborting after fassert() failure

       

       

      2019-06-13T11:42:13.433+0200 I -        [conn159578] Fatal Assertion 28559

      2019-06-13T11:42:13.433+0200 I -        [conn159653] Fatal Assertion 28559

      2019-06-13T11:42:13.433+0200 I -        [conn159578]

       

      ***aborting after fassert() failure

       

      Issue gets fixed after restarting the servers and then the mongo db is up and running. Can you please help us here?

       

      Thanks!

      Naresh Gudla

      Attachments

        Activity

          People

            daniel.hatcher@mongodb.com Danny Hatcher (Inactive)
            nareshg635 naresh gudla
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: