I would guess that it doesn't like the sub network. Either run on the
entire 172.20 (ick) or delete 172.20.3 and readd it as it's own /24
.Jason
The place where you made your stand never mattered,
only that you were there... and still on your feet
rscrane wrote:
Trying to run zendisc on subnet yields the following:
zendisc run --add-inactive --logpath=/usr/local/zenoss/log --net 172.20.3.0
INFO:zen.ZenDisc:loading collector plugins
from:/usr/local/zenoss/Products/DataCollector/plugins
ERROR:zen.ZenDisc:Error performing net discovery on network 172.20.3.0 not
found in dmd
Traceback (most recent call last):
File "/usr/local/zenoss/Products/DataCollector/zendisc.py", line 174, in run
raise SystemExit("network %s not found in dmd" % net)
SystemExit: network 172.20.3.0 not found in dmd
a) can't find anything describing "dmd"
b) subnet is defined on the Networks page as
/Networks /172.20.0.0 /172.20.3.0
Can anyone tell me what problem is?
Have tried a variety of values for --net and all produce the same error;
running as root, tried it without --net and it appears to be running,
attempting to process all 65K addresses; since I have a very sparsely populated
large network I wanted to avoid that.
------------------------
Richard Crane
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=6729#6729
-------------------- m2f --------------------
_______________________________________________
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
