This applies to Solr Search in Ektron 9.00 and higher.
If an issue occurs where your keyword searches are not working on your site or Workarea, Tomcat may not be starting.
If your search results aren't coming back, check your Task Manager on your Solr Server. Do you see 3 Java processes? If you only see 2, and you are not receiving any results, it is likely that Tomcat is not starting. You can find out if Tomcat is having issues starting by going to
C:\Program Files (x86)\Ektron\Search1.0(2.0)\ProcessManager\Ektron.Cms.Search.Solr.ProcessManager.txt
Check the log and if you have a Search1.0 folder you should see the ManifoldCF Started followed by Tomcat started. If you have a Search2.0 folder Tomcat starts before Manifold.
If Tomcat reports that its startup failed...
- You may have antivirus software on the Solr server.
Set your antivirus to exclude either the Search1.0 or Search2.0 folder. Then recycle the EktronSolrProcessManager service and check Task Manager to see if you have 3 Java Processes. It may take a minute or two to start up.
- Your crawldb may be getting to large for Tomcat to start up.
See Clearing the Solr Crawl Database (/KB/10144/). You can check the size of the crawl db by going to C:\Program Files (x86)\Ektron\Search1.0\ManifoldCF\core\crawldb , right clicking on the crawldb folder and viewing its properties.
- You may not have enough RAM or hard drive space on your server.
Solr requires a minimum of 8GB of RAM by itself. If you manage to install Solr without the 8GB of RAM but your site will not crawl or you are not getting search results, check your system specs.
You can also try manually starting Tomcat:
As a quick workaround (in case this happens on production).
- If you have a Search2.0 folder, open a cmd prompt as an administrator and enter cd C:\Program Files (x86)\Ektron\Search2.0\Tomcat\bin and run catalina.bat start
- If you have a Search1.0 folder open a cmd prompt as an administrator and enter
cd C:\Program Files (x86)\Ektron\Search1.0\Tomcat7\bin and run catalina.bat start