May 03 08:26:00 ansible-demo-tower runuser: pam_unix(runuser:session): session opened for user mongod by (uid=0) May 03 08:26:00 ansible-demo-tower systemd: Starting SYSV: Mongo is a scalable, document-oriented database. See "systemctl status rvice" and "journalctl -xe" for init.d]# journalctl -xe Job for rvice failed because the control process exited with error code. However, with recent versions of MongoDB the database might not come up via init.d]# systemctl start mongod Since MongoDB is not part of RHEL/CentOS, it is installed directly form the upstream MongoDB repositories. A workaround requires some SELinux work.Īnsible Tower collects system data inside a MongoDB. In such cases with recent updates the service might fail to start via systemctl. You have to ensure that the hard disk has sufficient space before launching an instance and a system restart would be needed for MongoDB to start automatically.MongoDB is often installed right from upstream provided repositories.
Mongo requires 3gb hard disk free space to get started. T06:07:56.809+0000 shutdown: going to close listening sockets. T06:07:56.809+0000 exception in initAndListen: 15926 Insufficient free space for journals, terminating T06:07:56.764+0000 Please make at least 3379MB available in /var/lib/mongo/journal or use -smallfiles T06:07:56.763+0000 ERROR: Insufficient free space for journal files T06:07:56.763+0000 recover : no journal files present, no recovery needed Try to start MongoDB service and check MongoDB logs you may find these errors on the log /var/log/mongodb/mongod.log . Jun 23 06:07:56 localhost.localdomain systemd: rvice failed. Jun 23 06:07:56 localhost.localdomain systemd: Unit rvice entered failed state. Jun 23 06:07:56 localhost.localdomain systemd: Failed to start SYSV: Mongo is a scalable, document-oriented database. Jun 23 06:07:56 localhost.localdomain systemd: rvice: control process exited, code=exited status=1 Jun 23 06:07:56 localhost.localdomain mongod: Starting mongod: Jun 23 06:07:56 localhost.localdomain runuser: pam_unix(runuser:session): session opened for user mongod by (uid=0) Jun 23 06:07:56 localhost.localdomain systemd: Starting SYSV: Mongo is a scalable, document-oriented database. Main PID: 2350 (code=exited, status=0/SUCCESS) Process: 2588 ExecStart=/etc/rc.d/init.d/mongod start (code=exited, status=1/FAILURE) Process: 2547 ExecStop=/etc/rc.d/init.d/mongod stop (code=exited, status=0/SUCCESS) Loaded: loaded (/etc/rc.d/init.d/mongod bad vendor preset: disabled)Īctive: failed (Result: exit-code) since Fri 06:07:56 UTC 19h ago
This document describes how to troubleshoot "MongoDB not able to start" error on CloudCenter Orchestrator (CCO).