TECHZEN Zenoss User Community ARCHIVE  

Zenoss Core 5 installed but inaccessible

Subject: Zenoss Core 5 installed but inaccessible
Author: [Not Specified]
Posted: 2016-02-24 05:52

Hi guys,

i write here after several attemps of zenoss installation by ova image, autodeploy and manual installation. In all of these case i could always login to Control Center and start my Zenoss.core application, but from my remote machine i can't access to zenoss application at https://zenossmasterIP:8080 or http://zenossmasterIP:8080


This is my controlcenterHost server setting :

6 vCPU
32 GB Memory

Ubuntu 14.04.2 LTS

Type      Size  Mounted on
ext4      150GB /
ext4      40GB  /opt/serviced/var
ext4      40GB  /var/lib/docker
ext4      2GB   /opt/serviced/var/backups 
btrfs     2GB   /opt/serviced/var/volumes
swap      32GB  /swap
docker0   Link encap:Ethernet  HWaddr 02:42:00:56:6a:3e  
inet addr:172.17.42.1  Bcast:0.0.0.0  Mask:255.255.0.0
inet6 addr: fe80::42:ff:fe56:6a3e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:694734 errors:0 dropped:0 overruns:0 frame:0
TX packets:732905 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1164103437 (1.1 GB)  TX bytes:318592735 (318.5 MB)

eth0      Link encap:Ethernet  HWaddr 00:50:56:ac:04:a4  
inet addr:172.22.100.2  Bcast:172.22.255.255  Mask:255.255.0.0
inet6 addr: fe80::250:56ff:feac:4a4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:77490 errors:0 dropped:0 overruns:0 frame:0
TX packets:44991 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:85484400 (85.4 MB)  TX bytes:9376343 (9.3 MB)

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         172.22.1.251    0.0.0.0         UG    0      0        0 eth0
172.17.0.0      *               255.255.0.0     U     0      0        0 docker0
localnet        *               255.255.0.0     U     0      0        0 eth0

root       884     1  3 17:37         00:01:46 /usr/bin/docker daemon -s devicemapper --dns=172.17.42.1

NAME                   ID                             STATUS       UPTIME                HOST              IN_SYNC      DOCKER_ID
Zenoss.core          9xkbu9mjbktov5abyw3gwwqgc      Running      44m29.849824605s      zenossmaster      Y            53ac0b1d3452

During the last manual installation i had a problem with quilt.txt because the zenoss container could not resolve links of the offical guide because it had't a google dns in /etc/resolv.conf, i've exec all .txt commands manually in the container, for the rest of installation i followed the instructions propertly

This is what i've try to do for accessing Zenoss application :

root@zenossmaster:# serviced service attach Zenoss.core

[root@53ac0b1d3452 /]# iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 8080 -j DNAT --to 172.17.0.56:8080


After forwarding port 8080 of Zenoss.core application to localhost:8080 this happens when i open http://172.22.100.2:8080 by my remote machine :

Automatic redirect to:

https://172.22.100.2:8080/zport/acl_users/cookieAuthHelper/login_formcame_from=https%3A//172.22.100.2%3A8080/zport/dmd/

with this error :


An error occurred during a connection to 172.22.100.2:8080. SSL received a record that exceeded the maximum permissible length. (Error code: ssl_error_rx_record_too_long)

This is the result or lynx query in Zenoss.core container :

[root@53ac0b1d3452 /]# lynx localhost:8080

Looking up localhost first
Looking up localhost:8080
Making HTTP connection to localhost:8080
Sending HTTP request.
HTTP request sent; waiting for response.
HTTP/1.1 302 Moved Temporarily
'A'lways allowing from domain 'localhost'.
Data transfer complete
HTTP/1.1 302 Moved Temporarily
Location URL is not absolute.
Using http://localhost:8080/zport/dmd/
Looking up localhost:8080
Making HTTP connection to localhost:8080
Sending HTTP request.
HTTP request sent; waiting for response.
HTTP/1.1 302 Moved Temporarily
Data transfer complete
HTTP/1.1 302 Moved Temporarily
Using https://localhost:8080/zport/acl_users/cookieAuthHelper/login_formcame_from=https%3A//localhost%3A8080/zport/dmd/
Looking up localhost:8080
Making HTTPS connection to localhost:8080
Retrying connection without TLS.
Looking up localhost:8080
Making HTTPS connection to localhost:8080
Alert!: Unable to make secure connection to remote host.

lynx: Can't access startfile http://localhost:8080/

Someone can helpme Do you need more informations

Thx



Subject: [root@53ac0b1d3452 /]#
Author: Jan Garaj
Posted: 2016-02-24 13:46

[root@53ac0b1d3452 /]# iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 8080 -j DNAT --to 172.17.0.56:8080

You are hacking system and that's your problem. This is not old Zenoss4 anymore. You are skipping some component/layers with this hack - it's not officialy supported setup. Follow official doc or you hack it more.

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

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



< Previous
Zenoss Core 4.2.5 installation problem
  Next
Google map locations not showing for other users
>