[
https://issues.apache.org/jira/browse/SOLR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507990
]
Hoss Man commented on SOLR-118:
-------------------------------
FYI: I think i may have found one possible cause of this problem .. not sure if
there are other causes.
1) open two terminals both of which are in the solr example directory.
2) in terminal A, run 'java -jar start.jar'
3) note that the following URLs all work fine...
http://localhost:8983/solr/
http://localhost:8983/solr/select/?q=solr&version=2.2&start=0&rows=10&indent=on
http://localhost:8983/solr/admin/
4) in terminal B, run "java -jar start.jar"
5) note that in terminal b, the server logs a "java.net.BindException: Address
already in use" exception but the process does not terminate itself.
6) note that while the process in terminal B is still running, the urls from
step#3 still work fine, and the queries are logged to terminal A
7) hit Ctrl-C in terminal B to kill that process, wait for it to log "Shutdown
hook complete" and return your prompt
8) note that the following URLs now 404...
http://localhost:8983/solr/admin/
http://localhost:8983/solr/
9) note that this URL (and all non JSP non flat file solr urls) continues to
work, and log the request to terminal A...
http://localhost:8983/solr/select/?q=solr&version=2.2&start=0&rows=10&indent=on
..in short, i suspect this is a jetty problem, relating to people inadvertently
trying to run two instances on the same port, and the shutdown hook for the
second instance that does not actually bind to the port inadvertently breaks
the first instance.
> Some admin pages stop working with "error 404" as the only symptom
> ------------------------------------------------------------------
>
> Key: SOLR-118
> URL: https://issues.apache.org/jira/browse/SOLR-118
> Project: Solr
> Issue Type: Bug
> Components: web gui
> Environment: Fedora Core 4 (Linux version 2.6.11-1.1369_FC4smp)
> Sun's JVM 1.5.0_07-b03
> Reporter: Bertrand Delacretaz
> Priority: Minor
>
> This was reported to the mailing list a while ago, see
> http://mail-archives.apache.org/mod_mbox/lucene-solr-user/200610.mbox/[EMAIL
> PROTECTED]
> Today I'm seeing the same thing on a Solr instance that has been running
> since January 9th (about 13 days) with the plain start.jar setup. Index
> contains 150'000 docs, 88322 search requests to date.
> $ curl http://localhost:8983/solr/admin/analysis.jsp
> <html>
> <head>
> <title>Error 404 /admin/analysis.jsp</title>
> </head>
> <body>
> <h2>HTTP ERROR: 404</h2><pre>/admin/analysis.jsp</pre>
> <p>RequestURI=/solr/admin/analysis.jsp</p>
> ...
> curl http://localhost:8983/solr/admin/index.jsp
> <html>
> <head>
> <title>Error 404 /admin/index.jsp</title>
> </head>
> <body>
> <h2>HTTP ERROR: 404</h2><pre>/admin/index.jsp</pre>
> <p>RequestURI=/solr/admin/index.jsp</p>
> ...
> Other admin pages work correctly, for example
> http://localhost:8983/solr/admin/stats.jsp
> I don't see any messages in the logs, which are capturing stdout and stderr
> from the JVM.
> I guess I'll have to restart this instance, I'm out of possibilities to find
> out what's happening exactly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
