---

Subject:	Same problem..
Author:	[Not Specified]
Posted:	2014-05-09 05:15

Hi, Dpetzel

I can confirm your findings. I've done two separate installations and get exactly the same results. The Control Plane is running fine, all apps are started and the docker that's supposed to forward from port 49159 -> 8080 seems to be running. (My experience with docker is also very limited!)

root@zenoss5:~# docker ps | grep 8080
59512854957c quay.io/zenossinc/zenoss5-core:5.0.0_265 "/serviced/serviced 5 minutes ago Up 5 minutes 0.0.0.0:49159->8080/tcp, 0.0.0.0:49160->8443/tcp, 0.0.0.0:49161->8888/tcp, 0.0.0.0:49162->9180/tcp a3c12974-2b07-4675-327f-785a1180d0cd

But if I check with netstat port 8080 is only listened on ipv6,

# netstat -nat | grep 49159
tcp6 0 0 :::49159 :::* LISTEN

But obviously I can't connect to it on my ipv4 interface.

Btw, I've got everything up and running on the latest Ubuntu LTS with the latest kernel as well with _exactly_ the same result as with 12.4 LTS and the recommended kernel (3.8)

Anyone who can shed some light on this

Thanks!
/Stefan

---

Subject:	Interesting. It appear mine
Author:	[Not Specified]
Posted:	2014-05-09 08:01

Interesting. It appear mine is a little different, as mine is actually listening on IPV4

# docker ps | grep 8080
148ca89cfd84 quay.io/zenossinc/zenoss5-core:5.0.0_265 "/serviced/serviced 8 hours ago Up 8 hours 0.0.0.0:49156->8080/tcp, 0.0.0.0:49157->8443/tcp, 0.0.0.0:49158->8888/tcp, 0.0.0.0:49159->9180/tcp 7895a84b-4896-7da3-0f3b-97ccccdf45e7

---

Subject:	Indeed, but ...
Author:	[Not Specified]
Posted:	2014-05-10 13:15

Yes, mine looks the same. But what happens if you look with netstat Do a "netstat -nat | grep 8080"

---

Subject:	Gentlemen, I can confirm this
Author:	Andrew Kirch
Posted:	2014-05-13 11:09

Gentlemen, I can confirm this as well, that said if you hit 48080 it will work. This is an alpha and the Docker piece is the latest addition. There will be a beta in a few weeks with quite a few areas fleshed out and made much more simple.

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:	Best I can tell from
Author:	[Not Specified]
Posted:	2014-05-13 12:47

Best I can tell from following the port forwards, is that 8080 is not listening at all on the host and 48080 is only listening on IPv6. And sadly between my workstation and this test server IPv6 routing is not enabled. I think this solution might be just telling docker to setup this forward using IPv4 (still trying to figure out how to do that though)

---

Subject:	All services, zope, zenhub,
Author:	[Not Specified]
Posted:	2014-05-16 14:30

All services, zope, zenhub, etc., that are run in docker by Control Plane are assigned a random port. The services are not meant to be accessed directly unless you want to go find out the random port.

Also the main entry point into zenoss is no longer zope. There is a nginx based service called zproxy that handles the routing to zope and the new components that handle metric data.

Control Plane sets up a vhost, zenoss5x, for zenoss and is the way to access zenoss running in the control plane. You should be able to access zenoss5x. to get to zenoss.

---

Subject:	Thanks Jplouis, that is
Author:	[Not Specified]
Posted:	2014-05-16 19:28

Thanks Jplouis, that is useful info and I'd really like to say it solved my problem, but I'm still stuck.

First up the reference of zenoss5x. baffles me. I did that host file entry up per the WIKI but I'm clueless how it actually comes into play since its not a valid DNS entry outside the host (in my case, the machine running docker and all the instances is a separate machine).

Based on your info, it sounds like I'm looking for something (a container) running called zproxy Should it be listening on 8080 (the traditional Zenoss port) or 80 based on your comment above

Is there any info on zproxy that I can look at to help troubleshoot

From my very limited understanding, everything "looks" likes its running, I just can't seem to access it.

---

Subject:	zproxy listens on the
Author:	[Not Specified]
Posted:	2014-05-19 01:39

zproxy listens on the containers 8080 port; docker assigns a random port on the host to port forward to the container port.

If you do docker ps -a it will list all the containers and what ports are being forwarded. You should see something lie 49xxx -> 8080

We are working on features to let you assign an external IP and port to services running in control plane.

---

Subject:	Still no luck and feels a bit
Author:	[Not Specified]
Posted:	2014-05-19 10:09

Still no luck and feels a bit like we came full circle. The forwards seem to be on IPV6 only (which Isn't routable between me and the host I'm using to test this).

Here is what I am seeing:

docker ps -a | grep -i 8080
e2661b22e860 quay.io/zenossinc/zenoss5-core:5.0.0_265 "/serviced/serviced 5 days ago Exited (0) 5 days ago 0.0.0.0:49153->8080/tcp, 0.0.0.0:49154->8443/tcp, 0.0.0.0:49155->8888/tcp, 0.0.0.0:49156->9180/tcp 8da18763-eca6-8326-8a04-77f930d7707c
148ca89cfd84 quay.io/zenossinc/zenoss5-core:5.0.0_265 "/serviced/serviced 10 days ago Exited (0) 5 days ago 0.0.0.0:49156->8080/tcp, 0.0.0.0:49157->8443/tcp, 0.0.0.0:49158->8888/tcp, 0.0.0.0:49159->9180/tcp 7895a84b-4896-7da3-0f3b-97ccccdf45e7
23a621f44a79 quay.io/zenossinc/zenoss5-core:5.0.0_265 "/serviced/serviced 10 days ago Exited (0) 10 days ago 0.0.0.0:49159->8080/tcp, 0.0.0.0:49160->8443/tcp, 0.0.0.0:49161->8888/tcp, 0.0.0.0:49162->9180/tcp 87328585-ee13-7d3a-4294-e1bd4fbb85e4

netstat -anp | grep 49153
tcp6 0 0 :::49153 :::* LISTEN 689/docker
udp6 0 0 :::49153 :::* 689/docker

netstat -anp | grep 49156
tcp6 0 0 :::49156 :::* LISTEN 689/docker

Nothing on 49159

How can I make the installation setup the forwards using IPV4

---

Subject:	facing same issue on the current release
Author:	[Not Specified]
Posted:	2017-02-27 22:07

Hi

Imfacing the same issue on implementing the latest version of Zenoss, I can't find any resolution for that so could you please share on how we can fix this.