Production environment using docker deployment of Nginx suddenly does not work, port 80 can not access, and using Docker restart can not start, so record the problem troubleshooting ideas.

Post the restart failure log first

[root@VM_32_49_centos ~]# docker start nginx
Error response from daemon: containerd: container not started
Error: failed to start containers: nginx
Copy the code

Will this error be displayed no matter how you start

  1. Reinstalling the image

  2. After the installation is complete, the error is still reported when you restart

  3. Reinstall docker

  4. Still not working. Not restarting it

  5. Perceiving it’s not necessarily a Docker thing, so look at it at the system level. Run the systemctl status docker command

  6. [root@VM_32_49_centos ~]# systemctl status docker ● docker. Service – docker Application Container Engine Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled) Active: active (running) since Fri 2020-10-30 10:47:23 CST; 32min ago Docs: docs.docker.com Main PID: 27852 (dockerd-current) CGroup: / / system. Slice docker. Service ├ ─ 27852 / usr/bin/dockerd – current – add – the runtime docker-runc=/usr/libexec/docker/docker-runc-current –default-runtime=docker-runc –exec-opt nativ… └ ─ 27860 / usr/bin/docker containerd – current – l Unix: / / / var/run/docker/libcontainerd/docker – containerd. The sock –metrics-interval=0 –start-timeout 2m…

    Oct 30 10:47:23 VM_32_49_centos dockerd-current[27852]: Time ="2020-10-30T10:47:23.653344611+08:00" level=warning MSG =" Failed to retrieve docker-runc... dumped)" Oct 30 10:47:23 VM_32_49_centos dockerd-current[27852]: Time ="2020-10-30T10:47:23.665870748+08:00" level=info MSG ="Daemon has completed initialization" Oct 30 10:47:23 VM_32_49_centos dockerd-current[27852]: Time ="2020-10-30T10:47:23.665921989+08:00" level=info MSG ="Docker daemon" commit=" ccCB291/1.... N =1.13.1 Oct 30 10:47:23 VM_32_49_centos dockerd-current[27852]: Time ="2020-10-30T10:47:23.675393959+08:00" level=info MSG ="API listen on /var/run/docker.sock" Oct 30 10:47:23 VM_32_49_centos systemd[1]: Started Docker Application Container Engine. Oct 30 11:14:55 VM_32_49_centos dockerd-current[27852]: Time ="2020-10-30T11:14:55.104116871+08:00" level=error MSG ="containerd: Start Container "err... 185a0979 Oct 30 11:14:55 VM_32_49_centos dockerd-current[27852]: Time ="2020-10-30T11:14:55.105097872+08:00" level=error MSG ="Create Container failed with err... started" Oct 30 11:14:55 VM_32_49_centos dockerd-current[27852]: Time ="2020-10-30T11:14:55.115406992+08:00" level=error MSG ="containerd: Deleting Container "...) : \"\"" Oct 30 11:14:55 VM_32_49_centos dockerd-current[27852]: Time = ": the 2020-10-30 T11 14:55. 344969246 + 08:00" level = warning MSG = "ef3fbebbcd5fa945e6da16e495b8a9... rgument" Oct 30 11:14:55 VM_32_49_centos dockerd-current[27852]: Time ="2020-10-30T11:14:55.345016518+08:00" level=error MSG ="Handler for POST /v1.26/containe... started" Hint: Some lines were ellipsized, use -l to show in full.Copy the code

The health has been found to be error as well. Could it be that CPU or memory is too high?

6. Run the top command to check the CPU and memory usage

Found %Cpu(s): 99.4us is almost 100%. Ok problem found, now to find a way to reduce CPU usage.

Because using the top command directly does not show which block occupies the CPU. So we’re pretty sure it’s been hacked.

I looked online and found it was mined.

Finally through the method of the great god, finally is to kill the disgusting wooden horse

Link address: www.cnblogs.com/guigujun/p/…