drupal 7 fatal error
Inmotion Hosting support was no help on this issue. Hoping someone here might be.
On our testing site at http://testing.apmbags.com I'm getting the following error:
Fatal error: Maximum execution time of 150 seconds exceeded in /home/apmbag5/public_html/testing/includes/module.inc on line 101
Uncaught exception thrown in shutdown function.
PDOException: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away: DELETE FROM {semaphore} WHERE (value = :db_condition_placeholder_0) ; Array ( [:db_condition_placeholder_0] => 1122356977578688bf7dc592.87443157 ) in lock_release_all() (line 269 of /home/apmbag5/public_html/testing/includes/lock.inc).
Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 114480413 bytes) in Unknown on line 0
Site is running Drupal 7.
This happened after an ajax error was thrown when updating one of the site's views. I still have admin access, but the site is not repsonsive.
On our testing site at http://testing.apmbags.com I'm getting the following error:
Fatal error: Maximum execution time of 150 seconds exceeded in /home/apmbag5/public_html/testing/includes/module.inc on line 101
Uncaught exception thrown in shutdown function.
PDOException: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away: DELETE FROM {semaphore} WHERE (value = :db_condition_placeholder_0) ; Array ( [:db_condition_placeholder_0] => 1122356977578688bf7dc592.87443157 ) in lock_release_all() (line 269 of /home/apmbag5/public_html/testing/includes/lock.inc).
Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 114480413 bytes) in Unknown on line 0
Site is running Drupal 7.
This happened after an ajax error was thrown when updating one of the site's views. I still have admin access, but the site is not repsonsive.
The problem happened when working on one of the views for the site. Admin access to the site was still functioning, just page display was messed up. Deleted the view I was editing and that solved the problem. Had to rebuild the view, which took some time, but got the problem solved.
Still no idea what caused the problem.