Mongod Does Not Start (Mongod.Service: Failed with Result 'Signal')

Mongod does not start (mongod.service: Failed with result 'signal')

Signal "ILL" is illegal instruction.

MongoDB 5.0 requires Advanced Vector Extensions, Xeon E5540 does not have them.

For a list of processors that support AVX, see https://en.wikipedia.org/wiki/Advanced_Vector_Extensions#CPUs_with_AVX

Mongod does not start: mongod.service: Failed with result 'signal'

While this doesn't completely solve the issue, I'm fine with this resolution:
For whatever reason, 4.2 works fine, but 4.4 doesn't, even though I was completely fine running 4.4 on Arch.

MongoDB failed (result: core-dump)?

1.Stop the mongod process by issuing the following command:-

    sudo service mongod stop
    

2.Remove any MongoDB packages that you had previously installed:-

    sudo apt-get purge mongodb-org*
    

3.Remove MongoDB databases and log files:-

    sudo rm -r /var/log/mongodb
    sudo rm -r /var/lib/mongodb
    

4.Then reinstall mangodb 4.4.8

5.Import the public key used by the package management system:-

    wget -qO - https://www.mongodb.org/static/pgp/server-4.4.asc | sudo apt-key add -
    

6.The following instruction is for Ubuntu 20.04 (Focal):-

    echo "deb [ arch=amd64,arm64 ] https://repo.mongodb.org/apt/ubuntu focal/mongodb-org/4.4 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-org-4.4.list
    

7.Update Apt

    sudo apt-get update
    

8.Install mongodb

    sudo apt-get install mongodb-org=4.4.8 mongodb-org-server=4.4.8 mongodb-org-shell=4.4.8 mongodb-org-mongos=4.4.8 mongodb-org-tools=4.4.8
    

9.Use mongod --version to check its succesfully installed

10.If u encounter any error while using mongod

    sudo mkdir /data
    cd /data
    sudo mkdir db
    sudo pkill -f mongod
    

11.Then use sudo mongod command.

Service mongod does not start on Centos8

For some kind of reason, mongod want the folder /data/db and ignore the file mongod.conf

After I created these folders, if I run mongod command (with sudo), programme start "correctly".
But if I reboot the system, the service fails on boot and continue to have problems.

How to stop mongo DB in one command

Starting and Stopping MongoDB is covered in the MongoDB manual. It explains the various options of stopping MongoDB through the shell, cli, drivers etc. It also details the risks of incorrectly stopping MongoDB (such as data corruption) and talks about the different kill signals.

Additionally, if you have installed MongoDB using a package manager for Ubuntu or Debian then you can stop mongodb (currently mongod in ubuntu) as follows:

• Upstart: sudo service mongod stop

• Sysvinit: sudo /etc/init.d/mongod stop

Or on Mac OS X

• Find PID of mongod process using $ top

• Kill the process by $ kill <PID> (the Mongo docs have more info on this)

Or on Red Hat based systems:

• service mongod stop

Or on Windows if you have installed as a service named MongoDB:

• net stop MongoDB

And if not installed as a service (as of Windows 7+) you can run:

• taskkill /f /im mongod.exe

To learn more about the problems of an unclean shutdown, how to best avoid such a scenario and what to do in the event of an unclean shutdown, please see: Recover Data after an Unexpected Shutdown.

---

Related Topics