Re: Solr failing to create index files or start properly
On 28/11/2007, Chris Hostetter <[EMAIL PROTECTED]> wrote: > Incidently: this thread probably should have been on solr-user. Yes - drat! I thought I subscribed to the solr-user list! sorry A. -- http://www.aarontrevena.co.uk LAMP System Integration, Development and Hosting
Re: Solr failing to create index files or start properly
: > Deleting the index directory and restarting seems like the plan - I'll : > try that next. : : Tried this - it worked. Just to be very explicit about this for posterity: the dataDir (as specified in the solrconfig.xml, or the default of "data" in the solr home dir) must exist when you start Solr or Solr will complain with an appropriate error message. if the dataDir does not contain an "index" directory, Solr will happily create one for you -- but if it does contain an index directory, Solr will (justifiably) assume that there is suppose to be an index there and will let you know about any low level Lucene errors opening that index. Incidently: this thread probably should have been on solr-user. -Hoss
Re: Solr failing to create index files or start properly
On 28/11/2007, Aaron Trevena <[EMAIL PROTECTED]> wrote: > On 28/11/2007, Ryan McKinley <[EMAIL PROTECTED]> wrote: > > I'm only talking about the data, not the configs. From the error it > > looks like your index is broken. If you can rebuild it that is probably > > the best option. If you have a backup elsewhere, that should also work. > > Deleting the index directory and restarting seems like the plan - I'll > try that next. Tried this - it worked. Once I've sorted the working directory out I'll feel a lot more confident about our using Lucene/Solr, which will save looking into or switching to the C++ version. Thanks, A. -- http://www.aarontrevena.co.uk LAMP System Integration, Development and Hosting
Re: Solr failing to create index files or start properly
On 28/11/2007, Ryan McKinley <[EMAIL PROTECTED]> wrote: > I'm only talking about the data, not the configs. From the error it > looks like your index is broken. If you can rebuild it that is probably > the best option. If you have a backup elsewhere, that should also work. Deleting the index directory and restarting seems like the plan - I'll try that next. > > ( the admin > > interface, which we need for analyse.jsp (yuck - screenscraping - how > > very early 90s) keeps on disappearing). > > > > what servlet container are you running? is it jetty? Any chance it is > related to: > https://issues.apache.org/jira/browse/SOLR-118 Yes - it's jetty - yes it's default config setting - yes that sounds like exactly the problem - I'll try replacing the /tmp dir in the settings if I can find it. > re screenscraping, most of the admin interface has request handler > equivalents now - except analysis.jsp - This would be a good one to > refactor. *cough* MVC anyone ? Didn't Java have an MVC framework back in the days before Rails (heck even perl had an MVC before rails) ;) It's bad enough I have to use a web service interface instead a nice library in my preferred language - but screen scraping is postively awful. That's one of the most infuriating things about Java applications - unless you happen to be using Java you're a 2nd class citizen and have to use the paupers gate (webservices) no direct integration of libraries or features - something that grates when you can use native language bindings for the webserver, the database, the operating system, etc. Don't get me started on the 'this application needs it's own java web/application server' meme. Thanks for the help Ryan and Yonik, I would never have been able to get to the bottom of this without your help. I'm afraid I'm a Perl Monger and so my eyes tend to glaze over when trying to decipher Java lingo about servlet containers, beans, or randomly scattered and verbose XML configuration :) A. -- http://www.aarontrevena.co.uk LAMP System Integration, Development and Hosting
Re: Solr failing to create index files or start properly
Aaron Trevena wrote: On 28/11/2007, Ryan McKinley <[EMAIL PROTECTED]> wrote: - java.lang.RuntimeException: java.io.FileNotFoundException: no segments* file found in org.apache.lucene.store.FSDirectory@/usr/local/apache-solr-1.2.0/slando/solr/data/index: files: The configuration is identical to a working installation on another server so I know there is nothing wrong with that, and there is no more additional information available in nohup.out , there is no error log either. This does not look like an configuration problem, it looks like a data problem. If you copy the data from the identical working installation does everything work ok? I can try that, but I'd much rather it Just Worked (TM) - given I can't use the web interface to add files to the index, I'm reluctant to trust it as a fallback server - particularly as our "working" solr installation has had to be restarted twice this month I'm only talking about the data, not the configs. From the error it looks like your index is broken. If you can rebuild it that is probably the best option. If you have a backup elsewhere, that should also work. ( the admin interface, which we need for analyse.jsp (yuck - screenscraping - how very early 90s) keeps on disappearing). what servlet container are you running? is it jetty? Any chance it is related to: https://issues.apache.org/jira/browse/SOLR-118 re screenscraping, most of the admin interface has request handler equivalents now - except analysis.jsp - This would be a good one to refactor. ryan
Re: Solr failing to create index files or start properly
On Nov 28, 2007 4:45 AM, Aaron Trevena <[EMAIL PROTECTED]> wrote: > Hi all, > > I've installed solr on a RHEL 5 server and it fails to start properly > - apparently it's failed to create or find index files. > > when running : > nohup /usr/java/jdk1.5.0_14/bin/java -jar -Xmx1024m -Xms1024m start.jar & > > I get the following in nohup > 27-Nov-2007 15:57:42 org.apache.solr.core.SolrException log > SEVERE: java.lang.RuntimeException: java.io.FileNotFoundException: no > segments* file found in > org.apache.lucene.store.FSDirectory@/usr/local/apache-solr-1.2.0/foo/solr/data/index: > files: > > checking /usr/local/apache-solr-1.2.0/foo/solr/data/index I see that > there are indeed no files in there - there doesn't appear to be a step > when installing where the files would be created so what is going on? Remove the index directory... it shouldn't be there if there is no index. -Yonik
Re: Solr failing to create index files or start properly
On 28/11/2007, Ryan McKinley <[EMAIL PROTECTED]> wrote: > > > > - > > java.lang.RuntimeException: java.io.FileNotFoundException: no > > segments* file found in > > org.apache.lucene.store.FSDirectory@/usr/local/apache-solr-1.2.0/slando/solr/data/index: > > files: > > > > The configuration is identical to a working installation on another > > server so I know there is nothing wrong with that, and there is no > > more additional information available in nohup.out , there is no error > > log either. > > > > This does not look like an configuration problem, it looks like a data > problem. If you copy the data from the identical working installation > does everything work ok? I can try that, but I'd much rather it Just Worked (TM) - given I can't use the web interface to add files to the index, I'm reluctant to trust it as a fallback server - particularly as our "working" solr installation has had to be restarted twice this month ( the admin interface, which we need for analyse.jsp (yuck - screenscraping - how very early 90s) keeps on disappearing). A. -- http://www.aarontrevena.co.uk LAMP System Integration, Development and Hosting
Re: Solr failing to create index files or start properly
- java.lang.RuntimeException: java.io.FileNotFoundException: no segments* file found in org.apache.lucene.store.FSDirectory@/usr/local/apache-solr-1.2.0/slando/solr/data/index: files: The configuration is identical to a working installation on another server so I know there is nothing wrong with that, and there is no more additional information available in nohup.out , there is no error log either. This does not look like an configuration problem, it looks like a data problem. If you copy the data from the identical working installation does everything work ok?
