<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 12 (filtered medium)"> <style>  </style>  </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> After adding a fair number of hosts/services based on templates -- all with a number of dependent services -- we're seeing Nagios taking a fair amount of time to start up now. We're using Nagios 3.2.1. Startup times seemed to be in the vicinity of 4 minutes. During that time Nagios chews up 100% of one CPU core and eventually 2 CPU cores, then settles down. I assumed it was time for me to investigate the fast-startup options and deal with at least the dependency checking.<o:p></o:p> <o:p> </o:p> Note that this host in question is the "central" node in a distributed setup so virtually everything it gets is a passive check result.<o:p></o:p> <o:p> </o:p> When I tried starting with '-s', I found that the first block (Object Config Processing Times) went very quickly and then it hung on the second block (Retention Data Times) ran for a while as indicated. Everything else after that seemed to go fairly quickly to my surprise. So apparently, my problem is with retained data.<o:p></o:p> <o:p> </o:p> My relevant nagios.cfg entries are as follows:<o:p></o:p> <o:p> </o:p> retain_state_information=1<o:p></o:p> retention_update_interval=60<o:p></o:p> use_retained_program_state=1<o:p></o:p> use_retained_scheduling_info=1<o:p></o:p> retained_host_attribute_mask=0<o:p></o:p> retained_service_attribute_mask=0<o:p></o:p> retained_process_host_attribute_mask=0<o:p></o:p> retained_process_service_attribute_mask=0<o:p></o:p> retained_contact_host_attribute_mask=0<o:p></o:p> retained_contact_service_attribute_mask=0<o:p></o:p> <o:p> </o:p> So we definitely want to make use of historical data. I see in the config file comment that using retained state may come at the cost of increased startup times. None of the speedup options I see seem to say that they try to help startup time with retained status. Am I stuck? Do I either need to live with the 194-second processing time (and that will go up as we add more hosts/services over time) or do without retained data?<o:p></o:p> <o:p> </o:p> nagios -s output:<o:p></o:p> <o:p> </o:p> Object Config Source: Config files (uncached)<o:p></o:p> <o:p> </o:p> OBJECT CONFIG PROCESSING TIMES (* = Potential for precache savings with -u option)<o:p></o:p> ----------------------------------<o:p></o:p> Read: 0.042305 sec<o:p></o:p> Resolve: 0.008222 sec *<o:p></o:p> Recomb Contactgroups: 0.002196 sec *<o:p></o:p> Recomb Hostgroups: 0.006549 sec *<o:p></o:p> Dup Services: 0.026616 sec *<o:p></o:p> Recomb Servicegroups: 0.289033 sec *<o:p></o:p> Duplicate: 0.012538 sec *<o:p></o:p> Inherit: 0.005349 sec *<o:p></o:p> Recomb Contacts: 0.000000 sec *<o:p></o:p> Sort: 0.000001 sec *<o:p></o:p> Register: 0.076975 sec<o:p></o:p> Free: 0.008261 sec<o:p></o:p> ============<o:p></o:p> TOTAL: 0.478046 sec * = 0.350505 sec (73.32%) estimated savings<o:p></o:p> <o:p> </o:p> <o:p> </o:p> RETENTION DATA TIMES<o:p></o:p> ----------------------------------<o:p></o:p> Read and Process: 194.016362 sec<o:p></o:p> ============<o:p></o:p> TOTAL: 194.016362 sec<o:p></o:p> <o:p> </o:p> <o:p> </o:p> Timing information on configuration verification is listed below.<o:p></o:p> <o:p> </o:p> CONFIG VERIFICATION TIMES (* = Potential for speedup with -x option)<o:p></o:p> ----------------------------------<o:p></o:p> Object Relationships: 0.054524 sec<o:p></o:p> Circular Paths: 0.822133 sec *<o:p></o:p> Misc: 0.005159 sec<o:p></o:p> ============<o:p></o:p> TOTAL: 0.881816 sec * = 0.822133 sec (93.2%) estimated savings<o:p></o:p> <o:p> </o:p> <o:p> </o:p> EVENT SCHEDULING TIMES<o:p></o:p> -------------------------------------<o:p></o:p> Get service info: 0.014405 sec<o:p></o:p> Get host info info: 0.001732 sec<o:p></o:p> Get service params: 0.000013 sec<o:p></o:p> Schedule service times: 0.000801 sec<o:p></o:p> Schedule service events: 0.000461 sec<o:p></o:p> Get host params: 0.000001 sec<o:p></o:p> Schedule host times: 0.000144 sec<o:p></o:p> Schedule host events: 0.000038 sec<o:p></o:p> ============<o:p></o:p> TOTAL: 0.017595 sec<o:p></o:p> <o:p> </o:p> <o:p> </o:p> Projected scheduling information for host and service checks<o:p></o:p> is listed below. This information assumes that you are going<o:p></o:p> to start running Nagios with your current config files.<o:p></o:p> <o:p> </o:p> HOST SCHEDULING INFORMATION<o:p></o:p> ---------------------------<o:p></o:p> Total hosts: 870<o:p></o:p> Total scheduled hosts: 19<o:p></o:p> Host inter-check delay method: SMART<o:p></o:p> Average host check interval: 300.00 sec<o:p></o:p> Host inter-check delay: 15.79 sec<o:p></o:p> Max host check spread: 30 min<o:p></o:p> First scheduled check: Sat Oct 16 23:26:24 2010<o:p></o:p> Last scheduled check: Sat Oct 16 23:28:46 2010<o:p></o:p> <o:p> </o:p> <o:p> </o:p> SERVICE SCHEDULING INFORMATION<o:p></o:p> -------------------------------<o:p></o:p> Total services: 7569<o:p></o:p> Total scheduled services: 34<o:p></o:p> Service inter-check delay method: SMART<o:p></o:p> Average service check interval: 292.94 sec<o:p></o:p> Inter-check delay: 8.62 sec<o:p></o:p> Interleave factor method: SMART<o:p></o:p> Average services per host: 8.70<o:p></o:p> Service interleave factor: 1<o:p></o:p> Max service check spread: 30 min<o:p></o:p> First scheduled check: Sat Oct 16 23:31:16 2010<o:p></o:p> Last scheduled check: Sat Oct 16 23:33:26 2010<o:p></o:p> <o:p> </o:p> <o:p> </o:p> CHECK PROCESSING INFORMATION<o:p></o:p> ----------------------------<o:p></o:p> Check result reaper interval: 2 sec<o:p></o:p> Max concurrent service checks: Unlimited<o:p></o:p> <o:p> </o:p> <o:p> </o:p> PERFORMANCE SUGGESTIONS<o:p></o:p> -----------------------<o:p></o:p> I have no suggestions - things look okay.<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> Thanks<o:p></o:p> <o:p> </o:p> Mark<o:p></o:p> <o:p> </o:p> </div> </body> </html>