Hi Sascha,
Try running zenping with debugging:
$ zenping run -v 10
If you can determine what kind of device is sending you the bad ping,
please let us know.
If you add:
plog.debug('pkt' + `data`)
After this line (around line 140) of Products/ZenStatus/AsyncPing.py
if not data: return
So the result looks like this:
if not data: return
plog.debug('pkt: ' + `data`)
ipreply = ip.Packet(data)
This will print out the ping packet in a format that we can use to
diagnose why the packet is bad.
-Eric
Sascha Luck wrote:
Hi all,
has anyone seen this one:
2007-01-01 17:47:20 ERROR zen.Ping: receiving packet error:
^K^@<FE><92>[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL
PROTECTED]@^A^AD<EE>
[<8E>n^CT<CB><DB>[EMAIL PROTECTED]<CE><FA>^G^@
Traceback (most recent call last):
File "/usr/local/zenoss/Products/ZenStatus/AsyncPing.py", line 142, in
recvPackets
icmppkt = icmp.Packet(ipreply.data)
File "/usr/local/zenoss/Products/ZenStatus/icmp.py", line 48, in
__init__
self.__disassemble(packet, cksum)
File "/usr/local/zenoss/Products/ZenStatus/icmp.py", line 85, in
__disassemble
raise ValueError, packet
ValueError:
^K^@<FE><92>[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL
PROTECTED]@^A^AD<EE>[<8E>n^CT<CB><DB>[EMAIL PROTECTED]<CE><FA>^G^@
This is the trunk as of 30/12/06...
Thanks and a Happy New Year,
Sascha Luck
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
