You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Karl Richter (JIRA)" <ji...@apache.org> on 2017/05/09 13:27:04 UTC
[jira] [Updated] (SOLR-10650) First start fails due to "Problem
accessing /solr/. Reason: Not Found"
[ https://issues.apache.org/jira/browse/SOLR-10650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Richter updated SOLR-10650:
--------------------------------
Description:
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)
was:
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
```
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)
> 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
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org