QuickFinder indexing crashes Tomcat -- Webpages display "Error 503"

  • 3354451
  • 26-Feb-2008
  • 26-Feb-2015


Novell Open Enterprise Server 2 (OES 2)
Novell Open Enterprise Server (Linux based)
Novell QuickFinder


After starting a QuickFinder index, the browser displays Apache"Error 503" indicating that Tomcat is not running. Any web application on the server that uses Tomcat will also display the error.

The index log may show that the index was successful but might be an old log from a previous date.


The problem is most often caused by QuickFinder encountering currently unsupported file formats and crashing. Typically, these file formats are new versions of .pdf files but they can be other file formats as well. When QuickFinder crashes, it stops Tomcat and therefore all the Tomcat web applications.

To find what file Quickfinder is having problems with, do the following:
  • Add this line at the top of the /etc/init.d/novell-tomcat5 script:

After adding this line, restart Tomcat, re-run the index generation. The line above should write to the log in real time and will show if it is crashing on a certain file. The file it is crashing on should be the last file listed in the log file, located in the /var/lib/qfsearch/Sites/default/indexes/<index_name>/ directory.
  • Restart Tomcat the index again to see if the index stops on the same file. If it does, the work-around would be to remove this file and re-run the index.
Patches for the QuickFinder library (libqfreaders.so.3.0.0) will be available when they are released. This updated file format library should resolve the QuickFinder crash.


Reported to Engineering

Additional Information

Another possibility for the error is that the server memory has become full and Tomcat has no more memory available so it shuts down. Check the memory usage and CPU usage to ensure that this is not the case.