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

Upstart configuration fails to start server if other instances are running

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: 2.4.4
    • Fix Version/s: 2.7.3
    • Component/s: Packaging
    • Environment:
      Ubuntu 12.04
    • Operating System:
      Linux
    • Steps To Reproduce:
      Hide

      1. Install Mongo from the 10gen apt repository.
      2. Run mongod in a shell, perhaps with different configuration, port bindings, etc.
      3. Run "/sbin/start mongodb"

      Expected behaviour:

      • starts MongoDB and outputs something like mongodb start/running, process 12345

      Actual behaviour:

      • refuses to start MongoDB due to second running instance, and prints mongodb stop/waiting
      Show
      1. Install Mongo from the 10gen apt repository. 2. Run mongod in a shell, perhaps with different configuration, port bindings, etc. 3. Run "/sbin/start mongodb" Expected behaviour: starts MongoDB and outputs something like mongodb start/running, process 12345 Actual behaviour: refuses to start MongoDB due to second running instance, and prints mongodb stop/waiting
    • Sprint:
      Server 2.7.3

      Description

      The upstart configuration installed by the mongodb-10gen package from http://downloads-distro.mongodb.org/repo/ubuntu-upstart uses start-stop-daemon(8) to control the spawn of /usr/bin/mongod. It currently doesn't use a pidfile to track the lifecycle of the process, and thus falls back to the default behaviour of scanning the process table for an extant instance of a mongod process.

      This means that when, for example, mongod is running inside an LXC container on the host, the upstart script will fail to start MongoDB.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              ernie.hershey Ernie Hershey
              Reporter:
              nick.stenning@digital.cabinet-office.gov.uk Nick Stenning
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: