The docker service on the Linux server cannot be started after running for a period of time
Record a docker service problem encountered at the customer’s site
Problem description
After running the docker service for a period of time, some services are killed and cannot be restarted successfully through docker compose. Check the docker service log and report an error stream copy error: reading from a closed FIFO
Troubleshooting process:
1. The initial positioning is that there is not enough memory. Check with Free -g
and find that the content is enough
2 After searching the Internet, some bloggers said that restarting docker could solve the problem. After restarting docker, they found that the error changed, and the service that didn’t get up before still couldn’t get up. The error became failed to allocate network resources for node *****
3 The network of docker service is the default. Regardless of the problem of docker network, changing the stack name and restarting still won’t work
4 Docker service PS ID/docker service logs ID check the service log that failed to start. It is found that the error log is still stream copy error: reading from a closed FIFO
5 Finally, before restarting the server, check the disk with the df -h
command and find that the/dev/mapper/centosroot disk is full
Solution:
Go to cd /var/log to delete some useless log files, if the current log files are small, you can use du -sh in the root directory to view those folders occupy a lot of space, generally the /var folder and /root folder will occupy the root disk, you need to delete the contents of these two folders
Read More:
- Error Running Context: The server unexpectedly closed the connection
- /usr/bin/ssh-copy-id: ERROR: No identities found [How to Solve]
- Git Clone RPC failed;curl 18 transfer closed with outstanding read data remaining
- [Solved] Jenkins+Ant Error: Error reading project file xxxxx
- [Solved] Using GCP copy to report errors in Linux: DBUS. Exceptions. Dbusexception: org. Freedesktop. DBUS. Error. Notsupported:
- [Solved] GVM Error: rsync: connection unexpectedly closed & rsync: read error: Connection reset by peer (104)
- Ubuntu18.04 Compile A40i SDK Error: misc/create_inode.c:395:18: error: conflicting types for ‘copy_file_range‘
- Disk Extended Error: WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
- [Solved] paramiko.ssh_exception.SSHException: Error reading SSH protocol banner
- [Solved] Win10 and Linux address reading format is different (CV2. Error: opencv (4.2.0)/Io/opencv…)
- [Ubuntu] How to Solve dpkg Error: dpkg: error: failed to open package info file ‘/usr/local/var/lib/dpkg/status’ for reading: No such file or directory
- [Solved] Rocketmq error: service not available now, may disk full, CL: 0.95, CQ: 0.95, index: 0.95
- Nginx Error: [emerg] bind() to [::]:80 failed (98: Address already in use)
- Error: ENOSPC: no space left on device [How to Solve]
- Virtual machine ping Command Error: ping name or service not known
- See system logs and ‘systemctl status docker.service‘ for details
- The solution of insufficient disk space of docker in Ubuntu
- [Solved] Docker Download Mirror Error: Cannot connect to the Docker daemon at…
- Job for network.service failed [How to Solve]
- [Solved] Docker Filed to Start Container: Error response from daemon: network XXX not found