Seems like an OK workaround, but I'm not really sure that doing what you
did is *wrong*. Maybe a bug report ought to be submitted?
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University
coyote wrote:
Found the problem, the status host was set to the FQDN of the Zenoss server
instead of localhost host. This was set to the FQDN of the Zenoss server
because I am going to deploy Zenoss satellite servers through the world. My
departments autoload script was setting the status host, now called collector,
to the FQDN of the Zenoss server.
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=22604#22604
-------------------- 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
