mongod.pid is not removed when calling db.shutdownServer(), preventing subsequent init.d start

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Admin, Packaging
    • Server Development Platform
    • Build 2016-11-21
    • 5
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We're running mongod as an init.d service (Amazon linux), v.3.2.10 -
      no matter how we stop mongod (shutdownServer or "service stop") - on the next start we get:

      Error starting mongod. /var/run/mongodb/mongod.pid exists.

      We then rm the pid file and start, but this is very annoying.
      This did not happen in 3.2.1. Please advise on init.d changes we can apply to fix this.

              Assignee:
              [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
              Reporter:
              Yoni Douek
              Votes:
              1 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: