Take a look at the solr logs, they'll give you a more explicit message.
My guess: Someone went into the Solr admin UI, clicked "core admin"
and then said "I wonder what this 'new core' button does?". The
default name is, you guessed it, "new_core". And if you don't have the
underlying directories
Erick Erickson wrote
> Sure, someone changed the system variable "solr.install.dir" (i.e.
> -Dsolr.install.dir=some other place). Or removed it. Or changed the
> startup script. Or
>
> I've gotten very skeptical of "we didn't change anything but suddenly
> it stopped working". Usually it's som
Sure, someone changed the system variable "solr.install.dir" (i.e.
-Dsolr.install.dir=some other place). Or removed it. Or changed the
startup script. Or
I've gotten very skeptical of "we didn't change anything but suddenly
it stopped working". Usually it's something someone's changed
unbeknow
Thanks so much for the reply, Erick!
I haven't touched anything in several months; I got a message from the
client I built the website for saying the PDF files they're putting into the
folder weren't being indexed so I went in to investigate and discovered the
error. Here's the applicable part of
Well, assuming you didn't, say, install a new Solr or some such it
looks like somebody removed some of the jar files that Tika depends
on, they're in the contrib area. Or changed the solrconfig.xml file to
not contain the something like:
BTW, for various reasons I prefer to do the heavy Ti
