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

mongos failed on error - Failed to mlock: Unknown error

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Works as Designed
    • Affects Version/s: 4.0.1
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Operating System:
      ALL

      Description

      I installed mongodb in sharding, but the mongos process was down suddenly not long after the start. There's error in the log file:

      2018-08-11T22:11:18.010+0800 I NETWORK [listener] connection accepted from
      2018-08-11T22:11:18.011+0800 I NETWORK [listener] connection accepted from 111.199.184.231:25765 #1609 (1539 connections now open)
      2018-08-11T22:11:18.037+0800 F - [conn1275] Failed to mlock: Unknown error
      2018-08-11T22:11:18.037+0800 F - [conn1275] Fatal Assertion 28832 at src/mongo/base/secure_allocator.cpp 246
      2018-08-11T22:11:18.038+0800 F - [conn1275]

      ***aborting after fassert() failure

      2018-08-11T22:11:18.051+0800 F - [conn1275] Got signal: 6 (Aborted).
      0x561133b129b1 0x561133b11bc9 0x561133b120ad 0x7fe63b7ac5e0 0x7fe63b40f1f7 0x7fe63b4108e8 0x561132ef0e3f 0x561133aa6ca7 0x5611335b7559 0x5611335b83c8 0x5611332a9b50 0x5611332ab7d0 0x5611334e6789 0x56113303e4c0 0x56113303f927 0x561132f43b77 0x561132f6126a 0x561132f5bf27 0x561132f5f731 0x5611333ba7b2 0x561132f5a13f 0x561132f5d2d5 0x561132f5b667 0x561132f5bfad 0x561132f5f731 0x5611333bad15 0x561133a8dc44 0x7fe63b7a4e25 0x7fe63b4d234d

      ...

        Attachments

          Activity

            People

            Assignee:
            dmitry.agranat Dmitry Agranat
            Reporter:
            sword2000 jiancai.hao
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: