Hi, I've just compiled and installed Ht://Dig 3.1.6 on a RedHat 9 server and I'm having some problems getting it working correctly, sorry if some of my questions are insanely obvious!!
Initially everything looks okay, rundig (and rundig.sh for incremental indexes) seem to run fine, and build the relevent dbs: [common_dir] -rw-r--r-- 1 search 84 Oct 19 12:45 bad_words drwxr-sr-x 2 search 4096 Oct 21 10:41 conf -rw-r--r-- 1 search 923308 Oct 19 12:45 english.0 -rw-r--r-- 1 search 5756 Oct 19 12:45 english.aff -rw-r--r-- 1 search 190 Oct 19 12:45 footer.html -rw-r--r-- 1 search 877 Oct 19 12:45 header.html -rw-r--r-- 1 search 194 Oct 19 12:45 long.html -rw-r--r-- 1 search 1390 Oct 19 12:45 nomatch.html -rw-r--r-- 1 search 2285568 Oct 20 14:15 root2word.db -rw-r--r-- 1 search 67 Oct 19 12:45 short.html -rw-r--r-- 1 search 14481 Oct 19 12:45 synonyms -rw-r--r-- 1 search 90112 Oct 20 14:13 synonyms.db -rw-r--r-- 1 search 1261 Oct 19 12:45 syntax.html -rw-r--r-- 1 search 3022848 Oct 20 14:15 word2root.db -rw-r--r-- 1 search 1087 Oct 19 12:45 wrapper.html [database_dir] -rw-r--r-- 1 search 2048 Oct 20 14:18 db.accents.db -rw-r--r-- 1 search 10362880 Oct 21 12:01 db.docdb -rw-r--r-- 1 search 10362880 Oct 21 10:41 db.docdb.work -rw-r--r-- 1 search 2048 Oct 21 10:41 db.docs.index -rw-r--r-- 1 search 2048 Oct 20 14:18 db.metaphone.db -rw-r--r-- 1 search 2048 Oct 20 14:18 db.soundex.db -rw-r--r-- 1 search 104323392 Oct 21 12:01 db.wordlist -rw-r--r-- 1 search 1308 Oct 21 10:41 db.wordlist.work -rw-r--r-- 1 search 4096 Oct 21 10:41 db.words.db But htsearch returns "No matches found" for any search word, this occurs both from the command line and from a web browser: ]# ./htsearch -vvv -d words=iraq tempWords: 'iraq:0 ' Boolean: 'iraq:0 ' initial: '' Fuzzy on: iraq exact iraq synonyms endings word=iraq prefix_suffix=* prefix_suffix_length=1 minimum_prefix_length=1 prefix searchWords: 'iraq:0 ' LogicalWords: iraq Pattern: iraq Content-type: text/html <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html><head><title>No match for 'iraq'</title></head> <body bgcolor="#eef7ff"> <h1><img src="/htdig/htdig.gif" alt="ht://Dig"> Search results</h1> <hr noshade size="4"> <h2>No matches were found for 'iraq'</h2> <p> Check the spelling of the search word(s) you used. If the spelling is correct and you only used one word, try using one or more similar search words with "<strong>Any</strong>." </p><p> If the spelling is correct and you used more than one word with "<strong>Any</strong>," try using one or more similar search words with "<strong>Any</strong>."</p><p> If the spelling is correct and you used more than one word with "<strong>All</strong>," try using one or more of the same words with "<strong>Any</strong>."</p> <hr noshade size="4"> <form method="get" action=""> <font size="-1"> <input type="hidden" name="config" value=""> <input type="hidden" name="restrict" value=""> <input type="hidden" name="exclude" value=""> Match: <select name="method"> <option value="and" selected>All <option value="or">Any <option value="boolean">Boolean </select> Format: <select name="format"> <option value="builtin-long">Long <option value="builtin-short">Short </select> Sort by: <select name="sort"> <option value="score" selected>Score <option value="time">Time <option value="title">Title <option value="revscore">Reverse Score <option value="revtime">Reverse Time <option value="revtitle">Reverse Title </select> <br> Refine search: <input type="text" size="30" name="words" value="iraq"> <input type="submit" value="Search"> </font> </form> <hr noshade size="4"> <a href="http://www.htdig.org/";> <img src="/htdig/htdig.gif" border="0" alt="">ht://Dig 3.1.6</a> </body></html> The word definately exists within the indexes, as a grep will show (too many to list in db.wordlist!) I have checked Apache config, and I dont think its that (also, no errors in error_log), and I cant see anything wrong with my htdig.conf HtDig config file: # # Example config file for ht://Dig. # # This configuration file is used by all the programs that make up ht://Dig. # Please refer to the attribute reference manual for more details on what # can be put into this file. (http://www.htdig.org/confindex.html) # Note that most attributes have very reasonable default values so you # really only have to add attributes here if you want to change the defaults. # # What follows are some of the common attributes you might want to change. # # # Specify where the database files need to go. Make sure that there is # plenty of free disk space available for the databases. They can get # pretty big. # database_dir: /home/applications/wmasearch/var/db # # This specifies the URL where the robot (htdig) will start. You can specify # multiple URLs here. Just separate them by some whitespace. # The example here will cause the ht://Dig homepage and related pages to be # indexed. # You could also index all the URLs in a file like so: # start_url: `${common_dir}/start.url` # #start_url: http://www.htdig.org/ start_url: http://delilah.dev.wmrc.com/search/getChangedIDs.asp?dateFrom=2004-01-01+00: 00:00 # # This attribute limits the scope of the indexing process. The default is to # set it to the same as the start_url above. This way only pages that are on # the sites specified in the start_url attribute will be indexed and it will # reject any URLs that go outside of those sites. # # Keep in mind that the value for this attribute is just a list of string # patterns. As long as URLs contain at least one of the patterns it will be # seen as part of the scope of the index. # limit_urls_to: http://delilah.dev.wmrc.com # # If there are particular pages that you definitely do NOT want to index, you # can use the exclude_urls attribute. The value is a list of string patterns. # If a URL matches any of the patterns, it will NOT be indexed. This is # useful to exclude things like virtual web trees or database accesses. By # default, all CGI URLs will be excluded. (Note that the /cgi-bin/ convention # may not work on your web server. Check the path prefix used on your web # server.) # exclude_urls: /cgi-bin/ .cgi /servlet/ # # Since ht://Dig does not (and cannot) parse every document type, this # attribute is a list of strings (extensions) that will be ignored during # indexing. These are *only* checked at the end of a URL, whereas # exclude_url patterns are matched anywhere. # bad_extensions: .wav .gz .z .sit .au .zip .tar .hqx .exe .com .gif \ .jpg .jpeg .aiff .class .map .ram .tgz .bin .rpm .mpg .mov .avi .css # # The string htdig will send in every request to identify the robot. Change # this to your email address. # #maintainer: [EMAIL PROTECTED] maintainer: [EMAIL PROTECTED] # # The excerpts that are displayed in long results rely on stored information # in the index databases. The compiled default only stores 512 characters of # text from each document (this excludes any HTML markup...) If you plan on # using the excerpts you probably want to make this larger. The only concern # here is that more disk space is going to be needed to store the additional # information. Since disk space is cheap (! :-)) you might want to set this # to a value so that a large percentage of the documents that you are going # to be indexing are stored completely in the database. At SDSU we found # that by setting this value to about 50k the index would get 97% of all # documents completely and only 3% was cut off at 50k. You probably want to # experiment with this value. # Note that if you want to set this value low, you probably want to set the # excerpt_show_top attribute to false so that the top excerpt_length characters # of the document are always shown. # max_head_length: 10000 # # To limit network connections, ht://Dig will only pull up to a certain limit # of bytes. This prevents the indexing from dying because the server keeps # sending information. However, several FAQs happen because people have files # bigger than the default limit of 100KB. This sets the default a bit higher. # (see <http://www.htdig.org/FAQ.html> for more) # max_doc_size: 20000000 # # Most people expect some sort of excerpt in results. By default, if the # search words aren't found in context in the stored excerpt, htsearch shows # the text defined in the no_excerpt_text attribute: # (None of the search words were found in the top of this document.) # This attribute instead will show the top of the excerpt. # no_excerpt_show_top: true # # Depending on your needs, you might want to enable some of the fuzzy search # algorithms. There are several to choose from and you can use them in any # combination you feel comfortable with. Each algorithm will get a weight # assigned to it so that in combinations of algorithms, certain algorithms get # preference over others. Note that the weights only affect the ranking of # the results, not the actual searching. # The available algorithms are: # accents # exact # endings # metaphone # prefix # soundex # substring # synonyms # By default only the "exact" algorithm is used with weight 1. # Note that if you are going to use the endings, metaphone, soundex, accents, # or synonyms algorithms, you will need to run htfuzzy to generate # the databases they use. # search_algorithm: exact:1 synonyms:0.1 endings:0.1 prefix:0.1 spelling:0.1 # # The following are the templates used in the builtin search results # The default is to use compiled versions of these files, which produces # slightly faster results. However, uncommenting these lines makes it # very easy to change the format of search results. # See <http://www.htdig.org/hts_templates.html> for more details. # # template_map: Long long ${common_dir}/long.html \ # Short short ${common_dir}/short.html \ # XML xml ${common_dir}/xml.html # template_name: xml # # The following are used to change the text for the page index. # The defaults are just boring text numbers. These images spice # up the result pages quite a bit. (Feel free to do whatever, though) # next_page_text: <img src="/htdig/buttonr.gif" border="0" align="middle" width="30" height="30" alt="next"> no_next_page_text: prev_page_text: <img src="/htdig/buttonl.gif" border="0" align="middle" width="30" height="30" alt="prev"> no_prev_page_text: page_number_text: '<img src="/htdig/button1.gif" border="0" align="middle" width="30" height="30" alt="1">' \ '<img src="/htdig/button2.gif" border="0" align="middle" width="30" height="30" alt="2">' \ '<img src="/htdig/button3.gif" border="0" align="middle" width="30" height="30" alt="3">' \ '<img src="/htdig/button4.gif" border="0" align="middle" width="30" height="30" alt="4">' \ '<img src="/htdig/button5.gif" border="0" align="middle" width="30" height="30" alt="5">' \ '<img src="/htdig/button6.gif" border="0" align="middle" width="30" height="30" alt="6">' \ '<img src="/htdig/button7.gif" border="0" align="middle" width="30" height="30" alt="7">' \ '<img src="/htdig/button8.gif" border="0" align="middle" width="30" height="30" alt="8">' \ '<img src="/htdig/button9.gif" border="0" align="middle" width="30" height="30" alt="9">' \ '<img src="/htdig/button10.gif" border="0" align="middle" width="30" height="30" alt="10">' # # To make the current page stand out, we will put a border around the # image for that page. # no_page_number_text: '<img src="/htdig/button1.gif" border="2" align="middle" width="30" height="30" alt="1">' \ '<img src="/htdig/button2.gif" border="2" align="middle" width="30" height="30" alt="2">' \ '<img src="/htdig/button3.gif" border="2" align="middle" width="30" height="30" alt="3">' \ '<img src="/htdig/button4.gif" border="2" align="middle" width="30" height="30" alt="4">' \ '<img src="/htdig/button5.gif" border="2" align="middle" width="30" height="30" alt="5">' \ '<img src="/htdig/button6.gif" border="2" align="middle" width="30" height="30" alt="6">' \ '<img src="/htdig/button7.gif" border="2" align="middle" width="30" height="30" alt="7">' \ '<img src="/htdig/button8.gif" border="2" align="middle" width="30" height="30" alt="8">' \ '<img src="/htdig/button9.gif" border="2" align="middle" width="30" height="30" alt="9">' \ '<img src="/htdig/button10.gif" border="2" align="middle" width="30" height="30" alt="10">' # local variables: # mode: text # eval: (if (eq window-system 'x) (progn (setq font-lock-keywords (list '("^#.*" . font-lock-keyword-face) '("^[a-zA-Z][^ :]+" . font-lock-function-name-face) '("[+$]*:" . font-lock-comment-face) )) (font-lock-mode))) # end: How can I confirm that htdig is building the indexes correctly, and that htsearch correctly uses them?? I've tried to put all relevant info in this email, hope it helps! Thanks for any advice, Michael. This email, and any attachment, is confidential to the addressee. If you have received this email and are not an authorised recipient please notify the sender and delete this message from your system. If you are not an authorised recipient you must not use, disclose, distribute, copy, print or rely on this email. Email transmission cannot be guaranteed to be secure, error-free or virus-free. Although World Markets Research Centre ("WMRC plc") routinely screens for viruses you are responsible for checking this email and any attachments for viruses and WMRC plc accepts no responsibility for any damage caused to your systems or for loss of data caused by any virus. WMRC plc does not accept liability resulting from errors or omissions in the content of this message following email transmission. If verification is required please request a hard copy version. If this email is of a personal nature any views expressed are solely those of the author and are not made in the course of the author's employment with WMRC. ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ 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
