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

Duplicate (but identical) option in config file causes server to fail to start with no clue as to why

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 1.8.0
    • Component/s: Admin
    • None
    • Environment:
      Ubuntu 10.10 AMD64 10gen stable build
    • ALL

      Due to a bug in a shell script that tries to ensure journalling is on (I wish you had made that the default for the packaged builds) I ended up with the option twice. Ie my /etc/mongodb.conf ended with

      journal = true
      journal = true

      If you try to start the server "service mongodb start" then it will say started successfully and give a pid. However a ps will show no process. There is also absolutely nothing in /var/log/mongodb/mongodb.log or in any other logfile in /var/log.

      Trying to find out why the server didn't start was rather difficult.

            Assignee:
            Unassigned Unassigned
            Reporter:
            rogerbinns Roger Binns
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: