[ 
https://issues.apache.org/jira/browse/SOLR-10650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002930#comment-16002930
 ] 

Alexandre Rafalovitch commented on SOLR-10650:
----------------------------------------------

Ok,

So, we do have logs clearing showing Solr did not start well. And we know the 
underlying cause (incorrect Java version), so it is not a bug.

And we know - from other un-linked Jiras - that other similar use cases (e.g. 
missing Java setup, earlier, rather than later Java version) are now detected. 
We also know that most issues when Solr does not start, the bin/solr script 
does catch that and complaint (e.g. if there is a port conflict).

So, to me, this case becomes VERY SPECIFICALLY about adding a version check and 
an error message for a later Java version. As such, it is probably not the 
highest priority, but we can adjust the Jira title and summary to reflect 
specific use case. A patch - of course - would be welcome too.

> First start fails due to "Problem accessing /solr/. Reason:      Not Found"
> ---------------------------------------------------------------------------
>
>                 Key: SOLR-10650
>                 URL: https://issues.apache.org/jira/browse/SOLR-10650
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: 6.5.1
>            Reporter: Karl Richter
>
> After downloading Solr 6.5.1. standalone zip archive, extracting it into 
> `$HOME` and starting it with `cd solr-6.5.1/ && bin/solr start` I see
> ```
> HTTP ERROR: 404
> Problem accessing /solr/. Reason:
>     Not Found
> ```
> when I access http://localhost:8983 which redirects to 
> http://localhost:8983/solr.
> After the initial start there's no log file (at least not one which can 
> intuitively be found with `find . -name '*.log'`). There're some workarounds 
> like 
> http://stackoverflow.com/questions/27669323/solr-404-error-with-getting-admin-page,
>  but they involve log files I don't find (and if they'd exist are 
> unnecessarily hard to find), and this issue is more about shedding light on 
> the fact that the first and possibly simplest use case (starting the 
> application) doesn't work. Any sane person interested in trying out Solr 
> would turn it's back on it immediately which is a petty. Please provide an 
> intuitive configuration-free startup routine like one can expect from any 
> good software.
> experienced with 6.5.1 (which is not in the list of available versions)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to