PassMark Logo
Home » Forum

Announcement

Collapse
No announcement yet.

Keeping the entire indexing log file - Debug mode

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Keeping the entire indexing log file - Debug mode

    We have had a few people asking about the log file that is created during the indexing process.

    Some people have wondered why the entire status log is not displayed in the log window and not stored to disk when the log is saved (i.e. the start of the log is missing).

    The log is deliberately limited in order to save on RAM. The limit is 5000
    lines. After more than 5000 lines, older log lines are discarded. Even with this limit the log can gobble up more than 10MB of RAM.

    As an alternative, you can place Zoom into debug mode using -D on the command line. A file called debuglog.txt is then created with the complete log. So the command line might look something like

    "C:\Program Files\Zoom Search Engine 4.0\ZoomIndexer.exe" -D

    But it will slow down the indexing process significantly, so don't use it all the time.

    Another alternative is to decrease the amount of detail displayed in the log. For example if you just want to see the Errors encountered during indexing then you can turn off all other messages from the "Status log" tab in the Zoom configuration window.

    ----
    David

  • #2
    Additional detail:

    To enter in the command line. Find the Zoom icon on the desktop, right click, select properties, enter the command line text into the target field.

    The debuglog.txt will appear in the Zoom install directory after you have
    complete indexing.
    C:\Program Files\Zoom SearchEngine 4.2\debuglog.txt

    If you are using V4.2, then the most likely install directory would be
    C:\Program Files\Zoom SearchEngine 4.2\
    and not
    C:\Program Files\Zoom SearchEngine 4.0\

    ----
    David

    Comment

    Working...
    X