TECHZEN Zenoss User Community ARCHIVE  

Zenoss DNS issues and SNMP issues

Subject: Zenoss DNS issues and SNMP issues
Author: [Not Specified]
Posted: 2015-06-25 12:43

Hi,

I have installed 5.0.3 via the control center and I'm having some strange issues. I added our main DNS server to the /etc/defaults/docker file DOCKER_OPTS, and DNS forward and reverse commands work for infrastructure devices. However, when I try to model a device (only SNMP is available) I'm getting the following error:

2015-06-25 17:40:06,264 INFO zen.ZenModeler: plugins: zenoss.snmp.NewDeviceMap, zenoss.snmp.DeviceMap, HPDeviceMap, DellDeviceMap, zenoss.snmp.InterfaceMap, zenoss.snmp.RouteMap, zenoss.snmp.IpServiceMap, zenoss.snmp.HRFileSystemMap, zenoss.snmp.HRSWInstalledMap, zenoss.snmp.HRSWRunMap, zenoss.snmp.CpuMap, HPCPUMap, DellCPUMap, DellPCIMap
Invalid version specified after -v flag:
2015-06-25 17:40:06,266 ERROR zen.ZenModeler: Unable to fill collection slots: [Failure instance: Traceback (failure with no frames): : ('Unable to parse arguments', ['/opt/zenoss/Products/DataCollector/zenmodeler.py', '-v', '', '-c', 'public', '-t', '1', '-r', '5', 'udp:x.x.x.x:161'])

(IP Address replaced by x.x.x.x)

When I try to do an snmpwalk command I get the following error:

snmpwalk -${device/zSnmpVer} -c${device/zSnmpCommunity} x.x.x.x system
getaddrinfo: - Name or service not known
snmpwalk: Unknown host (-)

(IP Address replaced by x.x.x.x)

Why on earth would it try to do a DNS lookup on an ip address

Am I doing something wrong or is this release broken

Please help, thanks in advance.



Subject: Here is your problem http:/
Author: Jan Garaj
Posted: 2015-06-25 15:26

Here is your problem http://www.zenoss.org/forum/10026

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

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



Subject: Yes, edit your Zenoss core
Author: Jan Garaj
Posted: 2015-06-26 18:16

Yes, edit your Zenoss core template e.g. /opt/serviced/templates/zenoss-core-5.0.3_1.json and specify newer version of Zenoss image e.g. instead of "ImageID": "zenoss/core_5.0:5.0.3_1", use "ImageID": "zenoss/core_5.0:5.0.4_152_unstable". Then import template and redeploy your Zenoss instance. It's unstable version, so keep it in your mind - http://i.imgur.com/HTisMpC.jpg :-D

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

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



Subject: When will this be patched? I
Author: [Not Specified]
Posted: 2015-07-01 11:21

When will this be patched I tried that git commit and patched it myself, did a docker commit, rebooted, same exact issue. How can this code make it to production Did they even test this If I was a developer I would be embarrassed to release to production without working snmp. I guess I'm sticking with Nagios.



< Previous
event recieved has oid in summary, eventClassKey and message but MIB is already ...
  Next
Basic install Question .OVA
>