G'Day,
Thanks for an exellent readme file: we must be getting close with this installation.
But at the step of "making sure the server is running" we get the error above and in the console we get:

WARN::/solr/admin/ java.lang.IllegalStateException: STREAM

along with about 50 lines of java trace
1. The version is apache-solr-3.6.2.tgz
2. The three config files from the module were copied over to the example/solr/conf/* and given same permissions
3. The application started fine with java -jar start.jar
4. I've got the application installed at /usr/local/apache-solr-3.6.2/example/*
5. The install is on a remote server, so I can't test run using "localhost"...I use the IP address of the server: http://72.249.182.115:8983/solr/admin/

Any clues very much appreciated!!

Comments

boabjohn’s picture

So, just following on here, the solr server is running at:
http://72.249.182.115:8983/solr/

However the admin link is still returning the error.

When the link above is used for solr server URL at: admin/config/search/apachesolr/settings/solr
[Test Connection] and the site reports "Your site was unable to contact the Apache Solr server."

So this is either permissions? Or the solrconfig.xml is not set up correctly, or??

user654’s picture

.

mkalkbrenner’s picture

It would help if you post the error message included in the java stack trace.

aliciagh’s picture

I had the same error. I have resolved copying solrcore.properties and solrconfig_extra.xml to apache-solr-3.6.2/example/solr/conf

DeNelo’s picture

Stack trace:

2013-05-08 16:43:53.874:INFO::Started SocketConnector@0.0.0.0:8983
2013-05-08 16:43:59.308:WARN::/solr/admin/
java.lang.IllegalStateException: STREAM
        at org.mortbay.jetty.Response.getWriter(Response.java:616)
        at org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java:187)
        at org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:180)
        at org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java:237)
        at org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspFactoryImpl.java:173)
        at org.apache.jasper.runtime.JspFactoryImpl.releasePageContext(JspFactoryImpl.java:124)
        at org.apache.jsp.admin.index_jsp._jspService(org.apache.jsp.admin.index_jsp:415)
        at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:109)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:389)
        at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:486)
        at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:380)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
        at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
        at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
        at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
        at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
        at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:327)
        at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126)
        at org.mortbay.jetty.servlet.DefaultServlet.doGet(DefaultServlet.java:503)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1221)
        at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:306)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
        at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
        at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
        at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
        at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
        at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
        at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
        at org.mortbay.jetty.Server.handle(Server.java:326)
	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
        at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
        at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
        at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

The solr.xml file has:

<cores adminPath="/admin/cores" defaultCoreName="collection1">
    <core name="collection1" instanceDir="." />
  </cores>

Any clues? I did what the previous commenter said but to no avail.

mkalkbrenner’s picture

Did you try the solution posted in #4?

Countzero’s picture

Solution from aliciagh in #4 worked for me. Thanks a lot.

rylyn’s picture

#4 help me , thanks !

mkalkbrenner’s picture

Just a hint:
You can use Apache Solr Config Generator to create a complete configuration.

imoreno’s picture

#4 helped me as well after a new install of Solr server + module.
Maybe ths could be incorporate the readme.txt file....

DeNelo’s picture

#4 didn't help me. It says
Problem accessing /solr/admin/index.jsp. Reason:
missing core name in path

solr.xml says

  <cores adminPath="/admin/cores" defaultCoreName="collection1">
    <core name="collection1" instanceDir="." />
  </cores>

The solr.war file in solr/webapps is extracted correctly.

boabjohn’s picture

Sorry, I'm bowing out of this issue. My experience is that you need to be reasonably competent and experienced with *nix installations. We are running solr under Tomcat, and I can't tell you how many times I've had to go back to the technicians just to figure out where the installation is, where the logs are, and how many solr.xml config files actually need to be updated.
Our installation *is working* though. It's multicore. I set up my own "example" directory and just copy that over to a new name whenever I need to add a new core. Two config file edits, restart tomcat, and we're good.
So it is worth the pain...
Good luck all.

pwolanin’s picture

Status: Active » Fixed

I made some fixes to the config that were a little broken in the last release due to pulling in the "common" config for the first time.

This should be fixed on HEAD - at least I cannot reproduce w/ Solr 3.6.2 on jetty.

merilainen’s picture

I can only see this diff from May 15th:

-        <str name="field">content</str>
+        <str name="field">spell</str>

I tried to change that, but I still get the same error as in #11

HTTP ERROR 404

Problem accessing /solr/admin/index.jsp. Reason:

    missing core name in path
pwolanin’s picture

check your solr.xml file then per #11

merilainen’s picture

Latest dev works okay, I had some issue on my Solr. Downloading the latest 3.6.2 works now.

nick_vh’s picture

Status: Fixed » Closed (fixed)

Closing to clean the issue queue a bit

eleonel’s picture

#4 works for me. Thanks.