[SERVER-32986] cannot start mongod Created: 29/Jan/18  Updated: 21/Mar/18  Resolved: 23/Feb/18

Status: Closed
Project: Core Server
Component/s: Build
Affects Version/s: 2.6.12
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Mark Wan Assignee: Kelsey Schubert
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Steps To Reproduce:

Operating System: Centos 7.1.1503 or Redhat 7.3

yum install mongodb-server

service start mongod.service

Participants:

 Description   

after installing mongodb-server-2.6.12-5.el7.x86_64, I cannot start mongod. It works if I revert to mongodb-server-2.6.12-4.el7.x86_64. Details as follows:

Job for mongod.service failed because the control process exited with error code. See "systemctl status mongod.service" and "journalctl -xe" for details.

Running Systemctl status gives me:
Jan 29 22:41:35 localhost.localdomain systemd[1]: Starting High-performance, schema-free document-oriented database...
Jan 29 22:41:35 localhost.localdomain mongod[1313]: No map found at top level of YAML config
Jan 29 22:41:35 localhost.localdomain mongod[1313]: try '/usr/bin/mongod --help' for more information
Jan 29 22:41:35 localhost.localdomain systemd[1]: mongod.service: control process exited, code=exited status=2
Jan 29 22:41:35 localhost.localdomain systemd[1]: Failed to start High-performance, schema-free document-oriented database.
Jan 29 22:41:35 localhost.localdomain systemd[1]: Unit mongod.service entered failed state.
Jan 29 22:41:35 localhost.localdomain systemd[1]: mongod.service failed.

The mongod.conf is still in the old format. Switching the conf file to yaml does not help:

Jan 29 22:27:36 localhost.localdomain systemd[1]: Starting High-performance, schema-free document-oriented database...
Jan 29 22:27:36 localhost.localdomain mongod[1298]: No map found at top level of YAML config
Jan 29 22:27:36 localhost.localdomain mongod[1298]: try '/usr/bin/mongod --help' for more information
Jan 29 22:27:36 localhost.localdomain systemd[1]: mongod.service: control process exited, code=exited status=2
Jan 29 22:27:36 localhost.localdomain systemd[1]: Failed to start High-performance, schema-free document-oriented database.
Jan 29 22:27:36 localhost.localdomain systemd[1]: Unit mongod.service entered failed state.
Jan 29 22:27:36 localhost.localdomain systemd[1]: mongod.service failed.



 Comments   
Comment by Kelsey Schubert [ 23/Feb/18 ]

Hi mhywan,

Thank you for confirming that these packages aren't distributed by MongoDB. I would recommend that you use the repos specified in our docs and install a more recent version of MongoDB as Ramon suggested.

Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag.

Kind regards,
Kelsey

Comment by Mark Wan [ 22/Feb/18 ]

[epel]
name=Extra Packages for Enterprise Linux 7 - $basearch
#baseurl=http://download.fedoraproject.org/pub/epel/7/$basearch
mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=$basearch

Comment by Kelsey Schubert [ 20/Feb/18 ]

Hi mhywan,

Would you please confirm the repo you are installing from using yum?

Thanks,
Kelsey

Comment by Mark Wan [ 31/Jan/18 ]

Problem with 2.6 is with mixing and matching. We have mongodb-server-2.6.12-4.el7.x86_64 and yaml-cpp-0.5.1-6.el7.x86_64 installed.

When we yum update mongodb-server, it updated to mongodb-server-2.6.12-5 without updating yaml-cpp-0.5.3, thus having problems. Similarly we can run into the issue if yaml-cpp-0.5.1 is installed ahead of any mongodb-server and then we install mongodb-server.

I will try 3.6.2 after we dealt with this issue for our production servers.

Comment by Ramon Fernandez Marina [ 30/Jan/18 ]

Please note that MongoDB 2.6 is EOL and no longer supported. A colleague also points out this may be related to this change in EPEL 7.

Will you please try MongoDB 3.6.2 and report back?

Generated at Thu Feb 08 04:31:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.