[
https://issues.apache.org/jira/browse/SOLR-10650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002875#comment-16002875
]
Alexandre Rafalovitch commented on SOLR-10650:
----------------------------------------------
Your point about feedback is valid. And, there has been a number of
improvements in Solr recently to improve that feedback. A number of useless log
messages were reduced, some additional error and JVM version detection was
added. All of that should already be in 6.5.1.
There is always more work that can be done, of course. Edge cases (like using
unsupported version of JDK here) are always an issue.
Could you check if you have any logs in the *solr-6.5.1/server/logs* directory?
That's where they should be when you do bin/solr start without any other
parameters. I am surprised you have nothing there. Especially since from your
description it seems that the server part itself started but not the Solr part.
Usually, they fail together.
Like I said, yours seems to be a very edge case, probably due to unsupported
configuration. But, let's at least try to collect as much information about it
as possible to estimate the impact.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
