Exit code 6 ABRT

I have MongoDB running in a virtual machine. Everything was working fine until my physical PC lost power unexpectedly. After rebooting, I am unable to run MongoDb.

Below are the results of running commands that may give information that will help anyone who answers.

mongo -version

MongoDB shell version v4.4.25
Build Info: {
    "version": "4.4.25",
    "gitVersion": "3e18c4c56048ddf22a6872edc111b542521ad1d5",
    "openSSLVersion": "OpenSSL 1.1.1f  31 Mar 2020",
    "modules": [],
    "allocator": "tcmalloc",
    "environment": {
        "distmod": "ubuntu2004",
        "distarch": "x86_64",
        "target_arch": "x86_64"
    }
}

mongo

MongoDB shell version v4.4.25
connecting to: mongodb://127.0.0.1:27017/?compressors=disabled&gssapiServiceName=mongodb
Error: couldn't connect to server 127.0.0.1:27017, connection attempt failed: SocketException: Error connecting to 127.0.0.1:27017 :: caused by :: Connection refused :
connect@src/mongo/shell/mongo.js:374:17
@(connect):2:6
exception: connect failed
exiting with code 1

systemctl status mongod.service

● mongod.service - MongoDB Database Server
     Loaded: loaded (/lib/systemd/system/mongod.service; enabled; vendor preset: enabled)
     Active: failed (Result: core-dump) since Wed 2024-01-17 16:35:01 GMT; 57s ago
       Docs: https://docs.mongodb.org/manual
    Process: 1120 ExecStart=/usr/bin/mongod --config /etc/mongod.conf (code=dumped, signal=ABRT)
   Main PID: 1120 (code=dumped, signal=ABRT)

Jan 17 16:34:57 curtis-virtual-machine systemd[1]: Started MongoDB Database Server.
Jan 17 16:34:57 curtis-virtual-machine mongod[1120]: {"t":{"$date":"2024-01-17T16:34:57.881Z"},"s":"I",  "c":"CONTROL",  "id":7484500, "ctx":"main","msg":"Environment variable MONGODB_CONFIG_OVERRIDE_NOFORK == 1, overriding \"processManagement.fork\" to false"}
Jan 17 16:35:01 curtis-virtual-machine systemd[1]: mongod.service: Main process exited, code=dumped, status=6/ABRT
Jan 17 16:35:01 curtis-virtual-machine systemd[1]: mongod.service: Failed with result 'core-dump'.

Hi @Curtis_L

Check the monogdb server log there may be more information there.

Greetings guys,
I have a problem with one of my replica set nodes. We are trying to manage services from our git repo and to do so. We added the mongod.conf to our repository to better control our configuration files across our environments. What we did was clone the repo to a specific location and create a symlink to /etc/mongod.conf, which was successful on the primary and one secondary node. However, the third node crashed after implementing the changes.

sudo systemctl status mongod
●mongod.service - MongoDB Database Server
Loaded: loaded (/lib/systemd/system/mongod.service; enabled; vendor preset: disabled)
Active: failed (Result: core-dump) since Fri 2024-04-05 17:10:17 EDT; 7min ago
Docs: https://docs.mongodb.org/manual
Process: 2013845 ExecStart=/usr/bin/mongod $OPTIONS (code=dumped, signal=ABRT)
Main PID: 2013845 (code=dumped, signal=ABRT)

As you can see the
Process: 2013845 ExecStart=/usr/bin/mongod $OPTIONS doesn’t see the OPTION= -f /etc/mongod.conf value
on /lib/systemd/system/mongod.service
this is the symlink:
lrwxrwxrwx 1 root root 50 Apr 5 16:59 /etc/mongod.conf → /my-configuration/mongodb/mongod.conf

Is there any step that I can take to solve this issue?
In your opinion, could it be a MongoDB or a system problem (RHEL 8.9)?

Same advice that was not responded to by the OP. Check the logs.
Both journalctl and the mongod log.

If SELinux is enabled(enforcing) then using non-default locations will cause problems. I don’t recall SIGABRT being related to this but I mention it anyway.