![]() |
![]() |
Subject: | AWS EC2 Installation |
Author: | [Not Specified] |
Posted: | 2015-12-29 09:40 |
I have been trying for the past week and a half to figure out how to get Zenoss Core 5 to run successfully on m4.2xlarge AWS EC2 server. The server is created with a root directory of 40GB along with 4 additional hard drives of 40GB if I am doing the auto-deploy script or 2 80GB hard drives if I am doing the manual installation. Each time I can get to the Control Center and I can start Zenoss Core 5 from the Control Center but I can not access Zenoss Core itself.
My /etc/hosts file looks like this:
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
172.31.52.63 ip-172-31-52-63.ec2.internal
52.2.119.157 ip-172-31-52-63.ec2.internal hbase.ip-172-31-52-63.ec2.internal opentsdb.ip-172-31-52-63.ec2.internal .....
I am fairly certain I have followed all the instructions correctly but I still can not access Zenoss Core itself. Is it possible to access Zenoss Core even though I have installed Zenoss on an AWS EC2 server I really hope someone can help!
Subject: | "My /etc/hosts" - pls define |
Author: | Jan Garaj |
Posted: | 2015-12-29 11:05 |
Devops Monitoring Expert advice:
Dockerize/automate/monitor all the things.
DevOps stack:
Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform /
Elasticsearch
Subject: | That file is defined on the |
Author: | [Not Specified] |
Posted: | 2015-12-29 11:08 |
That file is defined on the EC2 instance.
Subject: | Nope. Edit hosts file on your |
Author: | Jan Garaj |
Posted: | 2015-12-29 11:12 |
Devops Monitoring Expert advice:
Dockerize/automate/monitor all the things.
DevOps stack:
Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform /
Elasticsearch
Subject: | Wow, okay I am getting |
Author: | [Not Specified] |
Posted: | 2015-12-29 11:20 |
Wow, okay I am getting somewhere. Thank you for correcting my ignorance. As you can tell I am very new to this.
< |
Previous Monitoring in zenoss 4.2.5 |
Next Can't Access Zenoss Core 5 |
> |