I don't know - by chance, I'm actually doing about the same sequence of events right now with Solr 4.1, and the cores are running fine…
What do the logs say? - Mark On Feb 14, 2013, at 10:18 PM, Anirudha Jadhav <aniru...@nyu.edu> wrote: > *1.empty Zookeeper* > *2.empty index directories for solr* > *3.empty solr.xml* > <?xml version="1.0" encoding="UTF-8" ?> > <solr persistent="true"> > <cores adminPath="/admin/cores" > zkClientTimeout="${zkClientTimeout:15000}" hostPort="${jetty.port:}" > hostContext="solr"> </cores> > </solr> > *3.1 upload / link cfg in zookeeper for test collection* > *4*.* start 4 solr servers on different machines* > *5. Access server* : i see > <There are no SolrCores running — for the current functionality we require > at least one SolrCore, sorry :)> that's ok > > *6. CREATE collection* > http://hostname:15000/solr/admin/collections?action=CREATE&name=test&numShards=1&replicationFactor=4 > > this creates one core on each server with one shard named > - test_shard1_replica1 > - test_shard1_replica2 > - test_shard1_replica3 > - test_shard1_replica4 > and persists it in solr.xml on each server. > > *but why are these core are not started?* and even on server reboot even > though solr.xml says loadOnStartup="true" > is still see ERROR on web admin UI > <There are no SolrCores running — for the current functionality we require > at least one SolrCore, sorry :)> > > I did try this once successfully and I think i am missing something now. > Cannot see any errors in log that are severe > > -- > Anirudha P. Jadhav