On 2003-05-09 18:04 Geoff Hutchison wrote...We get the same problem as mentioned above. This is a really odd situationI set up htdig as usual on a Red Hat Linux AS 2.1 box. It runs fine
via the command line, but when I run it via the web, it's very odd....
Err, I take from this that "htsearch" runs fine via the command line but
not through a CGI.
1. When there are no matches, I get a 500 error.
2. When there are matches, I get a result page showing some results,
but the page is usually truncated, ending right in the middle of a result.
Have you taken a look at the web server error log? Certainly in the case
of #1 above, it will give the output from STDERR in the error log.
As for 2, I'd want a bit more info. It might be a timeout issue. Does your client timeout? How does the page actually end? Have you tried pulling up a browser on the server itself (ideally using localhost)?
and a major bug if I might say. It has nothing to do with timing out
because htdig and webserver are on the same machine. It looks as though
htdig 3.2.0-x has issues with 4K blocks. Is there someone who knows about
this issue and has a patch/solution for this major issue?
Unless I missed some messages, a similar problem has only ever been reported once previously, and there was no response to the request for additional information. The information provided thus far doesn't even make a particularly compelling case for this being an ht://Dig bug. A 500 error can easily result from other configuration issues, and the fact that htsearch runs correctly from the command line tends to point a finger in the direction of the web server.
Can you provide any additional information, such as answers to the questions that were asked the first time around? I don't think that htsearch and the web server being on the same machine has anything to do with whether or not a timeout issue is involved. If something on the server is configured to kill a process after a certain amount of time, the potential for timeout problems exists.
What version of ht://Dig are you using? If you are using the last 3.2 beta release, then you are using something that is very much out of date and known to have a number of problems. If you are using a newer development snapshot of the beta, then knowing the version might be useful. Btw, the 3.2's are all beta and not recommended for production. Unless there are some must-have features in the 3.2 branch, you are probably best off sticking with 3.1.6.
Are you using the same operating system as mentioned in the original post? Are you on Intel hardware, or something else? Have you determined whether the problem is repeatable across multiple versions of ht://Dig? Do you have another machine you could test on to see if the problem is repeatable across multiple machines? Perhaps with different web servers?
There are a number of us using 3.2 betas without running into this particular issue, so it does not appear to be a general ht://Dig problem. It seems that the problem either lies with something other than ht://Dig or that there is something specific to your setup that is tickling a subtle bug in the ht://Dig code.
Jim
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ 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
