Details
-
Bug
-
Resolution: Gone away
-
Major - P3
-
None
-
3.2.10
-
None
-
Linux based OS
-
ALL
Description
I have running mongod 3.2 with --dbpath on NFS.
When I run mongod -f /etc/mongod.conf then mongod is running and accepting connections, but file `/var/lib/mongodb/data/mongod.lock` is empty.
So mongod -f /etc/mongod.conf --shutdown is not working for me (getting error There doesn't seem to be a server running with dbpath: /var/lib/mongodb/data)
How it is possible? I am trying to figure out how to reproduce it, but for now what could be reason of this odd behavior?
Content of /etc/mongod.conf
##
|
## For list of options visit:
|
## https://docs.mongodb.org/manual/reference/configuration-options/
|
##
|
|
|
# systemLog Options - How to do logging
|
systemLog:
|
# Runs the mongod in a quiet mode that attempts to limit the amount of output
|
quiet: true
|
|
|
|
|
# net Options - Network interfaces settings
|
net:
|
# Specify port number (27017 by default)
|
port: 27017
|
|
|
|
|
# storage Options - How and Where to store data
|
storage:
|
# Directory for datafiles (defaults to /data/db/)
|
dbPath: /var/lib/mongodb/data
|
|
|
|
|
# replication Options - Configures replication
|
replication:
|
# Specifies a maximum size in megabytes for the replication operation log (i.e. the oplog,
|
# 5% of disk space by default)
|
oplogSizeMB: 64
|
|
|
storage.wiredTiger.engineConfig.cacheSizeGB: 1
|
File with server output is attached.