Frequently Asked Questions

• How can I contribute to the project?

  There are several ways you can help. Please visit Help Us page on mnoGoSearch website.

• If I have pages with no keywords in the META description, will the document get indexed?

  Yes. By default mnoGoSearch does index whole document. By changing the default values you can give different weights to different parts of the document: body, title, keywords, description.

• When searching words in Spanish (accentuated characters) with search.cgi I get results like the following: If I search for Espaсa, search.cgi breaks the word in two parts, searching for Espa and also for a, ignoring с.

  Set local charset to 8859-1 in both indexer.conf and search.htm.

• I'm wondering if mnoGoSearch supports multi-byte char code sets. I'm especially interested in EUC-JP.

  3.1.x branch hasn't multi-byte charsets. Multi-byte supported in 3.2.x branch.

• Why indexer fails with the message like indexer: can't load library 'libmysqlclient.so.6'?

  You probably don't have MySQL libraries properly installed. On Linux just find out where is your libmysqlclient.so.6 and enter the path to that file to /etc/ld.so.conf. Then run ldconfig as root.

  You can as well set up the value of environment variable LD_LIBRARY_PATH with the path to required dynamic libraries. This works on any OS

  Note that this is a general UNIX configuration issue, not only mnoGoSearch specific.

• What is the maximum size of server(s) mnoGoSearch can run with?

  Cache storage mode, introduced in 3.1.x, is able to index and search through several millions documents.

• I want to index multiple virtual domains on a single box. What settings do I need to change for that?

  It is fully supported. No additional settings are required.

• Is it possible to use different templates for searches, i.e. view search results in the design of different sites without having to recompile search.cgi?

  There are actually several ways to do it. They are given here in the order how search.cgi detects template name.

  1. search.cgi checks environment variable UDMSEARCH_TEMPLATE. Thus you can enter a path to desired search template into this variable.

  2. search.cgi also supports Apache internal redirect. It checks REDIRECT_STATUS and REDIRECT_URL environment variables. To activate this template option you may add these lines to Apache srm.conf:

     AddType text/html .zhtml AddHandler zhtml .zhtml Action zhtml /cgi-bin/search.cgi

     Put search.cgi into your /cgi-bin/ directory. Then put HTML template into your site directory structure under any name with .zhtml extension, for example template.zhtml. Now you may open search page: http://www.site.com/path/to/template.zhtml Of course you may use any available extension instead of .zhtml.

  3. If the above two ways fail, search.cgi will open a template which has the same name with the script being executed using SCRIPT_NAME environment variable. search.cgi will open a template ETC/search.htm, search1.cgi will open ETC/search1.htm and so on, where ETC is mnoGoSearch /etc directory (usually /usr/local/mnogosearch/etc). So, you can use the same search.cgi with different templates without having to recompile it. Just create one or several hard or symbolic links for search.cgi or copy it under different names then put correspondent search templates into /etc directory of mnoGoSearch installation.

• Indexer doesn't store some links in database that are expected to be stored. Indexer doesn't grab all the links from my web site, as a result only half the site is indexed.

  There are two reasons are possible:

  1. Indexer doesn't find links on the page. This is probably a bug in HTML parser in this case.

  2. Indexer does find links, but rejects them. This means that indexer.conf configuration doesn't allow these links. (Or again probably a bug in indexer.conf related code).

  For instance a page http://localhost/links.html contains such ignored links.

  To discover the reason, start indexer with these command line arguments:

  indexer -am -u http://localhost/links.html

  That will display various debug information, including:

  • every found link on this page

  • information why indexer rejects found link or accepts it

  With this information provided, it is easy to detect what is the reason of unexpected indexer behavior: either 1 or 2. When you know a reason, either reconfigure indexer.conf and check again, or feel free to report it as a bug when you're sure that everything is OK in your indexer.conf.

  When reporting such bugs, please always include indexer -am -u http://localhost/links.html output, as well as Server/Ream Allow/Disallow commands from your indexer.conf