Could not start SOLR issue
Hi We are running master/slave Solr 1.3 version on production since about 5 months. Yesterday, we faced following issue on one of the slaves for the first time because of which we had to restart the slave. SEVERE: Could not start SOLR. Check solr/home property java.lang.RuntimeException: java.io.FileNotFoundException: no segments* file found in org.apache.lucene.store.FSDirectory@/opt/solr/solr_slave/solr/data/index: files: null I searched on forums but couldn't find any relevant info which could have possibly caused the issue. In snapinstaller logs, following failed logs were observed: 2010/01/11 04:20:06 started by solr 2010/01/11 04:20:06 command: /opt/solr/solr_slave/solr/solr/bin/snapinstaller 2010/01/11 04:20:07 installing snapshot /opt/solr/solr_slave/solr/data/snapshot.20100111041402 2010/01/11 04:20:07 notifing Solr to open a new Searcher 2010/01/11 04:20:07 failed to connect to Solr server 2010/01/11 04:20:07 snapshot installed but Solr server has not open a new Searcher 2010/01/11 04:20:08 failed (elapsed time: 1 sec) Configurations: There are 2 search servers in a virtualized VMware environment. Each has 2 instances of Solr running on separates ports in tomcat. Server 1: hosts 1 master(application 1), 1 slave (application 1) Server 2: hosta 1 master (application 2), 1 slave (application 1) Both servers have 4 CPUs and 4 GB RAM. Master - 4GB RAM - 1GB JVM Heap memory is allocated to Solr Slave1/Slave2: - 4GB RAM - 2GB JVM Heap memory is allocated to Solr Can there be any possible reasons that solr/home property couldn't be found? Thanks Dipti
Re: Could not start SOLR issue
On Jan 11, 2010, at 1:38 AM, dipti khullar wrote: > Hi > > We are running master/slave Solr 1.3 version on production since about 5 > months. > > Yesterday, we faced following issue on one of the slaves for the first time > because of which we had to restart the slave. > > SEVERE: Could not start SOLR. Check solr/home property > java.lang.RuntimeException: java.io.FileNotFoundException: no segments* file > found in > org.apache.lucene.store.FSDirectory@/opt/solr/solr_slave/solr/data/index: > files: null It looks like your index was removed out from under you. Perhaps this is due to the failed snapshot install? Can you replicate the problem? Stopping the slave and deleting the index directory and then restarting it should resolve it for now. > > I searched on forums but couldn't find any relevant info which could have > possibly caused the issue. > > In snapinstaller logs, following failed logs were observed: > > 2010/01/11 04:20:06 started by solr > 2010/01/11 04:20:06 command: > /opt/solr/solr_slave/solr/solr/bin/snapinstaller > 2010/01/11 04:20:07 installing snapshot > /opt/solr/solr_slave/solr/data/snapshot.20100111041402 > 2010/01/11 04:20:07 notifing Solr to open a new Searcher > 2010/01/11 04:20:07 failed to connect to Solr server > 2010/01/11 04:20:07 snapshot installed but Solr server has not open a new > Searcher > 2010/01/11 04:20:08 failed (elapsed time: 1 sec) > > > Configurations: > There are 2 search servers in a virtualized VMware environment. Each has 2 > instances of Solr running on separates ports in tomcat. > Server 1: hosts 1 master(application 1), 1 slave (application 1) > Server 2: hosta 1 master (application 2), 1 slave (application 1) > > Both servers have 4 CPUs and 4 GB RAM. > Master > - 4GB RAM > - 1GB JVM Heap memory is allocated to Solr > Slave1/Slave2: > - 4GB RAM > - 2GB JVM Heap memory is allocated to Solr > > Can there be any possible reasons that solr/home property couldn't be found? > > Thanks > Dipti
Re: Could not start SOLR issue
We were able to resolve the problem by restarting the slave. Also these failed snapshot install incidents occur after the exception was observed, which seems logically correct also. "Could not start SOLR. Check solr/home property" We just want to avoid such instances for future. Is it possible that an any instance of time solr/home property can get corrupted? One more thing we observed was that tomcat-users.xml was overwritten. Should we debug towards that also? Thanks Dipti On Mon, Jan 11, 2010 at 6:55 PM, Grant Ingersoll wrote: > > On Jan 11, 2010, at 1:38 AM, dipti khullar wrote: > > > Hi > > > > We are running master/slave Solr 1.3 version on production since about 5 > > months. > > > > Yesterday, we faced following issue on one of the slaves for the first > time > > because of which we had to restart the slave. > > > > SEVERE: Could not start SOLR. Check solr/home property > > java.lang.RuntimeException: java.io.FileNotFoundException: no segments* > file > > found in org.apache.lucene.store.FSDirectory@ > /opt/solr/solr_slave/solr/data/index: > > files: null > > It looks like your index was removed out from under you. Perhaps this is > due to the failed snapshot install? > > Can you replicate the problem? Stopping the slave and deleting the index > directory and then restarting it should resolve it for now. > > > > > I searched on forums but couldn't find any relevant info which could have > > possibly caused the issue. > > > > In snapinstaller logs, following failed logs were observed: > > > > 2010/01/11 04:20:06 started by solr > > 2010/01/11 04:20:06 command: > > /opt/solr/solr_slave/solr/solr/bin/snapinstaller > > 2010/01/11 04:20:07 installing snapshot > > /opt/solr/solr_slave/solr/data/snapshot.20100111041402 > > 2010/01/11 04:20:07 notifing Solr to open a new Searcher > > 2010/01/11 04:20:07 failed to connect to Solr server > > 2010/01/11 04:20:07 snapshot installed but Solr server has not open a new > > Searcher > > 2010/01/11 04:20:08 failed (elapsed time: 1 sec) > > > > > > Configurations: > > There are 2 search servers in a virtualized VMware environment. Each has > 2 > > instances of Solr running on separates ports in tomcat. > > Server 1: hosts 1 master(application 1), 1 slave (application 1) > > Server 2: hosta 1 master (application 2), 1 slave (application 1) > > > > Both servers have 4 CPUs and 4 GB RAM. > > Master > > - 4GB RAM > > - 1GB JVM Heap memory is allocated to Solr > > Slave1/Slave2: > > - 4GB RAM > > - 2GB JVM Heap memory is allocated to Solr > > > > Can there be any possible reasons that solr/home property couldn't be > found? > > > > Thanks > > Dipti > >
