Mongod command failing with Core dump

MongoDB University M103: Basic Cluster Administration
#1

Hi,
I had setup 2 shards in my environment with config and data replica set. After reboot of my machine none of the commands (mongod, mongos) are working. Mongod is failing with below error:
Aborted (core dumped)

Mongos is hung with below output:
vagrant@m103:~$ mongos -f mongos.conf
2019-03-04T14:36:29.788+0000 W SHARDING [main] Running a sharded cluster with
fewer than 3 config servers should only be done for testing purposes and is not
recommended for production.
about to fork child process, waiting until server is ready for connections.
forked process: 3028

Content of one of the conf files:
sharding:
clusterRole: shardsvr
storage:
dbPath: /var/mongodb/db/1
wiredTiger:
engineConfig:
cacheSizeGB: .1
net:
bindIp: 192.168.103.100,localhost
port: 27001
security:
authorization: enabled
keyFile: /var/mongodb/pki/m103-keyfile
systemLog:
destination: file
path: /var/mongodb/db/mongod1.log
logAppend: true
##processManagement:

fork: true

replication:
replSetName: m103-repl

Can you please let me know what could be the issue here ?

Thanks,
Prashant.

Lab - Shard a Collection error
#2

Are you able to bring up 3 config servers?
Does a simple test mongod on a new port also core dumps?
Cleanup all mongod’s and restart

#3

Hi Ramachandra,
No. I am unable to bring up config servers too.
mongod on a random new port number works fine.

Cleanup mongod - do you mean to kill all mongod processes and start ?

#4

Hi, please share the rs.status() for replica set: m103-csrs.

It should contain three nodes- 26001, 26002 and 26003.

Kanika

#5

Hi Ramachandra,
I could resolve it by changing DB path on all config files and restarting the nodes. Thanks for your time.