TECHZEN Zenoss User Community ARCHIVE  

Zenoss 5: Deploying application template failed

Subject: Zenoss 5: Deploying application template failed
Author: Benjamin Dronen
Posted: 2015-04-15 15:12

I am getting this error in control center when trying to deploy Zenoss on an Ubuntu host: Deploying application template failed Internal Server Error: could not look up image zenoss/core_5.0:5.0.1_6: docker: no such image. Check your docker login and retry service deployment.

I had thought I had followed every instruction in the install guide very carefully. The control center user I am using is a paart of the docker group, the sudo group, and the serviced group.

Any thoughts



Subject: see if you can run: docker
Author: Andrew Kirch
Posted: 2015-04-15 15:54

see if you can run: docker pull zenoss/core_5.0:5.0.1_6

If you get an error paste the output.

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: Please show the (http:/
Author: Jan Garaj
Posted: 2015-04-15 15:56

Please show the (http://pastebin.com) logs:
journalctl -u serviced -an

And try to pull image manually as root:
docker pull zenoss/core_5.0:5.0.1_6

Devops Monitoring Expert advice: Dockerize/automate/monitor all the things.

DevOps stack: Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform / Elasticsearch



Subject: bd9dc1f2ab6a: Error
Author: Benjamin Dronen
Posted: 2015-04-15 16:29

bd9dc1f2ab6a: Error downloading dependent layers
FATA[0021] Error pulling image (5.0.1_6) from zenoss/core_5.0, Untar exit status 1 write /opt/zenoss/webapps/zeneventserver/WEB-INF/lib/jython-standalone-2.5.2.jar: no space left on device

It seems I was running out of space on /var. Changing Docker root fixed issue, but will changing docker root affect Zenoss



Subject: portions of the FS that
Author: Andrew Kirch
Posted: 2015-04-16 10:08

portions of the FS that docker uses needs to be btrfs. Please consult the installation manual as this will break if you aren't on btrfs.

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: Im getting the same error
Author: [Not Specified]
Posted: 2015-11-18 01:37

Deploying application template failed Internal Server Error: could not look up image zenoss/core_5.0:5.0.8_1: docker: no such image. Check your docker login and retry service deployment.

@Trelane:
May I knwo how to do the btrfs
Thank you



Subject: Tried to run: docker pull zenoss/core_5.0:5.0.1_6
Author: [Not Specified]
Posted: 2015-11-18 01:50

Error:
Pulling repository zenoss/core_5.0
FATA[0066] Get https://registry-1.docker.io/v1/repositories/zenoss/core_5.0/tags: read tcp x.x.x.x:443: i/o timeout



Subject: Check your https network
Author: Jan Garaj
Posted: 2015-11-18 02:07

Check your https network connectivity to https://registry-1.docker.io and try again. I guess it's docker hub problem, because it's incredible slow last week.

Devops Monitoring Expert advice: Dockerize/automate/monitor all the things.

DevOps stack: Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform / Elasticsearch



Subject: Thanks garaj for your reply.
Author: [Not Specified]
Posted: 2015-11-18 02:14

Thanks garaj for your reply.
I suspect it has something to do on btrfs. because when i installed it using auto-deploy script, it says:
xfs /opt/serviced/var/volumes filesystem detected, but btrfs is required. Do you want to continue (y/n)



Subject: And it was red warning and
Author: Jan Garaj
Posted: 2015-11-18 02:39

And it was red warning and you said yes, even if it's required filesystem type. Not good - you will have a issue in near future.
Don't ignore RED warnings from autodeploy script. You can do it only, if you are expert.

I'll publish blog post soon about this problem - people are ignoring red warnings and they install Zenoss 5 on VM with 1CPU, 1GB, simfs filesystems, ...

Devops Monitoring Expert advice: Dockerize/automate/monitor all the things.

DevOps stack: Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform / Elasticsearch



Subject: I used 20gb ram, 4 cpu's and
Author: [Not Specified]
Posted: 2015-11-18 02:44

I used 20gb ram, 4 cpu's and 120 hdisk space.
can you help me on the btrfs part I will just do the re-installation.
i used auto-deploy script. are there other commands i need to run aside from the auto deploy script im using centos 7. Thank you so much.



Subject: I'm getting this exact error
Author: [Not Specified]
Posted: 2015-11-18 07:21

I'm getting this exact error now as well.

Assuming there's some issue at Docker.



Subject: Any help?
Author: [Not Specified]
Posted: 2015-11-19 03:51

Any help



< Previous
Zenoss5 - Change IP Address of Host OS
  Next
Problem starting services
>