The main reason is abnormal shutdown.
if you have abnormal shutdown operation, please try the following methods
mongod --dbpath /usr/local/mongodb/data --logpath /usr/local/mongodb/mongod.log --fork
Dbpath is your data configuration path
logpath is your log path
through this command, similar to windows restart services Service
Read More:
- Mongodb uses Mongo to report error: could’t connect to server 127.0.0.1:27017, connection attempt failed: socket
- The mongoDB service failed to start (exception: connect failed)
- 【MongoDB】 Failed to connect to 127.0.0.1:27017, reason: Connection refused
- Window installation of MongoDB exception: connect failed exception
- MongoDB Error: Failed to start mongod.service: Unit mongodb.service is masked
- Mongodb encountered an error: connect econnreused 127.0.0.1:27017
- MongoNetworkError: failed to connect to server [localhost:27017] on first connect [Error: connect EC
- Unable to connect to MKS：Internal error
- Deploy mongodb fragment combined with replica set to realize distributed storage of MySQL database files (step 10)
- About WLW (Windows Live Writer): “unable to connect to your log service: invalid server response” solution
- [Solved] failed to connect to server, reason: Unable to establish connection
- On fileZilla unable to connect FATAL ERROR: Connection union
- JRebel: ERROR Failed to obtain seat. Unable to connect to license server. Check
- svn RA layer request failed unable to connect to a repository
- How to Fix “Oracle sp2-0640 unable to connect” Error
- Mongodb — startup exception, error report ERROR:NUMBER 100
- TCP error code 10061: unable to connect because the target machine actively refused http://localhost :8732/Design_ Time_ Addresses/TeacherHelperServic
- Docker was unable to connect to the docker daemons
- Mongodb start error: child process failed, exited with error number 1
- MongoDB：Failed: error connecting to db server: no reachable servers