According to Jason Hellwege: > Hi, I asked about this problem a week back. I've now tried all the > solutions people offered, but my problm is still with me: > > ================== > I'm trying to get 3.2.0b4 running (111101 snapshot) on a box running > Solaris 2.6 using Netscape Enterprise as the webserver. > > - htDig has compiled fine. > - rundig has built its databases OK > - running htsearch from the command line works > and produces the HTML output I expected > - trying to run htsearch from the web fails with "Server Error" > the server's error log only reports: > "program terminated without a valid CGI header." > - I've swapped my old 3.1.5 installation in place of the 3.2 > directory and have successfully run it from the web, so > it doesn't appear to be a webserver config problem > - I've checked the permissions for 3.2 and all looks OK > =================== > > The suggested fixes which I've tried are: > > - have a look at the web server's error log > (nothing helpful there, just "program terminated > without a valid CGI header") > - Try reconfiguring with --disable-shared and see > if that fixes the problem. > - Set the LD_RUN_PATH environment variable during compile > to the directory where libstdc++.so.2.8.1.1 lives > > Unfortunatly, I'm still stuck with the same error, and I don't have any > useful error messages to guide me. > > Any suggestions for what I can try next?
Try running with -vvvv from the browser, e.g.: http://your.domain/cgi-bin/htsearch?-vvv+words=test and see if anything useful comes out. Also look around for a core dump file in case that's what's happening. If it fails right away, it isn't likely a problem with the timeout, but if it hangs for 5 minutes before failing, the failure is triggered by the alarm() call in htsearch/htsearch.cc (main). Of course, a proper search should never take that long, so there'd be something very wrong with your databases which would cause htsearch to get stuck like that. However, increasing the timeout may help get to the bottom of things. It would certainly be wierd for a database problem like that to show up only when run from the browser, though. Another thing that might be worth trying is to run htsearch from a CGI wrapper script that saves htsearch's stderr output to a file, just in case the Netscape web server isn't properly saving and logging this output. -- Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil Dept. Physiology, U. of Manitoba Phone: (204)789-3766 Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930 _______________________________________________ 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
