Why do I get a server status error when I perform a search?

Occasionally, an exceedingly large or complex document causes the search indexing service to abort. This is typically when all searches in SourceForge return an exid to the user.

Check the server status page and see if the search server is listed as anything other than OK. If it is not OK, then you should restart the search service by logging into the SourceForge application server as root and issuing the following commands:

/usr/local/sourceforge/james/james-/bin/phoenix.sh restart

Check the server status page again in SourceForge and ensure that it shows a status of OK. If it shows OK, then searches should now work, and the site will slowly catch up on any indexing requests that were logged while the service was down. If you continue to get exids returned for all searches even with an OK status, then you probably have corrupt search index files and you should see the link below.