Topic
  • 3 replies
  • Latest Post - ‏2016-02-17T16:28:14Z by bwchang
RUXA_Alex_Nalivayko
RUXA_Alex_Nalivayko
1 Post

Pinned topic Error start search

‏2014-05-14T12:42:18Z |

Hello,

I installed ICA 3.0 (standallone with Jetty) on RedHat 6.5 x64. Installed fixpack 4. I start system using comman "esadmin system startall", and validate installation - installatin rigth. Installed filenet CE connector.

I'm login to admin console and create new Collection. Add crawler to Filenet 5.2. Crawler, Analysis and Search run automatic, no problem.

I changed Crawler and add new Filenet folder. Restart crawler, index and search. Search no start and error:

FQEP0002E An error occurred when processing a remote API. The reason is : FFQC2037E The search process failed to start on servers 172.28.24.172 [node1]. Check the collection and system log files for more details. FFQC4823E Session Search Manager (node1) [searchmanager.node1] is not running. FFQO0262E Session Search Manager (node1) [searchmanager.node1] is not created yet. FFQC2002E An error occurred while starting the search server for collection col_63496. Message code: ES_ERR_CTRL_SEARCH_START_FAILED. Check the collection and system log files for more details.

com.ibm.es.oze.api.rest.exception.APIException: FFQEP0002E at com.ibm.es.admin.control.ESApiServlet.execute(ESApiServlet.java:351) at com.ibm.es.admin.control.ESApiServlet.doPost(ESApiServlet.java:157) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166) at com.ibm.es.admin.filters.SetEncodingFilter.doFilter(SetEncodingFilter.java:34) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:938) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

I restarted service, search components start no error, but error stay. Removing and rebuilding the collection did not help.

 

  • imagine_rays
    imagine_rays
    1 Post

    Re: Error start search

    ‏2016-01-29T08:34:34Z  

    Hi,

     

    Were you able to get this issue resolved?

    I am also getting the same error.

     

     

  • bwchang
    bwchang
    4 Posts

    Re: Error start search

    ‏2016-02-17T16:28:10Z  

    Alex,

     

    Your error

        FFQO0262E Session Search Manager (node1) [searchmanager.node1] is not created yet.

    seems to indicate that the system session called searchmanager.node1 is missing.  Can you please run the command esadmin check to see if this session is listed in the stdout?  If yes, then is it started?  If not, can you run the command esadmin start and then check if this session is started?

     

    Without the searchmanager.node1 started, you will not be able to start any search runtime for a collection.  If you cannot see the session listed from esadmin check or having a hard time starting it, then something is seriously wrong with the installation and a PMR should be opened with support to further this investigation.

     

    Billy.

  • bwchang
    bwchang
    4 Posts

    Re: Error start search

    ‏2016-02-17T16:28:14Z  

    Alex,

     

    Your error

        FFQO0262E Session Search Manager (node1) [searchmanager.node1] is not created yet.

    seems to indicate that the system session called searchmanager.node1 is missing.  Can you please run the command esadmin check to see if this session is listed in the stdout?  If yes, then is it started?  If not, can you run the command esadmin start and then check if this session is started?

     

    Without the searchmanager.node1 started, you will not be able to start any search runtime for a collection.  If you cannot see the session listed from esadmin check or having a hard time starting it, then something is seriously wrong with the installation and a PMR should be opened with support to further this investigation.

     

    Billy.