Modify prometheus.yml file and failed to start:
1. Configuring prometheus + node_exporter monitoring, the solution to the failure to start after modifying the prometheus.yml file.
2. Error message 1: err=”opening storage failed: lock DB directory: resource temporarily unavailable”
Solution: Check whether the current directory has generated files plus data/lock, need to delete the lock file: rm -rf lock
Delete and restart again
error message 2:err= “error starting web server: listen TCP 0.0.0:9090: bind: address ready in use”
installation command: yum install lsof -y
view command: lsof -i:9090
end command: kill -9 2878
restart command: ./prometheus
restart succeeded after operation 
Read More:
- Nginx Error: [emerg] bind() to [::]:80 failed (98: Address already in use)
- [Solved] mongo Startup Error: ERROR: child process failed, exited with error number 1
- [Solved] Web server failed to start. Port 8080 was already in use.
- Ubuntu found an error during apt operation [How to Solve]
- Install and start the tftp-server server and possible solutions to Redirecting to /bin/systemctl restart xinetd.service problems
- Docker Error: error invoking remote method ‘docker-start-container‘: error: (http code 500) server error –
- [Solved] redis Startup Error: Creating Server TCP listening socket 127.0. 0.1:6379: bind: no error redis
- Solution of device eth0 does not see to be present, delaying initialization. Error in network card under Linux
- [Nginx] solution: it can’t be accessed on the background API interface after HTTPS (access the specified port through the domain name)
- Aliyunshield occupies port 80 error: Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use
- [Solved] FTP Setup Error: Job for vsftpd.service failed because the control process exited with error code…
- Nginx configuration 80 can be accessed by forcing jump 443 or not
- redhat7. 5 system service is not started automatically and use systemctl start error: error getting authority: error initializing authority: CO, (the server will restart)
- How to Solve NPM Error: listen EADDRINUSE 127.0.0.1:8080
- [Solved] Error: listen EADDRINUSE: address already in use :::5000
- How to Solve Ubuntu “Failed to fetch” Error
- [Solved] Linux ECDSA key Error: Host key verification failed
- The problem of inconsistent host names in building rabbitmq on Linux
- [Solved] rsync Error: @ERROR: chdir failed rsync error
- Prometheus auto discovery and re labeling based on consumer