|
|
| Subject: | Control center won't start anymore because docker is 100% full |
| Author: | [Not Specified] |
| Posted: | 2016-03-25 08:48 |
Hi,
I noticed that after rebooting my CentOS machine; the control center didn't work anymore. After manually try to start the docker service it ran in to a error. I took a look at the journalctl -xe and saw the following:
Mar 25 12:57:37 nl-mon-fra201 docker[2473]: time="2016-03-25T12:57:37.154732407+01:00" level=fatal msg="Error starting daemon: Insertion failed because databause is full: database or disk is full
Mar 25 12:57:37 nl-mon-fra201 systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Mar 25 12:57:37 nl-mon-fra201 systemd[1]: Failed to start Docker Application Container Engine.
I googled on Error starting daemon: Insertion failed because databause is full: database or disk is full and noticed somebody talking about the /var/lib/docker that was 100%.
Did a df -h and saw indeed that my /var/lib/docker is 100%
Now the problem is; how can i clean it up Most sites are talking about invoking the docker but the docker won't run because the lack of freespace.
Anyone have an idea to fix this
Thanks in advance!
David
[root@nl-mon-fra201 docker]# docker version
Client:
Version: 1.8.2
API version: 1.20
Go version: go1.4.2
Git commit: 0a8c2e3
Built: Wed Oct 7 17:25:19 UTC 2015
OS/Arch: linux/amd64
Cannot connect to the Docker daemon. Is 'docker -d' running on this host
[root@nl-mon-fra201 docker]#
| Subject: | Yikes! |
| Author: | Andrew Kirch |
| Posted: | 2016-04-12 08:56 |
Yikes!
This guide should help!https://support.zenoss.com/hc/en-us/articles/204643769-How-to-Recover-Control-Center-from-Hardware-Failure
Andrew Kirch
akirch@gvit.com
Need Zenoss support, consulting or custom development Look no further. Email or PM me!
Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard
| Subject: | I just ran into this problem. |
| Author: | Jim R |
| Posted: | 2016-05-20 10:56 |
I just ran into this problem. I had installed docker and serviced, but did not configure docker correctly to use the correct thinpool.
Basically, I removed and recreated /var/lib/docker, recreated the symlink from /var/lib/docker/tmp to /tmp and restarted docker.
If you have some other storage, you can likely move the files around and create symlinks that point to the correct directories if you aren't using thin-pool storage already.
Docker will complain if you cahnge the storage location and type between restarts, so you will need to recreate /var/lib/docker in this case.
| < |
Previous Trying to resolve an issue we see in Control Center |
Next Zenoss 5 and WinRM |
> |