---

Subject:	what about a manual installation of Zenoss 5.2.2
Author:	[Not Specified]
Posted:	2017-03-14 05:08

Hi,

I recommend you install from ISO, instead of OVA. It will automatically install and configure everything for you.

What about a manual installation of Zenoss 5.2.2? Let me know if you are interested.

Kind regards,

Robert E.

zenoss@webhostingspace.net

Zenoss Core/Service Dynamics 5.2.2 High Availability - the missing guide is here

---

Subject:	i'll try anything at this
Author:	[Not Specified]
Posted:	2017-03-14 08:23

i'll try anything at this moment. i'm just triyng to test it out as it's been a while since i've used Zenoss.

---

Subject:	actually i downloaded the
Author:	[Not Specified]
Posted:	2017-03-14 13:11

actually i downloaded the minimal install of centos and will manaully install 5.2.2 if we can do it easier that way.

i just installed a fresh VM from zenoss-core-5.2.1-1-master.vmware.ova and am testing a few things out again.

 

---

Subject:	The easy way is installing
Author:	[Not Specified]
Posted:	2017-03-14 14:44

The easy way is installing from ISO or OVA. Manually installations will give you more options for deployment.

Kind regards,

Robert E.

zenoss@webhostingspace.net

Zenoss Core/Service Dynamics 5.2.2 High Availability - the missing guide is here

---

Subject:	you said it best, the easy
Author:	[Not Specified]
Posted:	2017-03-16 22:01

you said it best, the easy way is the .ova, but i've even failed that....

 

---

Subject:	I'm not familiar with the OVA
Author:	[Not Specified]
Posted:	2017-03-17 07:54

I'm not familiar with the OVA process. Are you still having the same issue from your first post?

Are you able to open Control Center without adding the template?

From the very little you've posted, it looks like serviced and zenoss are already installed and should be ready to go.

---

Subject:	since the insructions are
Author:	[Not Specified]
Posted:	2017-03-20 15:54

since the insructions are about as clear as mud, i'm stuck with a server that does nothing after deploying through the ova file.  i've set the IP and on the screen it says just browse to it, but i'm still left with:

dial tcp4 10.1.11.48:4979: getsockopt: connection refused

can't browse to the server or get a status of anything.

 

 

---

Subject:	did a little more digging.  i
Author:	[Not Specified]
Posted:	2017-03-20 16:06

did a little more digging.  i believe it's failing because the docker is behind a proxy and can't hit the internet:

 

 

I0320 21:05:18.874409 11793 controlplanedao.go:124] Opening ElasticSearch ControlPlane Dao: hostName=localhost, port=9200
I0320 21:05:18.965886 11793 dfs.go:396] Checking v1 docker registry
I0320 21:05:18.965970 11793 dfs.go:348] Starting local docker registry v1
I0320 21:05:18.967117 11793 dfs.go:618] Creating container cc-temp-registry-v1 from image registry:0.9.1
I0320 21:05:18.969340 11793 api.go:732] Pulling image from repo: registry and registry:  with tag: 0.9.1
E0320 21:06:03.972043 11793 dfs.go:621] Error trying to create container cc-temp-registry-v1: Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/registry/images. You may want to check your internet connection or if you are behind a proxy.
E0320 21:06:03.972105 11793 dfs.go:351] Could not start v1 docker registry at port 5001: Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/registry/images. You may want to check your internet connection or if you are behind a proxy.
time="2017-03-20T21:06:03Z" level=fatal msg="Unable to upgrade internal Docker image registry" error="Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/registry/images. You may want to check your internet connection or if you are behind a proxy." location="daemon.go:534" logger=cli.api
serviced.service: main process exited, code=exited, status=1/FAILURE
Mon Mar 20 21:06:03 UTC 2017: post-stopping serviced daemon - waiting for serviced to stop
Mon Mar 20 21:06:03 UTC 2017: waiting for serviced daemon to stop
Mon Mar 20 21:06:04 UTC 2017: waiting for serviced to stop listening
Mon Mar 20 21:06:04 UTC 2017: waiting for serviced isvcs to stop
59ce7d223295
d086fc7ec8a2
66f4807872de
599f13ed3170
8ba9f33c33dd
6bdb5d781be0
a144e3a64dc5
Mon Mar 20 21:06:06 UTC 2017: serviced is now stopped - done with post-stop
Unit serviced.service entered failed state.