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

sharding failed after restarting mongo

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical - P2 Critical - P2
    • None
    • 2.1.1
    • Sharding
    • None
    • db version v2.1.1-pre-, pdfile version 4.5
      git version: a2d6f752d56aa446220b9f14c8ad3865c2fb5db8
    • ALL

    Description

      Assertion: 15927:can't open database in a read lock. if db was just closed, consider retrying the query. might otherwise indicate an internal error

      To reproduce do next actions:
      0) mongo* running from mongodb:mongodb
      1) mkdir /mongo/db/path/moveChunk && chmod 700 /mongo/db/path/moveChunk && sudo chown root:root /mongo/db/path/moveChunk
      2) run sharding
      it will fail with the next message: ERROR: Uncaught std::exception: boost::filesystem::create_directory: Permission denied: "/mnt/ongo/db/moveChunk", terminating
      3) sudo chown mongodb:mongodb /mongo/db/path/moveChunk
      4) restart mongodb
      And now we have such messages in lock, that it can't open database
      5) If you run query to some of collections in this database (e.g. db.foo.findOne()), than this message disappear and migration is in progress

      Attachments

        Activity

          People

            randolph@mongodb.com Randolph Tan
            azat Azat Khuzhin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: