MongoDB Service doesn't start (Error 1067); Stored data for our application not accessible

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.0.7
    • Component/s: Storage
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Dear Support-Team,

      due to an software update for our data historian and visualisation application, we faced the problem that the installation process crashed and the update gone wrong. Since then we are unable to access the stored data and also can't write new data into database (of course because the service isn't running).
      I think we may restarted the server not properly (which also holds the MongoDB service) and so the mongod.lock file remained NOT empty.
      Deleting it didn't solve the problem.

      What can be done to get the MongoDB service running again?

      Attached please find all WiredTiger.* files such as sizeStorer.wt and *.lock files.

      Thanks in advance!

      Yours hopefully,

      Clemens Schadner
      cts GmbH

        1. for Mongo Support.rar
          90 kB
        2. logs complete.rar
          37.30 MB
        3. SERVER-30165-repair.tar.gz
          67 kB

            Assignee:
            Mark Agarunov (Inactive)
            Reporter:
            Clemens Schadner [X]
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: