CiviCRM Community Forums (archive)

Had an interesting experience yesterday troubleshooting a Drupal install of an existing CiviCRM install on a new server. Everything seemed to go ok except that when I went to http://mysite.org/civicrm  I'd get an out of memory fatal error.

Thinking it was a problem with php.ini (or htaccess or civiccrm.settings.php) memory sizing issue, I focused on that. Tried everything. Even resized my virtual server instance. No matter what I did, I'd get the same error.

I finally decided to attempt a clean, vanilla install and happened to re-check my civicrm config settings and lo and behold I had made a typo in my civicrm database name that caused it to look at another EXISTING, non-CiviCRM database, and assume it was the database it was supposed to use.

My guess is that the queries simply cycled until it timed out.

I'm posting this just in case someone else who tends to separate out their civicrm database from their drupal database, but gives them similar names, won't spend as much time as I did figuring out the problem.