After installing MongoDB 3.2 it will not start, so checking status I get:
# systemctl status mongodb -l ● mongodb.service - SYSV: Mongo is a scalable, document-oriented database. Loaded: loaded (/etc/rc.d/init.d/mongodb) Active: failed (Result: exit-code) since Tue 2016-06-14 09:05:33 EDT; 8min ago Docs: man:systemd-sysv-generator(8) Process: 17722 ExecStop=/etc/rc.d/init.d/mongodb stop (code=exited, status=0/SUCCESS) Process: 17736 ExecStart=/etc/rc.d/init.d/mongodb start (code=exited, status=1/FAILURE) Jun 14 09:05:33 mdb32-rh7-s1-c1 systemd[1]: Starting SYSV: Mongo is a scalable, document-oriented database.... Jun 14 09:05:33 mdb32-rh7-s1-c1 runuser[17740]: pam_unix(runuser:session): session opened for user mongod by (uid=0) Jun 14 09:05:33 mdb32-rh7-s1-c1 mongodb[17736]: Starting mongod: 2016-06-14T09:05:33.273-0400 F CONTROL [main] Failed global initialization: BadValue: nojournal is not allowed when configsvr is specified Jun 14 09:05:33 mdb32-rh7-s1-c1 runuser[17740]: pam_unix(runuser:session): session closed for user mongod Jun 14 09:05:33 mdb32-rh7-s1-c1 mongodb[17736]: [FAILED] Jun 14 09:05:33 mdb32-rh7-s1-c1 systemd[1]: mongodb.service: control process exited, code=exited status=1 Jun 14 09:05:33 mdb32-rh7-s1-c1 systemd[1]: Failed to start SYSV: Mongo is a scalable, document-oriented database.. Jun 14 09:05:33 mdb32-rh7-s1-c1 systemd[1]: Unit mongodb.service entered failed state. Jun 14 09:05:33 mdb32-rh7-s1-c1 systemd[1]: mongodb.service failed.
Clearly showing that even passing nojournal=false is read by the error as passing nojournal=true. This is bad form. See next section for steps to reproduce.
- is related to
-
SERVER-26487 mongod incorrectly allows config servers to be started without journaling if specified in the config file
- Closed
-
SERVER-25388 Use consistent options parsing to force journaling to be enabled with configsvr
- Closed
- related to
-
SERVER-27368 Balancer not working on 3.4
- Closed