Apache Solr Error 400 Bad Request
Contents |
connections all over the world. Join today Download & Extend Drupal Core Distributions Modules Themes Search API Solr SearchIssues Can't Index
Solr 400 Bad Request
Items: 400 Status, Bad Request Closed (fixed)Project:Search API Solr SearchVersion:7.x-1.3Component:CodePriority:NormalCategory:Support requestAssigned:UnassignedReporter:splitsplitsplitCreated:November 4, solr returned an error 400 bad request 2013 - 23:33Updated:June 7, 2016 - 11:54 Log in or register to update this issue Jump to:Most
Org.apache.solr.common.solrexception: Bad Request
recent comment Problem When I try to index items, none are indexed and I get an error 400 Status: Bad Request. A bit of googling revealed this usually bad request solr to be down to not copying in the solr config from Search API Solr Module, however I done this and it still doesn't solve the problem. Is this a mis-configuration or a bug? Set-Up Ubuntu 12.04 Server LEMP Stack Tomcat 7.0.47 Apache Solr 4.5.1 Apachesolr Module 1.5 Search API Solr Search 1.3 (Installed from the following instructions http://www.lullabot.com/blog/article/installing-solr-use-drupal) magento solr 400 status bad request Installed Tomcat without problems. Set it to port 8983. Tomcat still running successfully. Copied across basic solr config files. Setting up Drupal Core: Copied solr 4.5.1 example config to /usr/local/tomcat/solr. Removed the three lines listed in the patch from apachesolr module to avoid the solrconfig.xml loading bug. (Issue here https://drupal.org/node/2107417) Copied config from apachesolr 1.5 Drupal Module to overwrite example config. Created solr core definition Created solr/drupal directory and copied in config from apachesolr 1.5 drupal module. Rebooted Tomcat and assigned all permissions to Tomcat user. This gives the error 400 status bad request that I'd forgotten about. (had to reinstall solr) Removed the three lines listed in the patch from search_api_solr module to avoid the solrconfig.xml loading bug. (Issue here https://drupal.org/node/2107417) Copied config from search_api_solr module into solr core config (/usr/local/tomcat/solr) and drupal config (/usr/local/tomcat/drupal/solr). Rebooted Tomcat and assigned all permissions to Tomcat user. But this still gives me the index error, shown in full below. Mis-configuration or genuine bug? (I attached the schema and solrconfig.xml from my s
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss
Solr Returned An Error #400 Bad Request
the workings and policies of this site About Us Learn more solr undefined field about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack
Drupal Apache Solr
Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping https://www.drupal.org/node/2127555 each other. Join them; it only takes a minute: Sign up Solr HTTP 400 Error Bad Request on search up vote 0 down vote favorite I currently get the following error when dispatching a query. Module collective.solr.search, line 94, in search Module collective.solr.solr, line 266, in search Module collective.solr.solr, line 127, in doPost Module collective.solr.solr, line 116, in http://stackoverflow.com/questions/36765641/solr-http-400-error-bad-request-on-search __errcheck SolrException: HTTP code=400, reason=Bad Request I also get an 'HTTP code-400, reason=Bad Request' error when I try to upload a file or create a new page. To me it seems there is a problem with the server connection, although everything else is running just fine. Does anyone have an idea what might be wrong here? The error log (after a query): 4/21/2016, 3:38:27 PM | ERROR | ShowFileRequestHandler | Can not find: admin-extra.html [/opt/plone/Plone/zeocluster/parts/solr-instance/solr/plone/conf/admin-extra.html] 4/21/2016, 3:40:26 PM | ERROR | SolrCore | org.apache.solr.common.SolrException: no field name specified in query and no default specified via 'df' param apache http solr plone share|improve this question edited Apr 21 at 13:52 asked Apr 21 at 9:39 artemis_clyde 1188 Did you checked the Solr error log? –Luca Fabbri Apr 21 at 10:03 I edited my question! –artemis_clyde Apr 21 at 13:52 For what I read so far the admin-extra.html is just a common error in Solr with no further effect. –artemis_clyde Apr 21 at 14:02 add a c
a quick overview of the site Help Center Detailed answers to http://magento.stackexchange.com/questions/10278/400-status-bad-request-solr any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business https://issues.apache.org/jira/browse/SOLR-4600 Learn more about hiring developers or posting ads with us Magento Questions Tags Users Badges Unanswered Ask Question _ Magento Stack Exchange is a bad request question and answer site for users of the Magento e-Commerce platform. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top 400 Status Bad Request - Solr 400 bad request up vote 0 down vote favorite I am getting "400 Status Bad Request" error when saving product in backend. Product values gets saved, but page remains in the edit screen and displays this error. This same error also comes when editing Category pages. Any idea what the issue can be or how to properly debug? UPDATE: This gets resolved if I change catalog search to "Mysql Fulltext" from SOLR. But what if I want to use Solr, how to prevent this error? UPDATE: Error while running reindex on Catalog Search Index Catalog Search Index index process unknown error: exception 'Exception' with message '"400" Status: Bad Request' in /var/www/dev/store/app/code/core/Enterprise/Search/Model/Client/Solr.php:256 Stack trace: #0 /var/www/dev/store/lib/Apache/Solr/Service.php(919): Enterprise_Search_Model_Client_Solr->_sendRawPost('http://localhos...', '
be returned if a query parameter has the wrong datatypeAgile Board ExportXMLWordPrintableJSON Details Type: Bug Status: Open Priority: Major Resolution: Unresolved Affects Version/s: 4.2 Fix Version/s: None Component/s: None Labels: None Description Solr returns a 500 Server Error for the following query even though the error is really a user error - wrong datatype for the &rows parameter: curl "http://localhost:8983/solr/select/?q=*:*&rows=all" -v The &rows parameter of course expects an integer. Somebody should probably trap the raw number format exception and turn it into a 400 Bad Request SolrException. The actual response: Jack Krupansky@JackKrupansky ~ $ curl "http://localhost:8983/solr/select/?q=*:*&rows=all" -v * About to connect() to localhost port 8983 (#0) * Trying 127.0.0.1... * connected * Connected to localhost (127.0.0.1) port 8983 (#0) > GET /solr/select/?q=*:*&rows=all HTTP/1.1 > User-Agent: curl/7.27.0 > Host: localhost:8983 > Accept: */* > * additional stuff not fine /usr/src/ports/curl/curl-7.27.0-1/src/curl-7.27.0/lib/transfer.c:1037: 0 0 * HTTP 1.1 or later with persistent connection, pipelining supported < HTTP/1.1 500 Server Error < Cache-Control: no-cache, no-store < Pragma: no-cache < Expires: Sat, 01 Jan 2000 01:00:00 GMT < Last-Modified: Sun, 17 Mar 2013 21:23:39 GMT < ETag: "13d7a3c83fb" < Content-Type: application/xml; charset=UTF-8 < Transfer-Encoding: chunked <