After over two years of trouble-free use of htDig (v 3.1.6),
I have run into an odd problem I don't understand. I hope
someone can point me in the right direction.
The way I run my site is this: I have a test site on a machine
in my office. I update my site files, then re-run the dig on
this machine; then, after testing locally, I copy the updated
files (including the updated db files) to the web server. Both
machines running Windows 2K.
This has worked successfully for over two years, and with
three different websites. For this particular site, it worked
as recently as 5 days ago, when I did the last update.
Today, I updated some files, re-ran the dig, and tested
locally. Fine. Updated the files on the web server, tested the
search, and got the following CGI errors:
========================================================
CGI Error
The specified CGI application misbehaved by not returning a complete set
of HTTP headers. The headers it did return are:
3 [main] htsearch 4892 handle_exceptions: Exception:
STATUS_ACCESS_VIOLATION
398 [main] htsearch 4892 open_stackdumpfile: Dumping stack trace to
htsearch.exe.stackdump
========================================================
(no such stackdump file is created, however).
Tested a few more times, and got two other results: sometimes,
I get a CGI timeout; other times -- particularly when I search for
a term that will return only a few (less than 10) results, I get
the search results page complete with the line that tells me how
many results were returned, but without the actual results.
Also, when I search for terms that are not there, or do an
incorrectly-formatted boolean search, I get the appropriate
results page.
We are guessing (hoping?) that this is a problem outside of htDig:
networking maybe? but I don't know enough about what kind of
data htDig is expecting that it's not getting to be sure. It does seem
as if the search executable is running, but something is happening
to the data on the return trip? The web server is in a building
remote from ours.
If anyone has any ideas on what may be going wrong, we'd greatly
appreciate hearing them. We don't own the web server, and we'd like
to have some notion of where the problem might be before we contact
the person who does (since this person will know nothing about htDig).
Many thanks --
Kyle Dallaire
The information contained in this message is proprietary of Amdocs,
protected from disclosure, and may be privileged.
The information is intended to be conveyed only to the designated recipient(s)
of the message. If the reader of this message is not the intended recipient,
you are hereby notified that any dissemination, use, distribution or copying of
this communication is strictly prohibited and may be unlawful.
If you have received this communication in error, please notify us immediately
by replying to the message and deleting it from your computer.
Thank you.
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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
