I had the same problem on CentOS. When I sniffed the traffic, I noticed that
ICMP echo request to the localhost was responded with the fully qualified name
-- causing Zenoss to think that the device name is different.
With a small code change I could fix the problem:
$ZENHOME/Products/ZenStatus/AsyncPing.py (Original):
Code:
if pingJob.hostname != current.hostname:
raise IpConflict("Conflict: Host %s and %s are both using
ip %s" %
(pingJob.hostname,
current.hostname,
pingJob.ipaddr))
$ZENHOME/Products/ZenStatus/AsyncPing.py (Fixed):
Code:
if pingJob.hostname != current.hostname:
if socket.getfqdn(pingJob.hostname) != current.hostname:
raise IpConflict("Conflict: Host %s and %s are both
using ip %s" %
(pingJob.hostname,
current.hostname,
pingJob.ipaddr))
As you can see, I made the code to check if the current device name matches
with the fully qualified name of the pinged device and skip the IpConflict.
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=13614#13614
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
