Article ID: 2017645 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
The following message is seen in the searchctrl-15600 logs when the search processes is attempting the load a new index, but it continuously fails after about 60 seconds:
Issuing a resetindex seems to allow the index to build properly, but search is still unable to start.
By default, fsearch is allowed 60 seconds to start up. If it fails to complete the startup process within that time, the search controller will stop the process, and the cycle will start again. With debug logging enabled (by adding debuglog="true" to $FASTSEARCH/etc/searchrc-1.xml), you see the timeout message explicitly:
Typically there are two reasons why this may occur:
If neither of the solutions above are possible, extend the timeout period by modifying the file $FASTSEARCH/etc/searchrc-1.xml on each search node. Add the following parameter and increase the value (in seconds) to something larger than 60.
After editing the file, restart the search-1 process (nctrl restart search-1) on each search node.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.