I experienced a nasty WSOD by trying to disable the acquia_search module with only one Apache Solr env (Acquia Search). I had deleted the default "localhost" env before and had to recreate it with its default values to prevent having the WSOD any longer. TRUNCATING cache tables manually or disabling any search/Acquia related module didn't help at all.

On the command line, it was breaking drush and throwing this error:

Drush command terminated abnormally due to an unrecoverable error.                                                                                                                                                                                                   [error]
PDOException : SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ')) 
ORDER BY env_id ASC, entity_type ASC, bundle ASC' at line 1: SELECT ib.env_id AS env_id, ib.entity_type AS entity_type, ib.bundle AS bundle
FROM 
{apachesolr_index_bundles} ib
WHERE  (env_id IN  ()) 
ORDER BY env_id ASC, entity_type ASC, bundle ASC; Array
(
)
 in apachesolr_environment_load_subrecords() (line 2579 in docroot/sites/all/modules/contrib/apachesolr/apachesolr.module).
  • All DB updates had been made
  • I'm using all latest stable releases + Drupal 7.15
  • There's no custom module altering search in any way

Comments

cpliakas’s picture

cpliakas commented
Status: Active » Closed (duplicate)

Hi anavarre.

Thanks for the post, but this is a dup of #1778150: Fatal error on all admin/config/* pages caused by SQL error in apachesolr_environment_load_subrecords().

Thanks,
Chris

mcdruid’s picture

mcdruid commented

I know this has been closed as a dupe, but panicking googlers are likely to find this issue as it contains the full error message.

There is a quick fix to get past the WSOD in this situation - to make it a bit easier to go and upgrade the modules without a site which is down.

This is from apachesolr.install

db_insert('apachesolr_environment')->fields(array('env_id' => 'solr', 'name' => 'localhost server', 'url' => 'http://localhost:8983/solr'))->execute();

...and should ensure that there's a row in the table to prevent the SQL error from bringing down the site.

If you can't run this code via drush ev, you should be able to do the equivalent insert straight into the db; something like:

INSERT INTO apachesolr_environment VALUES ('solr', 'localhost server', 'http://localhost:8983/solr', '');

n.b. this may well not actually fix apachesolr on your site, as the values may be wrong, but it should at least stop the WSOD.