I have two collections configured and would like all of their associated services to start up with esadmin system startall. Currently, this is true for the parse, index & search services, but the crawler for only one of the two collections starts automatically.
I've checked ES_INSTALL_ROOT/default_config/AutoRunComponents.properties and there's nothing there to prevent the crawler from being started. Where should I look for the configuration setting or clues to what might be going wrong?
Notice: We have upgraded developerWorks Community to the latest version of IBM Connections. For more information, read our upgrade FAQ.
Pinned topic Starting crawler automatically with system startall
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2011-07-24T13:57:12Z at 2011-07-24T13:57:12Z by SystemAdmin
SystemAdmin 110000D4XK2014 Posts
Re: Starting crawler automatically with system startall2011-07-24T13:57:12ZThis is the accepted answer. This is the accepted answer.I have tried before to make a new script file that contains the crawlers IDs to force start of them when starting OF, something like that:
echo "Starting OmniFind server"
/opt/IBM/es/bin/esadmin system startall
echo "Starting parsers"
/opt/IBM/es/bin/esadmin startParser -cid CollectionID1
echo "Starting crawlers for CollectionID1 collection"
/opt/IBM/es/bin/esadmin CollectionID1.SEEDLIST_12546 start
Ypu can grap the collection ID from the properties of the crawler from the Administration console.Of course in this case you will use this script file"StartOmniFind.sh" to start OF instead of the default "esadmin system startall" command