Rocketmq reports an error: service not available now, may disk full, CL: 0.95, CQ: 0.95, index: 0.95, may
the error is caused by the large log file in the/store/commitlog folder. Df-h instructs to view the memory occupied by the current disk By default, rocketmq will treat the ratio of remaining disks less than 75% as insufficient disk space
Solution:
1. Delete the useless log files in the/store/commitlog folder first
2. Edit/conf/2m-2s-async/broker-a.properties file and add Diskmaxusedspaceratio = 98. An error will be reported when the disk occupies 98%
3. Check whether other processes occupy a lot of space. My problem is the logstash problem of elk. Just kill the process
Read More:
- [Solved] Linux Error: tar: Error Is Not Recoverable: Exiting Now
- Linux Install Docker Error: Failed to restart docker.service: Unit docker.service not found.
- Centos8 Could not restart the Network: Failed to restart network.service: Unit network.service not found
- [Solved] Decompression error: tar: Error is not recoverable: exiting now
- How to Solve Unzip Error: tar: Error is not recoverable: exiting now
- [Solved] Linux Service Start Error: *.service: Main process exited, code=exited, status=203/EXEC
- The solution of insufficient disk space of docker in Ubuntu
- [Solved] Gbase Install Error: service cgconfig is not exist on hosts
- redhat7. 5 system service is not started automatically and use systemctl start error: error getting authority: error initializing authority: CO, (the server will restart)
- [Solved] websocket error in Linux service: / lib64 / libc. So. 6: version ` glibc_2.17‘ not found
- Virtual machine ping Command Error: ping name or service not known
- Virtual machine failed to start network service error: ob for network.service failed because the control process exited with error code
- See system logs and ‘systemctl status docker.service‘ for details
- Disk Extended Error: WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
- SSH Connect Service Error: Could not connect to ‘xxx.xxx.xx.xx‘ (port 22): Connection failed.
- [Solved] Some index files failed to download.They have been ignored, or old ones used instead
- Nginx Startup Error: Job for nginx.service failed because the control process exited with error code
- [Solved] error: this statement may fall through [-Werror=implicit-fallthrough=]
- Linux system service command error: Failed to allocate directory watch: Too many open files
- [Solved] FTP Setup Error: Job for vsftpd.service failed because the control process exited with error code…