I'm trying to test apache solr, but somehow I cannot get the indexing work. Whenever I try to run cron to update the index or delete the index, I always get the same response from the solr server: 400 Bad Request. I attached a raw TCP dump capture of a delete request. However, AFAICT the searches work albeit with empty results. Solr statistics counters in admin servlet gets updated. Any suggestions?
Details:
- Apache Solr nightly 11-Feb-2009, running on top of Tomcat 5.5 (also tested tomcat 6.0 with similar results)
- The 5.x-dev drupal module, dated 2009-Feb-04
- Solr can be pinged, the solr admin servlets seems to work
- Test site, no fancy modules, customizations, etc enabled.
- solr modules enabled: Apache Solr framework, Apache Solr search
The first few lines in tomcat logs of the exception are:
Feb 11, 2009 2:03:44 PM org.apache.solr.common.SolrException log
SEVERE: org.apache.solr.common.SolrException: missing content stream
at org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:49)
at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:131)
| Comment | File | Size | Author |
|---|---|---|---|
| solr-request-trace.txt | 1.43 KB | skiminki |
Comments
Comment #1
JacobSingh commentedI don't know how stable the 5 module is... But it looks like it might be a missing linebreak at the end of the XML payload? Totally random guess and I suppose unlikely.
Perhaps compare to the 6x version which is supported and see what differences exist in the payload?
Comment #2
damien_vancouver commented@skiminki,
Hi, are you still having problems with this?
If so, are you running Linux or Windows?
There may be something in the updated REAMDE.txt that helps, please see:
http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/apachesolr/...
Comment #3
skiminki commentedThis is no longer an important issue to us. Back then when I reported this, we eventually decided to postpone utilizing this module until we migrate the site in concern into newer version of Drupal. But anyhow, we're running Linux.
Comment #4
liorkesos commentedHi Jacob,
I'm experiencing the same problem
centos-5.3
tomcat-5.5-28
java-1.6.0
and (unfortunantly) drupal-5.20
on a 64 bit machine.
What does the "XML payload" mean? so I can start checking alongside the same issues.
The problem surfaces initially while trying to connect to the solr server.
I can telnet to the port in the machine serving so I assume this is not a connectivity issue.
Any help would be appreciated..
Comment #5
claudiu.cristeaIt seems that this thread in not active anymore... Closing.
Comment #6
user654 commented.
Comment #7
damien_vancouver commented@pinkonomy,
I think this is a connectivity or configuration issue between your webserver and Solr.
However, this issue is a really old one from Drupal 5, and is for the wrong module (the old ApacheSolr search integration module, rather than the new Search API module). It sounds like you are using Search API and all the latest stuff, not Drupal 5, so I'd have a look through the issue queues for Search API and see if you find anything (I didn't see anything at first glance though).
If I were in your shoes, I'd start by making sure I can hit the Solr search URL from my webserver. I'd do that by SSH'ing to the server, and then using either "links" or "lynx", the text WWW browsers. I'd fire one of those up and connect to the Solr URL configured with my site and convince myself that the site really can get to Solr on that URL, and realy can run searches at the Solr admin interface. If you can't see solr from the SSH account your website runs under, then neither can your website. Since there's no open issues about this error, I bet you'll find the problem along the way, it's probably misconfiguration.
Please do post back here if/when you solve it though, since this appears to be the best match for that error. I can provide some more detailed instructions if you're still not sure how to do the testing I describe above.