|
|
| Subject: | problems with starting zenoss.core after install |
| Author: | [Not Specified] |
| Posted: | 2015-09-21 08:52 |
I'm getting loads of errors in my serviced logs when trying to start zenoss.core after install
Anyone know what this means
| Subject: | A lot of "no route to host" - |
| Author: | Jan Garaj |
| Posted: | 2015-09-21 10:13 |
A lot of "no route to host" -> Your (docker) networking is probably broken.
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 noticed my iptables does |
| Author: | [Not Specified] |
| Posted: | 2015-09-21 10:22 |
I noticed my iptables does not have any masquerading for docker anymore, and it did previously, anyway to recreate that
| Subject: | I added this: |
| Author: | [Not Specified] |
| Posted: | 2015-09-22 04:15 |
I added this:
iptables -I INPUT 4 -i docker0 -j ACCEPT
and all my links started working..
Cenoss 7 base install
edited interface names to be old eth0 otherwise stock ..
Why do I need to do that
| < |
Previous SSL Configuration |
Next Webpage is not available for Zenoss5 when accessing from CC |
> |