On 9/7/2015 5:31 AM, Mark Fenbers wrote:
> On 9/6/2015 4:25 PM, Shawn Heisey wrote:
> I did as you prescribed. Being my solr.xml did not have a "sharedLib"
> line in it, I added
>
> <str name="sharedLib">libtest</str>
>
> between the <solr> and the <solrcloud> tags because I'm not running in
> cloud mode -- at least, not yet.
>
> I also renamed <installDir>/server/lib to <installDir>/server/libtest,
> then restarted solr. This time, solr did not start at all and nothing
> was written to solr.log. In solr.xml, I also tried the following (one
> at a time):
The only files that should be in server/lib is jetty and servlet jars.
The only files that should be in server/lib/ext is logging jars (slf4j,
log4j, etc).
In the server/lib directory on Solr 5.3.0:
ext/
javax.servlet-api-3.1.0.jar
jetty-continuation-9.2.11.v20150529.jar
jetty-deploy-9.2.11.v20150529.jar
jetty-http-9.2.11.v20150529.jar
jetty-io-9.2.11.v20150529.jar
jetty-jmx-9.2.11.v20150529.jar
jetty-rewrite-9.2.11.v20150529.jar
jetty-security-9.2.11.v20150529.jar
jetty-server-9.2.11.v20150529.jar
jetty-servlet-9.2.11.v20150529.jar
jetty-servlets-9.2.11.v20150529.jar
jetty-util-9.2.11.v20150529.jar
jetty-webapp-9.2.11.v20150529.jar
jetty-xml-9.2.11.v20150529.jar
In the server/lib/ext directory on Solr 5.3.0:
jcl-over-slf4j-1.7.7.jar
jul-to-slf4j-1.7.7.jar
log4j-1.2.17.jar
slf4j-api-1.7.7.jar
slf4j-log4j12-1.7.7.jar
Renaming server/lib to server/libtest like you did will prevent Jetty
(and by extension, Solr) from starting. Your extra jars should not go
in either of these two directories. These are part of the *program*
install for Solr, and should not be modified, because doing so will
complicate upgrades.
> <str name="sharedLib">server/libtest</str> <str
> name="sharedLib">/localapps/dev/solr-5.3.0/server/libtest</str> <str
> name="sharedLib">${sharedLib:libtest}</str> ...all with the same
> no-start results. Instead of removing the sharedLib line from solr.xml,
> I left it like this: <str name="sharedLib">${sharedLib:}</str> and
> renamed my libtest back to lib Doing so allowed Solr to restart, albeit
> with the return of DataImportHandler error, as before.
The lib directory that I have been talking about is the one in the solr
home, not in server. Your solr home is /localapps/dev/EventLog ... so
/localapps/dev/EventLog/lib should be renamed to
/localapps/dev/EventLog/libtest, and sharedLib should be just "libtest"
... not "server/libtest". There needs to be exactly one sharedLib entry
in solr.xml. You have mentioned three of them above.
> So does this tell us that we are barking up the wrong tree?? Does this
> mean it *is* a multiple jar version problem? If so, there may be
> multiple jars (caused by my copying things around to try to get this
> working, and my lack of knowledge of where all the places are that it
> looks for jars), but they would be the same versions.
I did not see any evidence of multiple or conflicting jars in the log
that you sent before, just jars loading twice, which SOLR-6188 will fix
for everyone in 5.4. By renaming the lib directory in the solr home to
libtest and adding a sharedLib config to explicitly load that directory,
we are making a similar change to the patch on SOLR-6188 through
configuration alone.
Make sure that server/lib and server/lib/ext are clean, only containing
the specific jars I mentioned above.
Thanks,
Shawn
