Feb 2, 2009 3:16 PM
Config cycle and modeler cycle
-
Like (0)
What does " reload their configuration" mean?
Could mean reload the configuration from the zenoss/etc/*.conf files
or it could reread some magic info from the database.
_______________________________________________
zenoss-users mailing list
zenoss-users@zenoss.org
http://lists.zenoss.org/mailman/listinfo/zenoss-users
Can we go around the "Config Cycle" question again? When Chet says "some of the daemons will reload their configuration unless it has been updated asynchronously" - which daemons? I am struggling yet again to get consistency with IP service monitoring and process monitoring and I am wondering if these are the daemons (zenprocess and zenstatus) that may use the config cycle as I sometimes find that configuration in this sort of area suddenly "takes" overnight.
The Event History, for example, has /Change/Set entries like "calling function 'setServiceClass' with '{'protocol': 'udp', 'port': 161}' on object udp_00161" after I was doing stuff with that service during the evening - the event came through at 4:09 (when I certainly wasn't doing stuff) but this time coincides with the "Last Collection" field on each device's status page (which I assumes means the last modeler poll?).
Is it just the modeler poll that is triggering these /Change/Set service / process entries or does the Config Cycle have a roll here? (or anywhere now????).
This is a 2.5 drop 5 beta but I believe it has not changed significantly for yonks.
Cheers,
Jane
Follow Us On Twitter »
|
Latest from the Zenoss Blog » | Community | Products | Services Resources | Customers Partners | About Us | ||
Copyright © 2005-2011 Zenoss, Inc.
|
||||||||