Well, the easiest thing to do is cheat. Fire up the admin UI, should be something like http://localhost:8983/solr
See if anything drops down in the "core selector" box and select it. Then select a core, the default is "collection1". Now you should see a "query" section, go there and scroll down to the "execute query" button. You should see stuff. But here's the important bit. There should be a URL in light grey near the top of the screen that gives you the right URL to ping. And anywhere in the above steps you can't proceed (say you don't see a drop-down with a core to select) and you know where to focus your efforts... Best, Erick Oh, and please raise new issues in a new e-mail thread, see "thread hijacking" http://people.apache.org/~hossman/#threadhijack On Fri, Nov 1, 2013 at 2:19 PM, Jack Park <jackp...@topicquests.org> wrote: > Thanks. I reviewed clusterstate.json again; those URLs are alive. Why > they are not responding seems to be the mystery du jour. > > I reviewed my test suite: it is using field names in schema.xml, and > the server is configured to use the update responders I installed, all > of which work fine in a non-cloud mode. > > Thanks > Jack > > On Fri, Nov 1, 2013 at 11:12 AM, Shawn Heisey <s...@elyograg.org> wrote: > > On 11/1/2013 12:07 PM, Jack Park wrote: > >> > >> The top error message at my test harness is this: > >> > >> No live SolrServers available to handle this request: > >> [http://127.0.1.1:8983/solr/collection1, > >> http://127.0.1.1:7574/solr/collection1, > >> http://127.0.1.1:7590/solr/collection1] > >> > >> I have to assume that error message was somehow shipped by zookeeper, > >> because those servers actually exist, to the test harness, at > >> 10.1.10.178, and if I access any one of them from the browser, > >> /solr/collection1 does not work, but /solr/#/collection1 does work. > > > > > > Those are *base* urls. By themselves, they return 404. For an example of > > how a base URL is used, try /solr/collection1/select?q=*:* instead. > > > > Any URL with /#/ in it is part of the admin UI, which runs mostly in the > > browser and accesses Solr handlers to gather information. It is not Solr > > itself. > > > > Thanks, > > Shawn > > >
