--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.
For other MongoDB technical support options, see: https://docs.mongodb.com/manual/support/
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+unsubscribe@googlegroups.com.
To post to this group, send email to mongod...@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/79d5002b-dbc3-4235-b23e-f53eb8746568%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Can you post your config file /usr/local/etc/mongod.conf ?Mar 09 08:27:46 ldmongodb01_u2 systemd[1]: mongod.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
2018-03-09 19:35 GMT+01:00 Alan <tngu...@gmail.com>:
Hi,I have just upgraded mongodb from version 3.4 to 3.6.3, but now the mongo server won't start up. When I try to start up the service with "sudo service mongod start", I get the following message. I'm running on Ubuntu 16.04.3 LTS. Anyone please help.● mongod.service - High-performance, schema-free document-oriented database
Loaded: loaded (/etc/systemd/system/mongod.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2018-03-09 08:27:46 HST; 3min 1s ago
Docs: https://docs.mongodb.org/manual
Process: 17401 ExecStop=/usr/local/mongodb/bin/mongod --shutdown (code=exited, status=1/FAILURE)
Process: 17398 ExecStart=/usr/local/mongodb/bin/mongod --quiet --config /usr/local/etc/mongod.conf (code=exited, status=2)
Main PID: 17398 (code=exited, status=2)Mar 09 08:27:46 ldmongodb01_u2 systemd[1]: Started High-performance, schema-free document-oriented database.
Mar 09 08:27:46 ldmongodb01_u2 systemd[1]: mongod.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Mar 09 08:27:46 ldmongodb01_u2 systemd[1]: mongod.service: Control process exited, code=exited status=1
Mar 09 08:27:46 ldmongodb01_u2 systemd[1]: mongod.service: Unit entered failed state.
Mar 09 08:27:46 ldmongodb01_u2 systemd[1]: mongod.service: Failed with result 'exit-code'.
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.
For other MongoDB technical support options, see: https://docs.mongodb.com/manual/support/
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+unsubscribe@googlegroups.com.
To post to this group, send email to mongod...@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/3a6b329f-a834-42b7-9550-f42d1b4f3709%40googlegroups.com.
but still having the same problem. Please help.
Hi Alan,
Please note that the deprecated options for HTTP Interface and REST API have been removed in MongoDB v3.6. This may be the cause of the mongod server unable to start up.
For more information about MongoDB 3.6 configuration file, please see Configuration Options.
I’d also suggest to check your mongod log file located in “/var/log/mongodb/mongod.log”.
You may also find Upgrade a standalone to 3.6 a useful reference.
Regards,
Wan.