do you know how can change the timeout before htdig gives up trying to contact the host?
At 11:44 AM 5/23/2002, Gilles Detillieux wrote: >According to Peter Choe: > > the strange thing is that it indexed some files from that server. but > when > > it reached a certain file, it gave that error. > > > > so, i think the host is up and running, but somewhere along the line, it > > stopped indexing it. > >That is odd. The htdig code simply does a gethostbyname() call before >each connection it has to make to a server, to get the IP address. >I don't know if that function does any IP caching of its own, but in >any case the name server should be caching. If you had a number of >successful name lookups followed by an unsuccessful one, this would seem >to suggest that your name server is overloaded and failed to respond >in time. > >If your name server isn't on your local network, maybe you should try >to find one that is at least closer and/or less overworked so you don't >run into failures like this. You may even want to consider installing >a caching-only name server on your indexing system, which isn't >necessarily as complicated as it sounds. Many OS distributions give >you a pre-packaged set of config files for a caching-only DNS server, >so you just have to install it, make sure it's running, and point your >/etc/resolv.conf to it. > > > At 11:07 AM 5/23/2002, Gilles Detillieux wrote: > > >According to Peter Choe: > > > > when htdig runs to index my website, some directories are not being > > > > indexed. i have a log file and it gives me an: > > > > > > > > unknow host: foo.bar.com host not found. > > > > > > > > after that file, everything else comes up with 'no server running' and > > > > 'unable to contact host'. > > > > > > > > why i am getting this and how can i fix it? > > > > > >The initial error, "Unknown host: ... host not found", indicates that > > >the name lookup for foo.bar.com failed, so htdig was unable to obtain > > >an IP address for it. After any failure to connect to a host, htdig > > >marks that host as "dead" for the duration of the dig, so it's not > > >continually trying to recontact a host that is unlikely to respond. > > >That's why for all subsequent requests for this host, it simply states > > >"no server running". > > > > > >The fix is to make sure the server is up and running again, and the > > >name server for its domain name is responding to name lookups properly, > > >then rerun htdig. > > >-- >Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> >Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ >Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html
