Description
The Intelligence Server may be unable to start up in a Linux environment, and you may receive the following error:
MSTRExec Error: Exiting with error -1 (0xFFFFFFFF): Child Process hung: Command SearchEngineManagerGetSearchEngine
Why is this happening?
You may be encountering this error because the search index folder is set on an NFS server and the index folder is no longer accessible.
The Search Engine fails to initialized if the following conditions are met:
- The search index folder is set to a folder that is mounted from the folder on the NFS server.
- The mount option is hard, instead of soft. The mount option determines the recovery behavior of the NFS client after an NFS request times out. If neither option is specified, or if the hard option is specified, NFS requests are retried indefinitely. If the soft option is specified, then the NFS client fails an NFS request after retrans retransmissions have been sent, causing the NFS client to return an error to the calling application. For details, click here.
- The index folder becomes inaccessible before the Intelligence Server startup, due to a possible NFS server shutdown or network problem.
The Search Engine will continuously check whether the search index folder is accessible, even when the index folder is no longer accessible. The failure of the search engine initialization will prevent the Intelligence Server startup.
Solution
If the search Index folder is not accessible, proceed with the following steps:
- Locate the index folder.
- Check the mount information of the index folder using command:
df -h
- Check the NFS server status.
- If the NFS server is shut down, start up the NFS server.
- If the NFS server no longer exists, unmount the NFS folder, and manually create the folder again.
- Restart the Intelligence Server.
Note: The inaccessible index folder causing the Intelligence Server startup failure only occurs on a Linux platform, and the folder is hosted by the NFS server.
