From: Rupert J. <ru...@sa...> - 2004-03-18 12:49:59
|
Hi, I've switched from trying to install 3.1.6 to trying the 3.2.0b5 release. I explicitly stated pathnames using options with ./configure, and everything seems to have installed in the right place. I noted I needed to create a symbolic link to the htdig.conf file from the /etc/ directory (all the htdig programs seemed to be looking for it there, regardless of the fact I had set the default conf file to be in the actual location I stored it). I also had to add common_dir to the conf file, as it was referencing this variable, although it wasn't actually set. This has allowed htsearch to find head.html and foot.html in the common directory. Next I built the databases, and the digging seems to have gone alright and succeeded normally. NOW, htsearch runs fine from the command line, but when accessed through the web browser via the form, it returns a 500 Internal Server Error. The Apache error_log does have a bit more meaningful error messages in it, however: WordDB: CDB___memp_cmpr_read: unable to uncompress page at pgno = 1 WordDB: PANIC: Input/output error DB_RUNRECOVERY: Fatal error, run database recovery I don't seem to be able to find any previous posts in the mailing list archive that directly relate to this error. Does anyone have any suggestions? Rupert Jones Save9 Limited Website: http://www.save9.com Telephone: +44 (0)1723 355999 'A stitch in time saves nine' - innovative e-business solutions. CONFIDENTIALITY: Unless otherwise agreed expressly in writing by a director of Save9 Ltd, this Email is to be treated as confidential and the information in it may not be used or disclosed except for the purpose for which it has been sent. If you have reason to believe that you are not the intended recipient of this Email, please contact the sender immediately. WARNING: Computer viruses can be transmitted by Email. The recipient should check this Email and any attachments for the presence of viruses. Save9 Ltd accepts no liability for any damage caused by any virus transmitted by this Email. This Email and any attachments may not be copied or forwarded without express written permission of a director of Save9 Ltd. In the event of any unauthorised copying or forwarding, the recipient will be required to indemnify Save9 Ltd against any claim for loss or damage caused by any viruses or otherwise. DISCLAIMER: Employees of Save9 Ltd are expressly required not to make any defamatory statements and not to infringe or authorise any infringement of copyright or any other legal right by Email communications. Any such communication is contrary to company policy and outside the scope of the employment of the individual concerned. Save9 Ltd will not accept any liability in respect of such a communication, and the employee responsible will be personally liable for any damages or other liability arising. CONTRACTS: No employee or agent is authorised to conclude any binding agreement on behalf of Save9 Ltd with another party by Email without express written confirmation by a director of Save9 Ltd. |
From: Jim <li...@yg...> - 2004-03-27 10:52:28
|
On Thu, 18 Mar 2004, Rupert Jones wrote: > I've switched from trying to install 3.1.6 to trying the 3.2.0b5 release. > I explicitly stated pathnames using options with ./configure, and everything > seems to have installed in the right place. > I noted I needed to create a symbolic link to the htdig.conf file from the > /etc/ directory (all the htdig programs seemed to be looking for it there, > regardless of the fact I had set the default conf file to be in the actual > location I stored it). > I also had to add common_dir to the conf file, as it was referencing this > variable, although it wasn't actually set. This has allowed htsearch to find > head.html and foot.html in the common directory. You said that you are working with a Red Hat server didn't you? Have you checked the system and RPM database to ensure that you don't have all or part of some other ht://Dig install lurking about on the system? The ht://Dig RPMs produced by Red Hat are notoriously troublesome and could certainly result in some strange problems if present. Also, a standard install from source with correct configuration and sufficient privileges should not result in you needing to add symbolic links or immediately add configuration settings. Something doesn't seem quite right here. Jim |