I really wish I could be more descriptive in the title but I am afraid it would make a very long title at best and be confusing at worst. For starters I am using the following: SLES 9.3 Nagios: 2.10 Nagios Plugins: 1.4.9 NDOUtils: 14b6 NagiosQL: 2.00 NagVis: 1.1 My first problem, and I am not sure it is actually a problem, is that when I do a reload of nagios (/etc/init.d/nagios reload) it takes, what seems to me to be, a long time. It is usually around 90-120 seconds for Nagios to start allowing use of the web interface once the reload is initiated. A check of the files reveals no errors (save one warning for a host with no services) and the nagios process shows in a ps awux list. However the web interface shows the "Whoops! Error: Could not read host and service status information!" during the 90-120 second delay I mentioned earlier. Here is a tail of the logfile for the shutdown and restart: Nov 16 15:16:19 ulapnag01 nagios: ndomod: Shutdown complete. Nov 16 15:16:19 ulapnag01 nagios: Event broker module '/usr/local/nagios/bin/ndomod.o' deinitialized successfully. Nov 16 15:16:19 ulapnag01 nagios: Nagios 2.10 starting... (PID=5582) Nov 16 15:16:19 ulapnag01 nagios: LOG VERSION: 2.0 Nov 16 15:16:19 ulapnag01 nagios: ndomod: NDOMOD 1.4b6 (09-27-2007) Copyright (c) 2005-2007 Ethan Galstad (nagios@nagios.org) Nov 16 15:16:19 ulapnag01 nagios: ndomod: Successfully connected to data sink. 0 queued items to flush. Nov 16 15:16:19 ulapnag01 nagios: Event broker module '/usr/local/nagios/bin/ndomod.o' initialized successfully. Nov 16 15:16:19 ulapnag01 ndo2db: Successfully connected to MySQL database Nov 16 15:16:19 ulapnag01 ndo2db: Successfully disconnected from MySQL database Nov 16 15:16:19 ulapnag01 nagios: Warning: Host 'qs105f7pm' has no services associated with it! We are monitoring: <a href="http://ulapnag01/nagios/cgi-bin/status.cgi?host=all&serviceprops=131072"># Active Host / Service Checks:</a><a href="http://ulapnag01/nagios/cgi-bin/status.cgi?hostgroup=all&hostprops=131072&style=hostdetail">272</a> / <a href="http://ulapnag01/nagios/cgi-bin/status.cgi?host=all&serviceprops=131072">329</a> This doesn't seem like enough to bog down a Dell PowerEdge 1855 with 2GB RAM onboard. Any and all help would be appreciated. I have been banging my head against the wall on this one. I have tried searching cannot seem to find these symptoms anywhere. I am being pressured to put this system into production but would prefer to have it restart as quickly as the current production system (never have had any lag reloading) so that I don't have to schedule daily restarts to test changes as they are being requested fast and furious. I apologize if I have over explained. Thanks in advance for any help! Best Regards, Mark L. Potter Systems Engineer Academy Sports & Outdoors