Good to meet you! It looks like you've tried to start Solr a time or two. When you start up the "cloud" example it creates /opt/solr-5.5.0/example/cloud and puts your SolrCloud stuff under there. It also automatically puts your configuration sets up on Zookeeper. When I get this kind of thing, I usually
> stop Zookeeper (if running externally) > rm -rf /opt/solr-5.5.0/example/cloud > delete all the Zookeeper data. It may take a bit of poking to find out where the Zookeeper data is. It's usually in /tmp/zookeeper if you're running ZK standalone, or in a subdirectory in Solr if you're using embedded ZK. NOTE: if you're running standalone zookeeper, you should _definitely_ change the data dir because it may disappear from /tmp/zookeeper.... One of Zookeeper's little quirks > try it all over again. Here's the problem. The examples (-e cloud) tries to do a bunch of stuff for you to get the installation up and running without having to wend your way through all of the indiviual commands. Sometimes getting partway through leaves you in an ambiguous state. Or at least a state you don't quite know what all the moving parts are. Here's the steps you need to follow if you're doing them yourself rather than relying on the canned example 1> start Zookeeper externally. For experimentation, a single ZK is quite sufficient, I don't bother with 3 ZK instances and a quorum unless I'm in a production situation. 2> start solr with the bin/solr script, use the -c and -z options. At this point, you have a functioning Solr, but no collections. You should be able to see the solr admin UI at http://node:8982/solr at this point. 3> use the bin/solr zk -upconfig command to put a configset in ZK 4> use the Collections API to create and maintain collections. And one more note. When you use the '-e cloud' option, you'll see messages go by about starting nodes with a command like: bin/solr start -c -z localhost:2181 -p 8981 -s example/cloud/node1/solr bin/solr start -c -z localhost:2181 -p 8982 -s example/cloud/node2/solr Once the structure is created, then you just use these commands to restart an existing set of Solr instances on your machine. Remember I said that the canned examples create ...example/cloud? What the canned examples are doing is creating solr instances that are independent, but on the same machine in order to get people started. When you specify the '-e cloud' option, those directories are created or, as you've seen, messages are printed that essentially indicate you're running the one-time example... more than once. HTH, Erick On Tue, Mar 29, 2016 at 8:06 AM, Jarus Bosman <oxy...@gmail.com> wrote: > Hi, > > Introductions first (as I was taught): My name is Jarus Bosman, I am a > software developer from South Africa, doing development in Java, PHP and > Delphi. I have been programming for 19 years and find out more every day > that I don't actually know anything about programming ;). > > My problem: > > We recently moved our environment to a new server. I've installed 5.5.0 on > the new environment. When I want to start the server, I get the following: > > *Welcome to the SolrCloud example!* > > *Starting up 2 Solr nodes for your example SolrCloud cluster.* > > *Solr home directory /opt/solr-5.5.0/example/cloud/node1/solr already > exists.* > */opt/solr-5.5.0/example/cloud/node2 already exists.* > > *Starting up Solr on port 8983 using command:* > */opt/solr-5.5.0/bin/solr start -cloud -p 8983 -s > "/opt/solr-5.5.0/example/cloud/node1/solr"* > > *Waiting up to 30 seconds to see Solr running on port 8983 [/] Still not > seeing Solr listening on 8983 after 30 seconds!* > *INFO - 2016-03-29 14:22:14.356; [ ] org.eclipse.jetty.util.log.Log; > Logging initialized @463ms* > *INFO - 2016-03-29 14:22:14.717; [ ] org.eclipse.jetty.server.Server; > jetty-9.2.13.v20150730* > *WARN - 2016-03-29 14:22:14.752; [ ] > org.eclipse.jetty.server.handler.RequestLogHandler; !RequestLog* > *INFO - 2016-03-29 14:22:14.757; [ ] > org.eclipse.jetty.deploy.providers.ScanningAppProvider; Deployment monitor > [file:/opt/solr-5.5.0/server/contexts/] at interval 0* > *INFO - 2016-03-29 14:22:15.768; [ ] > org.eclipse.jetty.webapp.StandardDescriptorProcessor; NO JSP Support for > /solr, did not find org.apache.jasper.servlet.JspServlet* > *WARN - 2016-03-29 14:22:15.790; [ ] > org.eclipse.jetty.security.ConstraintSecurityHandler; > ServletContext@o.e.j.w.WebAppContext@7a583307{/solr,file:/opt/solr-5.5.0/server/solr-webapp/webapp/,STARTING}{/opt/solr-5.5.0/server/solr-webapp/webapp} > has uncovered http methods for path: /* > *INFO - 2016-03-29 14:22:15.809; [ ] > org.apache.solr.servlet.SolrDispatchFilter; SolrDispatchFilter.init(): > WebAppClassLoader=1287618844@4cbf811c* > *INFO - 2016-03-29 14:22:15.848; [ ] > org.apache.solr.core.SolrResourceLoader; JNDI not configured for solr > (NoInitialContextEx)* > *INFO - 2016-03-29 14:22:15.849; [ ] > org.apache.solr.core.SolrResourceLoader; using system property > solr.solr.home: /opt/solr-5.5.0/example/cloud/node1/solr* > *INFO - 2016-03-29 14:22:15.850; [ ] > org.apache.solr.core.SolrResourceLoader; new SolrResourceLoader for > directory: '/opt/solr-5.5.0/example/cloud/node1/solr'* > *INFO - 2016-03-29 14:22:15.851; [ ] > org.apache.solr.core.SolrResourceLoader; JNDI not configured for solr > (NoInitialContextEx)* > *INFO - 2016-03-29 14:22:15.852; [ ] > org.apache.solr.core.SolrResourceLoader; using system property > solr.solr.home: /opt/solr-5.5.0/example/cloud/node1/solr* > *INFO - 2016-03-29 14:22:15.880; [ ] org.apache.solr.core.SolrXmlConfig; > Loading container configuration from > /opt/solr-5.5.0/example/cloud/node1/solr/solr.xml* > *INFO - 2016-03-29 14:22:16.051; [ ] > org.apache.solr.core.CorePropertiesLocator; Config-defined core root > directory: /opt/solr-5.5.0/example/cloud/node1/solr* > *INFO - 2016-03-29 14:22:16.104; [ ] org.apache.solr.core.CoreContainer; > New CoreContainer 1211012646* > *INFO - 2016-03-29 14:22:16.104; [ ] org.apache.solr.core.CoreContainer; > Loading cores into CoreContainer > [instanceDir=/opt/solr-5.5.0/example/cloud/node1/solr]* > *WARN - 2016-03-29 14:22:16.109; [ ] org.apache.solr.core.CoreContainer; > Couldn't add files from /opt/solr-5.5.0/example/cloud/node1/solr/lib to > classpath: /opt/solr-5.5.0/example/cloud/node1/solr/lib* > *INFO - 2016-03-29 14:22:16.133; [ ] > org.apache.solr.handler.component.HttpShardHandlerFactory; created with > socketTimeout : 600000,connTimeout : 60000,maxConnectionsPerHost : > 20,maxConnections : 10000,corePoolSize : 0,maximumPoolSize : > 2147483647,maxThreadIdleTime : 5,sizeOfQueue : -1,fairnessPolicy : > false,useRetries : false,* > *INFO - 2016-03-29 14:22:16.584; [ ] > org.apache.solr.update.UpdateShardHandler; Creating UpdateShardHandler HTTP > client with params: socketTimeout=600000&connTimeout=60000&retry=true* > *INFO - 2016-03-29 14:22:16.590; [ ] org.apache.solr.logging.LogWatcher; > SLF4J impl is org.slf4j.impl.Log4jLoggerFactory* > *INFO - 2016-03-29 14:22:16.592; [ ] org.apache.solr.logging.LogWatcher; > Registering Log Listener [Log4j (org.slf4j.impl.Log4jLoggerFactory)]* > *INFO - 2016-03-29 14:22:16.603; [ ] > org.apache.solr.cloud.SolrZkServerProps; Reading configuration from: > /opt/solr-5.5.0/example/cloud/node1/solr/zoo.cfg* > *INFO - 2016-03-29 14:22:16.605; [ ] org.apache.solr.cloud.SolrZkServer; > STARTING EMBEDDED STANDALONE ZOOKEEPER SERVER at port 9983* > *INFO - 2016-03-29 14:22:17.106; [ ] org.apache.solr.core.ZkContainer; > Zookeeper client=localhost:9983* > *ERROR: Did not see Solr at http://localhost:8983/solr > <http://localhost:8983/solr> come online within 30* > > > > However, when I do a ps - ef|grep solr, I can see it is running: > > *root 23835 1 0 16:22 pts/5 00:00:11 java -server -Xms512m > -Xmx512m -XX:NewRatio=3 -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=90 > -XX:MaxTenuringThreshold=8 -XX:+UseConcMarkSweepGC -XX:+UseParNewGC > -XX:ConcGCThreads=4 -XX:ParallelGCThreads=4 -XX:+CMSScavengeBeforeRemark > -XX:PretenureSizeThreshold=64m -XX:+UseCMSInitiatingOccupancyOnly > -XX:CMSInitiatingOccupancyFraction=50 -XX:CMSMaxAbortablePrecleanTime=6000 > -XX:+CMSParallelRemarkEnabled -XX:+ParallelRefProcEnabled > -XX:CMSFullGCsBeforeCompaction=1 -XX:CMSTriggerPermRatio=80 -verbose:gc > -XX:+PrintHeapAtGC -XX:+PrintGCDetails -XX:+PrintGCDateStamps > -XX:+PrintGCTimeStamps -XX:+PrintTenuringDistribution > -XX:+PrintGCApplicationStoppedTime > -Xloggc:/opt/solr-5.5.0/example/cloud/node1/solr/../logs/solr_gc.log > -DzkClientTimeout=15000 -DzkRun -Djetty.port=8983 -DSTOP.PORT=7983 > -DSTOP.KEY=solrrocks -Duser.timezone=UTC > -Djetty.home=/opt/solr-5.5.0/server > -Dsolr.solr.home=/opt/solr-5.5.0/example/cloud/node1/solr > -Dsolr.install.dir=/opt/solr-5.5.0 > -Dlog4j.configuration=file:/opt/solr-5.5.0/example/resources/log4j.properties > -Xss256k -jar start.jar > -XX:OnOutOfMemoryError=/opt/solr-5.5.0/bin/oom_solr.sh 8983 > /opt/solr-5.5.0/example/cloud/node1/solr/../logs --module=http* > > There is nothing in the "logs" directory. When I try to connect to the web > interface, it also times out. What am I missing? > > Thank you, > Jarus Bosman > > > "Getting information off the Internet is like taking a drink from a fire > hydrant." - Mitchell Kapor > > .---. .-. .-..-. .-.,'|"\ .---. ,--, > / .-. ) ) \_/ / \ \_/ )/| |\ \ / .-. ) .' .' > | | |(_)(_) / \ (_)| | \ \ | | |(_)| | __ > | | | | / _ \ ) ( | | \ \| | | | \ \ ( _) > \ `-' / / / ) \ | | /(|`-' /\ `-' / \ `-) ) > )---' `-' (_)-' /(_| (__)`--' )---' )\____/ > (_) (__) (_) (__)
