Interesting because I was getting the issue when I was passing the full path (without the trailing / ) to Tomcat.
On Mon, Sep 2, 2013 at 11:34 PM, Prasi S <prasi1...@gmail.com> wrote: > The issue is resolved. I have given all the path inside tomcat as relative > paths( solr home, solr war). That was the creating the problem. > > > On Mon, Sep 2, 2013 at 2:19 PM, Prasi S <prasi1...@gmail.com> wrote: > > > Does this have anyting to do with tomcat? I cannot go back as we already > > fixed with tomcat. > > > > Any suggestions pls. The same setup , if i copy and run it on a different > > machine, it works fine. Am not sure what is missing. Is it because of > some > > system parameter getting set? > > > > > > On Fri, Aug 30, 2013 at 9:11 PM, Jared Griffith < > > jgriff...@picsauditing.com> wrote: > > > >> I was getting the same errors when trying to implement SolrCloud with > >> Tomcat. I eventually gave up until something came out of this thread. > >> This all works if you just ditch Tomcat and go with the native Jetty > >> server. > >> > >> > >> On Fri, Aug 30, 2013 at 6:28 AM, Prasi S <prasi1...@gmail.com> wrote: > >> > >> > Also, this fails with the default solr 4.4 downlaoded configuration > too > >> > > >> > > >> > On Fri, Aug 30, 2013 at 4:19 PM, Prasi S <prasi1...@gmail.com> wrote: > >> > > >> > > Below is the script i run > >> > > > >> > > START /MAX > >> > > F:\SolrCloud\zookeeper\zk-server-1\zookeeper-3.4.5\bin\zkServer.cmd > >> > > > >> > > > >> > > START /MAX F:\solrcloud\zookeeper java -classpath .;solr-lib/* > >> > > org.apache.solr.cloud.ZkCLI -cmd upconfig -zkhost localhost:2182 > >> -confdir > >> > > solr-conf -confname solrconf1 > >> > > > >> > > > >> > > > >> > > START /MAX F:\solrcloud\zookeeper java -classpath .;solr-lib/* > >> > > org.apache.solr.cloud.ZkCLI -cmd linkconfig -zkhost 127.0.0.1:2182 > >> -collection > >> > firstcollection -confname solrconf1 -solrhome ../tomcat1/solr1 > >> > > > >> > > > >> > > > >> > > START /MAX F:\solrcloud\zookeeper java -classpath .;solr-lib/* > >> > > org.apache.solr.cloud.ZkCLI -cmd upconfig -zkhost localhost:2182 > >> -confdir > >> > > solr-conf -confname solrconf2 > >> > > > >> > > > >> > > > >> > > > >> > > START /MAX F:\solrcloud\zookeeper java -classpath .;solr-lib/* > >> > > org.apache.solr.cloud.ZkCLI -cmd linkconfig -zkhost 127.0.0.1:2182 > >> -collection > >> > seccollection -confname solrconf2 -solrhome ../tomcat1/solr1 > >> > > > >> > > > >> > > > >> > > START /MAX F:\solrcloud\tomcat1\bin\startup.bat > >> > > > >> > > > >> > > > >> > > START /MAX F:\solrcloud\tomcat2\bin\startup.bat > >> > > > >> > > > >> > > On Fri, Aug 30, 2013 at 4:07 PM, Prasi S <prasi1...@gmail.com> > wrote: > >> > > > >> > >> Im still clueless on where the issue could be. There is no much > >> > >> information in the solr logs. > >> > >> > >> > >> i had a running version of cloud in another server. I have copied > the > >> > >> same to this server, and started zookeeper, then ran teh below > >> commands, > >> > >> > >> > >> java -classpath .;solr-lib/* org.apache.solr.cloud.ZkCLI -cmd > >> upconfig > >> > >> -zkhost localhost:2181 -confdir solr-conf -confname solrconfindex > >> > >> > >> > >> java -classpath .;solr-lib/* org.apache.solr.cloud.ZkCLI -cmd > >> linkconfig > >> > >> -zkhost 127.0.0.1:2181 -collection colindexer -confname > >> solrconfindex > >> > >> -solrhome ../tomcat1/solr1 > >> > >> > >> > >> After this, when i started tomcat, the first tomcat starts fine. > When > >> > the > >> > >> second tomcat is started, i get the above exception and it stops. > >> Tehn > >> > the > >> > >> first tomcat also shows teh same exception. > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> On Thu, Aug 29, 2013 at 7:18 PM, Mark Miller < > markrmil...@gmail.com > >> > >wrote: > >> > >> > >> > >>> Yeah, you see this when the core could not be created. Check the > >> logs > >> > to > >> > >>> see if you can find something more useful. > >> > >>> > >> > >>> I ran into this again the other day - it's something we should > fix. > >> You > >> > >>> see the same thing in the UI when a core cannot be created and it > >> > gives you > >> > >>> no hint about the problem and is confusing. > >> > >>> > >> > >>> - Mark > >> > >>> > >> > >>> On Aug 29, 2013, at 5:23 AM, sathish_ix < > skandhasw...@inautix.co.in > >> > > >> > >>> wrote: > >> > >>> > >> > >>> > Hi , > >> > >>> > > >> > >>> > Check your configuration files uploaded into zookeeper is valid > >> and > >> > no > >> > >>> error > >> > >>> > in config files uploaded. > >> > >>> > I think due to this error, solr core will not be created. > >> > >>> > > >> > >>> > Thanks, > >> > >>> > Sathish > >> > >>> > > >> > >>> > > >> > >>> > > >> > >>> > -- > >> > >>> > View this message in context: > >> > >>> > >> > > >> > http://lucene.472066.n3.nabble.com/SolrCloud-Path-must-not-end-with-character-tp4087159p4087182.html > >> > >>> > Sent from the Solr - User mailing list archive at Nabble.com. > >> > >>> > >> > >>> > >> > >> > >> > > > >> > > >> > >> > >> > >> -- > >> > >> Jared Griffith > >> Linux Administrator, PICS Auditing, LLC > >> P: (949) 936-4574 > >> C: (909) 653-7814 > >> > >> <http://www.picsauditing.com> > >> > >> 17701 Cowan #140 | Irvine, CA | 92614 > >> > >> Join PICS on LinkedIn and Twitter! > >> > >> <https://twitter.com/PICSAuditingLLC> > >> > > > > > -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 <http://www.picsauditing.com> 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter! <https://twitter.com/PICSAuditingLLC>
