Hi Jim,
I think we found one problem may have been related to our Apache security set up on the web servers. The person who had been responsible for this process left the company and her web account (the one by which htDig was running to create the collections) had been deleted.
I've actually been able to successfully create completely new, "from scratch" collections using my authorized account information, and now everything seems to be working. However, at the same time we decided to re-instate the previous process owner's web account. When we did this, one of the collections which had not been working, started working again.....
So, is there anything related to how the search collections were created (i.e. which Apache-authorized account was used) that would affect htSearch being successful?
Thanks again,
Bruce
| Jim <[EMAIL PROTECTED]>
08/18/2004 06:24 PM
|
To: Bruce DeYoung <[EMAIL PROTECTED]> cc: [EMAIL PROTECTED] Subject: Re: [htdig] HtSearch Command Line Works....CGI Program Does Not |
On Mon, 16 Aug 2004, Bruce DeYoung wrote:
> We have a few existing search collections which no longer work. However, I
> can create a new search collection running htdig and search it just fine
> using HTSEARCH on the unix command line. However, when I push this new
> collection to our web server, and run our search page, I always get "No
> documents found."
>
> Does HTSEARCH get confused if the configuration file on the web server is
> not exactly the same as the one used to create the db's? (We run htdig
It doesn't need to be exactly the same. However there are some important
attributes that must be set appropriately for the server running htsearch.
However if you are receiving a page from htdig that says no matches were
found for the search term, then chances are the configuration file is not
too far off. I am not sure if this is what you mean by "No documents
found."; a default install doesn't provide this exact message, but it is
possible that the page has been customized.
> on a separate server and then copy the new collections dbs to our
> production environment when the process of creating them is done.) Is
Are you sure that the location you place the databases matches the
location specified in the configuration file on the server running
htsearch? It might be that you are not updating the correct databases.
Are the platforms that you use for digging and searching the same? Are you
using the same versions of ht://Dig on both machines?
Jim
