Debugging failed updates

Funnelback updates can fail for a number of reasons. These tips should assist in doing some preliminary debugging on what caused an update to fail.

The first thing to do is look at the update log for the collection that failed and determine at what point the update failed. Look for error lines.

You can access this file from the administration console by browsing the log files from the Administer tab, or from the command line from the $SEARCH_HOME/data/<collection name>/log folder. The main update log is located in the collection log files section and is called update-<collection name>.log.

Once you have found the source of the error you may need to check the relevant log file for the particular phase of the update where the failure occurred. These fill be located in the offline log files section.

Common errors include: