According to Rupert Jones: > I've installed ht://dig on a RedHat Linux ES Rel 2.1 machine, (trying both > 3.1.6 and 3.2.0b5), and am getting the following problem: > > Whenever I use a search term which htsearch has no match for, or if I don't > use a search term, I get a 500 Internal Server Error, with the Apache > error_log saying "Premature End of Script Headers" and no other information. > Htsearch otherwise runs fine, bringing up search results on terms that it > -can- find. > > Trying the same search from the command line outputs the raw HTML file, and > everything looks fine; it looks like htsearch is finding the nomatch.html > file and outputting a well-formed HTML document with valid header.
Rupert, it sounds like the problem you're having with htsearch getting internal server errors under Red Hat Enterprise Linux is the same one that Fred Stutzman ([EMAIL PROTECTED]) reported earlier this month: http://sourceforge.net/mailarchive/forum.php?thread_id=3945988&forum_id=2691 Fred didn't report which version of RHEL he was running, but I suspect it might be the same version. On the other hand, it's my understanding that Christopher Murtagh ([EMAIL PROTECTED]) is running htsearch quite successfully on RHEL 3.0, so it may be a problem that's been fixed in their latest release. It might be useful for the 3 of you to compare notes as to what versions your running for gcc, g++, libstdc++, and apache. One of those packages is the likely trouble spot that is causing htsearch's output to "cout" to mysteriously disappear on two of your 3 RHEL systems, when run from apache. Sorry to single you out like this, but we don't have a lot of Enterprise Linux users on this list, that I know of, so I'm hoping you can help each other out. > In lieu of anybody being able to pin-point the problem, does anyone know if > there is a way of getting debugging information from htsearch when > performing the search from the web browser? Probably your best bet would be to try running htsearch from a wrapper shell script, that called htsearch with some -v options and redirected the stderr stream (fd 2) to a file. (e.g. htsearch 2>>logfile) You could then add other tests to this shell script, such as storing the htsearch output in a temporary file and seeing if all of it comes out properly. -- 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) ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ 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
