[
https://issues.apache.org/jira/browse/SOLR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508159
]
Otis Gospodnetic commented on SOLR-118:
---------------------------------------
Scanning the past comments....
My first guess would be that Jetty was left configured as is by default, which
means it expanded webapps in /tmp/Jetty__some_dir_here.... Some UNIX boxes are
configured to purge old files from /tmp/ in order not tu run out of free disk
space in /tmp partition. Perhaps this is what happened here.
The fix is to configure Jetty to expand webapps to a dir that does not get
purged. Of course, I cannot remember the property name for that.
> 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.
