On Mon, 14 Aug 2006, Ralf Hildebrandt wrote: > During indexing, our nagios installation reports that the webserver is > not responding -- generating the index seems to stress the machine to > the point where it doesn't accept any HTTP connections. > > I already added: > server_wait_time: 10
Have you tried running with one or more -v options? That should give you some idea of what htdig is actually doing. If it is hitting the same server name over and over without pause, then that might be a sign that there is some sort of problem with your ht://Dig configuration file. If you haven't already done so, it might be worth manually deleting any existing database files created by htdig before starting a new dig. Have you verified that your web server's MaxClients (or equivalent) setting is high enough to support the extra connections? Long shot to say the least. The only other thing I can think of to suggest is to monitor your server's disk activity while the index is being created. If you have slow disks and/or very large databases, indexing can seriously degrade the responsiveness of the system. Jim ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ ht://Dig general mailing list: <[email protected]> ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-general
