Troubleshooting


 

Troubleshooting Techniques

This section contains tips and helpful information on troubleshooting methods and techniques.

Running Glimpse from a Shell

If you have shell access, the best way to troubleshoot problems with the search is to run the equivalent glimpse command in a command shell. To find this command, View the Source of your search results page (even if it is blank) and look for the comment line near the top, something like:

      <!-- Glimpse command: /usr/local/bin/glimpse -U -W -j -y -i -w -H /home/wgdemo/4 'test' | -->

Then go to a command shell and run

      /usr/local/bin/glimpse -U -W -j -y -i -w -H /home/wgdemo/4 'test'

(do not include the '|' character at the end of the command, that is a Unix pipe for sending the results of the command to Webglimpse)

This will give you the raw search results that Webglimpse sees, and may return error codes if the archive is not correctly indexed.

For example, you if the Glimpse executable is located in your /usr/local/bin directory and you wanted to search for 'Arizona' you would enter the following command:

/usr/local/bin/glimpse Arizona

Glimpse has multiple switches that can be used to further refine your query searches. For more information including a list of the switches available, see the Glimpse Man Page.

Manually Reindexing Your Archive

Manually reindexing your archive in order to troubleshoot can usually quickly resolve whatever problem you are having because you will be able to see the output on your screen in real time. To manually index your archive, go to the archive directory and run  ./wgreindex manually.

What Exactly is being Indexed? Viewing the .wg_toindex file

The .wg_toindex file contains a mapping of all the files indexed in your archive. It contains both the internal path and the external web url along with the number of hops used. An example of this is seen below:

/var/www/html/document1.html   http://myserver.domain.com/document1.html  1
/var/www/html/document2.html   http://myserver.domain.com/document2.html  1
/var/www/htmldocument3.html    http://myserver.domain.com/document3.html  1
/var/www/html/document4.html   http://myserver.domain.com/document4.html  1
/var/www/html/document5.html   http://myserver.domain.com/document5.html  1

In this example, the left side contains the servers internal path to the document, the right side is the web url to it and at the end is the link popularity of the document, ie how many other documents in the index link to it . The file is space delimited.

Common Errors During Installation

If you are installing Webglimpse through the web interface, the most common problem would be incorrect permissions or that the files are not owned by the web user.

Webglimpse needs temporary write access to a a cgi bin area where scripts can execute in order to install the files. Note that for security reasons Webglimpse should NOT be installed entirely under document root or a cgi area!

If you want to use the web administration interface, the /archives subdirectory of the webglimpse home should be made web writable. The best way to do this is to make it owned by the web user (the username that your web server runs as). For example, if your web server runs as 'nobody' and you installed webglimpse to /usr/local/wg2, this would be achieved by running

     chmod -R nobody /usr/local/wg2/archives

The install attempts to run this command but depending on the permissions of the user running the install, it may or may not be able to do so.

You also may need to change the permissions of the install.php script, in order to make it executable. If you are using an ftp application such as WS-FTPpro, you can simply right click on the file you need to change and choose 'chmod(UNIX)', as in the left side picture in Figure 19 below. Similarly, if you are using the WINscp3 ftp client, highlighting the file you want to change and clicking the F9 button on the bottom of your screen will bring up the permission box, as in the figure on the right side. (the unix/linux man pages contain further information about the chmod command.)

Figure 19

WS-FTPpro

 

 

 

 

 

             

Figure 19

WINscp3

If you are using your cpanel host to upload and change documents, you should use whichever method they recommend to change permissions.

If you have installed Webglimpse via the unix/linux shell, you may run into problems such as an inability to compile Glimpse. We do have a limited number of Glimpse executables for some of the more common operating systems and versions. Please check our downloads area for availability for your particular system.

 

Security Considerations