Closed (fixed)
Project:
Apache Solr Autocomplete
Version:
6.x-1.0
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
11 Jul 2010 at 22:33 UTC
Updated:
2 Jun 2012 at 02:57 UTC
Anytime I activate the autocomplete function of Aapche Solr, it cripples queries with the following error:
An HTTP error 500 occurred. apachesolr_autocomplete
Any suggestions
Comments
Comment #1
janusman commentedPlease post a portion of your apache error log to see what is failing.
Comment #2
tsbah commentedI reactivated Apache Solr autocomplete and as stated the search function no longer works.
Here is the apache relevant error_log section:
Comment #3
janusman commentedIt seems your site is not properly logging errors... or the module silently failed somehow.
Please state how you got the 500 error... what URL is that? Or did you somehow extract that 500 error from inside an AJAX request using Firebug or such?
Also some possible workarounds or further diagnostics:
* Also, does the same happen on a fresh install of Drupal + apachesolr? (Or by disabling all of the other contrib modules you might have)
* What happens if you try using the DEV version?
* Is your Drupal core patched in any way?
Comment #4
adamelleston commentedI am getting the same error.
I have got an install of pressflow drupal 6.17 with a handful of core modules enabled and feeds.
The error in my log file is
I have tried disabling all contrib modules that I can but no luck.
I also tried the dev version but instead of getting the error it just goes on forever and I got this message after install
Comment #5
janusman commented@adamelleston: thanks for the report.
Could you:
* report back with what version of Solr you are using?
* confirm if you have the proper schema.xml and solrconfig.xml files that are included with the installed version of apachesolr.module?
Comment #6
adamelleston commented@janusman we are just in the process of settings up a drupal cloud server environment setup and believe that solr is being installed from fresh. Once that is ready I will test again on this new setup and let you know if the problem is still there or if its fixed.
Comment #7
janusman commentedGreat. I just released version 1.1 yesterday, so make sure you use that too =)
Comment #8
adamelleston commented@janusman the new server environment with 1.1 works a treat. Module is a great addition :)
Comment #9
allie mickaLooks like this was resolved in 2010!