lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Matheis (steffkes) (JIRA)" <>
Subject [jira] [Commented] (SOLR-3591) Startup error not reflected in Solr web view
Date Wed, 04 Jul 2012 20:10:34 GMT


Stefan Matheis (steffkes) commented on SOLR-3591:

hum, quick thought was, that we maybe see a difference in the output if the AdminCoreHandler
.. but that's not the fact .. it looks exactly the same. having no cores defined gives the
same result as an startup error.

Is there really no way to see/detect if solr was started like expected? Until that Issue i
was pretty sure, that we have most of the cases covered ;o

Perhaps someone can give a few insights, why all the resources return 404 Not Found even w/o
hitting Solr itself? At least you'll see no requests in the default logs .. which are normally
populated for every request.
> Startup error not reflected in Solr web view
> --------------------------------------------
>                 Key: SOLR-3591
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: web gui
>    Affects Versions: 4.0-ALPHA
>            Reporter: Erik Hatcher
>            Assignee: Stefan Matheis (steffkes)
>            Priority: Blocker
>             Fix For: 4.0
>         Attachments: screenshot-1.jpg
> When Solr has a fatal startup error, it used to be reflected in general responses from
Solr.  With the new UI, it's relegated to only the logs.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message