|
|
| Subject: | Zenoss Core 5 - Cannot monitor itself (Resolved) |
| Author: | Ken Jenkins |
| Posted: | 2015-03-27 18:34 |
Zenoss Core 5 - Cannot monitor itself via DNS IP or the master localhost IP
In Core 4 I got this to work by specifying localhost and running a discovery then assigning a device class of /Server/Linux and adding a MySQL Collector plugin to it.
With Core 5 the original IP or localhost fails an SNMP query during discovery.
2015-03-27 23:13:03,809 INFO zen.SnmpClient: Device timed out: SNMP info for zenoss01.xxxx at ::1:161 timeout: 1 tries: 6 version: v2c community: xxxx
2015-03-27 23:13:03,810 INFO zen.SnmpClient: snmp client finished collection for zenoss01.xxxx
2015-03-27 23:13:03,810 WARNING zen.SnmpClient: Device zenoss01.xxxx timed out: are your SNMP settings correct
2015-03-27 23:13:03,811 INFO zen.ZenDisc: No change in configuration detected
2015-03-27 23:13:03,811 INFO zen.ZenDisc: Scan time: 6.11 seconds
2015-03-27 23:13:03,812 INFO zen.ZenDisc: Daemon ZenDisc shutting down
Is there a best practice document to configure Zenoss to monitor itself for Core 5
Help!
Thanks,
Ken
| Subject: | I tried this solution and using the external IP did not work |
| Author: | Ken Jenkins |
| Posted: | 2015-03-27 18:48 |
It sounds like localhost will not work. I tried the solution posted in the forum using the external IP and the snmpwalk still does not work.
http://www.zenoss.org/forum/2391
I can snmpwalk the Zenoss Master via the external IP on the Zenoss Master and from other servers.
Help!,
Thanks,
Ken
Thanks,
Ken Jenkins
| Subject: | Hi Ken, |
| Author: | Matt |
| Posted: | 2015-03-27 20:36 |
Hi Ken,
I got this working by specifying the external IP of the Server in Zenoss (as you already mentioned) and adding the network Docker is using to the snmpd.conf file.
E.g. 172.17.0.0/16
BR Matthias
| < |
Previous zenoss 5 backup error |
Next Zenoss Core 5 - Site Window issues |
> |