The error below occurs when mongodb is started. Check the log file and find:
exception in initAndListen std::exception: listen: Address already in use, terminating,
Possible errors:
1. Your conf file is incorrectly written, format or code, etc
2. Bindip binds both the localhost and the internal and external addresses of the server
Solution: check and write the file format, and pay attention to yaml format. Then, bindip directly accesses 0.0.0.0, allowing all access. It should be OK.
If viewing the log is this error:
Failed to set up listener: SocketException: Address already in use
ps aux | grep mongod sudo kill -9 {port-number}
Read More:
- [Solved] Tomcat Startup Error: A child container failed during start、LifecycleException: Failed to start component
- The number of control threads and concurrency number of concurrent executor of Java starting gun
- [Solved] Heroku Error: Web process failed to bind to $PORT within 60 seconds of launch
- Android studio compilation failed: java.util.concurrent.ExecutionException: com.android.ide.common.process.Process
- [Solved] Tomcat Startup Error: A child container failed during start
- mybatis “case when” Error: Failed to process, please exclude the tableName or statementId.
- How to convert a Java string into a number (stringtonumber)
- Resin Failed to Startup Error: ERROR: transport error 202: bind failed: Address already in use: JVM_Bind Listenin (Two Resins in One PC)
- [Solved] Kafka in Windows error:java. nio. file. Filesystemexception: this file is in use by another program and cannot be accessed by the process
- [Solved] JNI Error: ld: error: too many errors emitted, stopping now (use -error-limit=0 to see all errors)
- Exception information: jsonmappingexception: out of start_ ARRAY token
- [Solved] Web server failed to start. Port 8080 was already in use.
- [Solved] Artifact spbjh:war exploded: Error during artifact deployment. See server log for details.
- [Solved] Java POI export error: Invalid row number (65536) outside allowable range
- [Solved] Docker Startup Error: OCI runtime create failed container_linux.go380 starting container process
- [Solved] Artifact AServletTestCode:war exploded: Error during artifact deployment. See server log for details
- How to Solve Image Upload Error: Uncaught (in promise) DOMException: Failed to execute ‘put‘ on ‘IDBObjectStore‘
- [Fixed] Disgusting bug Error:Failed to Load project configuration: cannot parse filemessage: content is not allowed in the preface.
- [Solved] Tomcat Start Project Error: Artifact xxxxxx:war exploded: Error during artifact deployment. See server log