Hi,

I'm testing out your tool and only got this error:

python /usr/local/zenoss/bin/tracepath.py mydevice.dyndns.org
Getting path from localhost to mydevice.dyndns.org...
Traceback (most recent call last):
File "/usr/local/zenoss/bin/tracepath.py", line 30, in ?
path = source.os.traceRoute(destination, [])
AttributeError: 'NoneType' object has no attribute 'os'

Weird isn't? Any clue?

Hi,

I'm using default zenping configuration. Im not touching anything inside the $ZENHOME/etc since the zenoss installed.

Perhaps you can update your code here so I can test the new changes you made.

Okay,

I'm using zenoss 2.2.0. My zenping working as shown by zenoss status, and my zenping config are shown below:

#
# Configuration file for zenping
#
# To enable a particular option, uncomment the desired entry.
#
# Parameter Setting
# --------- -------
#
# Host of zenhub daemon. Default is localhost.,
# default: localhost
#hubhost localhost
#
# Port zenhub listens on.Default is 8789.,
# default: 8789
#hubport 8789
#
# Username for zenhub login. Default is
# admin., default: admin
#hubusername admin
#
# Password for zenhub login. Default is
# zenoss., default: zenoss
#hubpassword zenoss
#
# Name of monitor instance to use for
# configuration. Default is localhost.,
# default: localhost
#monitor localhost
#
# Initial time to wait for a ZenHub connection,
# default: 30
#hubtimeout 30
#
# Logging severity threshold, default: 20
#logseverity 20
#
# override default logging path
#logpath None
#
# config file must define all params (see man)
#configfile None
#
# user to become when running default:zenoss,
# default: zenoss
#uid zenoss
#
# Cycle continuously on cycleInterval
# from zope, default: False
#cycle False
#
# Become a unix daemon, default: False
#daemon False
#
# output log info in html table format,
# default: False
#weblog False
#
# Run under a supervisor which will restart
# it, default: False
#watchdog False
#
# The path to the watchdog reporting socket
#watchdogPath None
#
# wait seconds for initial heartbeat,
# default: 36000
#starttimeout 36000
#
# host that roots the ping dependency
# tree: typically the collecting hosts'
# name; defaults to our fully qualified
# domain name (localhost), default: localhost
# name localhost
#
# Run in test mode: doesn't really ping,
# but reads the list of IP Addresses
# that are up from /tmp/testping, default:
# False
#test False
#
# use the given (privileged) file descriptor
#useFileDescriptor None

Got the conf above from genconf. Then I uncomment:

# host that roots the ping dependency
# tree: typically the collecting hosts'
# name; defaults to our fully qualified
# domain name (localhost), default: localhost
name localhost

And restart zenping. Try again tracepath.py against devices locally and remotely shown:

Locally:

python /usr/local/zenoss/bin/tracepath.py 192.168.3.5
Getting path from localhost to 192.168.3.5...
Traceback (most recent call last):
File "/usr/local/zenoss/bin/tracepath.py", line 30, in ?
path = source.os.traceRoute(destination, [])
AttributeError: 'NoneType' object has no attribute 'os'


Localhost:

python /usr/local/zenoss/bin/tracepath.py localhost
Getting path from localhost to localhost...
Invalid destination.

Remotely:

python /usr/local/zenoss/bin/tracepath.py moddar.homeip.net
Getting path from localhost to moddar.homeip.net...
Traceback (most recent call last):
File "/usr/local/zenoss/bin/tracepath.py", line 30, in ?
path = source.os.traceRoute(destination, [])
AttributeError: 'NoneType' object has no attribute 'os'

The same error for locally and remotely.

Sorry netdata,

I misunderstood of what you say in the first place, which means to put the fqdn for the zenoss server instead of localhost.

Now I getting a little feedback, albeit questionable still.

-------------------------------------

From the output locally:

tracepath.py 192.168.3.6
Getting path from billion.dyndns.org to 192.168.3.6...
zenoss -> -> 192.168.3.6

What's the mean by the missing link between zenoss & 192.168.3.6 ? Maybe the missing link can be replaced by some readable error message.

---------------------------------------

From the output remotely:

tracepath.py korriger.homeip.net
Getting path from billion.dyndns.org to korriger.homeip.net...
Traceback (most recent call last):
File "/usr/local/zenoss/bin/tracepath.py", line 30, in ?
path = source.os.traceRoute(destination, [])
File "/usr/local/zenoss/Products/ZenModel/OperatingSystem.py", line 119, in traceRoute
raise TraceRouteGap("unable to trace to %s, gap at %s" % (target.id,
Products.ZenModel.Exceptions.TraceRouteGap: unable to trace to korriger.homeip.net, gap at billion.dyndns.org

Some error message which seem to cannot trace the routes between source and destination.

-------------------------------------------

Testing between zenoss server and the fqdn of internal server:

tracepath.py viva.mordor.com
Getting path from billion.dyndns.org to viva.mordor.com...
Invalid destination.

tracepath.py 192.168.3.135 (a.k.a viva.mordor.com)
Getting path from billion.dyndns.org to 192.168.3.135...
zenoss -> -> 192.168.3.135

This is all output of what I get from my test. :wink:

I followed the programs instructions and added the name value into the file recommended.

I now get this error:

Traceback (most recent call last):
  File "./tracepath.ph", line 20, in ?
    name, source = line.split(' ')
ValueError: need more than 1 value to unpack

Ok, I figured it out (without knowing Python). Toss out the shell script shown above as all it did was a different trace route.

The problem has nothing to do with the zenping.conf file. It was an issue with us (me) interpreting your (NetData's) suggestions for setting up. Most of confusion came from it echoing the source and destination names then failing.

The Python script does a lookup of the device name in the database and resolves an actual device to a Zenoss device, not an normal trace route. The error 'invalid source' is caused by no object in Zenoss for the Zenoss server its self. I created a new object under Devices/Server/Linux/SLES to represent the actual Zenoss server I was using and all of a sudden I was getting invalid destination. Bingo!

Now all I have to figure out is how to get into Zenoss all the WAN router devices and routing tables that our telco is providing and won't tell us anything about.