First of all, for security reasons, it is recommended to turn on auth regardless of whether the IP is restricted or not. It is recommended to turn it on when appropriate. "It worked fine yesterday" and "The link reported an error today" are actually not necessarily related, right? Even if it was fine yesterday, it doesn't prove that there won't be any problems today or in the future. So just focus on the current issues. Sorry for being a bit verbose, I am a bit obsessive about logical rigor:) First check whether the process exists and whether the monitoring is normal:
ps aux | grep mongod
netstat -pln | grep mongod
Usually the situation should be that mongod has been terminated. Please check your log for the specific reason. By default located at:
/var/log/mongod.log
If there are any modifications, please check them yourself. It is recommended to check the last situation of the log. You should see dbexit. Show the last 50 lines and let us continue the analysis.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
First of all, for security reasons, it is recommended to turn on auth regardless of whether the IP is restricted or not. It is recommended to turn it on when appropriate.
"It worked fine yesterday" and "The link reported an error today" are actually not necessarily related, right? Even if it was fine yesterday, it doesn't prove that there won't be any problems today or in the future. So just focus on the current issues. Sorry for being a bit verbose, I am a bit obsessive about logical rigor:)
First check whether the process exists and whether the monitoring is normal:
Usually the situation should be that mongod has been terminated. Please check your log for the specific reason. By default located at:
If there are any modifications, please check them yourself. It is recommended to check the last situation of the log. You should see
dbexit. Show the last 50 lines and let us continue the analysis.