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

Errors in configuration file leads to server crashing with no info in log

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Incomplete
    • Icon: Major - P3 Major - P3
    • None
    • 2.4.9, 3.0.4
    • Admin
    • None
    • ALL
    • Hide

      Add this to the configuration file:
      storage.smallFiles=true
      then restart the server.

      Show
      Add this to the configuration file: storage.smallFiles=true then restart the server.

    Description

      After editing the configuration file (and unintentionally adding some errors), I have restarted the service with:
      sudo service mongodb restart
      This results in the following message to the console:
      mongodb stop/waiting
      mongodb start/running, process XXXX
      However, ps aux | grep mongo reports no mongo server running, and nothing it is written to the log.

      If the server crashes due to a badly written configuration file, it should write to the log the cause and, even better, the lines in the configuration file that led to errors.

      OS: Ubuntu 14.04, also on CentOS 7

      Attachments

        Activity

          People

            sam.kleinman Sam Kleinman (Inactive)
            rflorian Valentin Florian
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: