|
|
| Subject: | serviced cannot start: failed to pull image: zenoss/serviced-isvcs:v27.2 not available |
| Author: | [Not Specified] |
| Posted: | 2016-02-01 08:17 |
Hi all,
When we tried to restart Zenoss after a memory full (on a 20Gb ram machine !) Zenoss cannot restart with the message:
Feb 01 11:36:54 hs3-sysmon-01.hs3.vdc.corp.homesend.com serviced[1775]: I0201 10:36:54.453790 01775 manager.go:244] Pulling image zenoss/serviced-isvcs:v27.2
Feb 01 11:36:55 hs3-sysmon-01.hs3.vdc.corp.homesend.com serviced[1775]: E0201 10:36:55.098651 01775 api.go:694] Unable to pull image zenoss/serviced-isvcs:v27.2
Feb 01 11:36:55 hs3-sysmon-01.hs3.vdc.corp.homesend.com serviced[1775]: F0201 10:36:55.098727 01775 daemon.go:145] Could not start isvcs: Failed to pull image zenoss/serviced-isvcs:v27.2: image zenoss/serviced-isvcs:v27.2 not availableIt is a Zenoss version 5.0.0.7. I suspect that the issue is related to the old Docker version.
CPaFoo
| Subject: | I ran into an issue (twice) |
| Author: | [Not Specified] |
| Posted: | 2016-02-01 15:29 |
I ran into an issue (twice) where /var/lib/docker/ was full. The data file in the devicemapper folder has blown up in size to take the entire partition. This is a known docker issue that needs to be fixed in the CentOS kernel, I do not know if it is done in the latest CentOS 7.
Manuel
| Subject: | Yes, old docker is your |
| Author: | Jan Garaj |
| Posted: | 2016-02-01 16:38 |
Yes, old docker is your problem.
On December 7, 2015, pulls via clients 1.5 and earlier will bedisabled. Only version 1.6 or later will be supported.
https://blog.docker.com/2015/10/docker-hub-deprecation-1-5/
Devops Monitoring Expert advice:
Dockerize/automate/monitor all the things.
DevOps stack:
Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform /
Elasticsearch
| < |
Previous rsyslog forwarding |
Next Purge old events in histoty Zenoss table |
> |