Additional uncaught exception thrown while handling exception.
Original
PDOException: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away: SELECT COUNT(cid) FROM {comment} WHERE status = :status; Array ( [:status] => 0 ) in comment_count_unpublished() (line 313 of C:\wamp\www\modules\comment\comment.module).
Additional
PDOException: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away: SELECT ff.* FROM {filter_format} ff WHERE (status = :db_condition_placeholder_0) ORDER BY weight ASC; Array ( [:db_condition_placeholder_0] => 1 ) in filter_formats() (line 407 of C:\wamp\www\modules\filter\filter.module).
Uncaught exception thrown in session handler.
PDOException: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away in _drupal_session_write() (line 206 of C:\wamp\www\includes\session.inc).
The above error messages appear after installing Hierarchical Select 7.x-3.0-alpha5 and Hierarchical Select - Taxonomy when one clicks on the "EDIT" tab of all Content Types.
The error does not appear if the database is restored to a state immediately preceding the installation of the module.
Any idea what may cause this and how to fix it? Thanks. :)
Comments
Comment #1
wim leersOn which particular page (post the Drupal path) are you clicking on the "edit" tab?
Comment #2
Triumphent commented@Wim Leers
When I am on the Content Type page. It happens when I click on any content type's Edit link or, if I am editing a field or field display, when I click on the Edit tab at the top of the page.
Having said that, it appears it is a problem related to Winamp. The research I have made indicates this can be solved by adding the following statement: max_allowed_packet = 100M to the [mysqld] section of the my.ini file. Services then need to be stopped and restarted.
So far, this fix is working for me.
Thanks for your prompt response.
Cheers.
Comment #3
sprite commentedThis problem may be more generalized than just this module.
This may be a general Drupal bug that is related somehow to MySql version compatibility.
As of today, my local Drupal installation is down because of this same problem.
Nothing I have done has fixed the problem. I have even encountered the problem right after creating a brand new Drupal installation, something I did to diagnose the problem.
Also, I do not have this module installed.
Given the potential commonalities involved, this bug may be related to a version compatibility problem in XAMPP with the version of mysql, apache, and drupal.
I experienced this problem after installing a new theme/template to try out on my local machine test Drupal installation. I can no longer run any Drupal installations locally. After encountering this bug I even tried to create some fresh installations with new Mysql databases. All this installations now experience this severe total failure.
Nothing I have tried has fixed the problem.
(spent a few hours diagnosing this problem)
-----------------------
PDOException: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away: SELECT COUNT(cid) FROM {comment} WHERE status = :status; Array ( [:status] => 0 ) in comment_count_unpublished() (line 313 of C:\__sites\mysite\modules\comment\comment.module).
---
Uncaught exception thrown in session handler.
PDOException: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away in _drupal_session_write() (line 209 of C:\__sites\mysite\includes\session.inc).
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] => 4420179764faf6fdf34fb48.88262114 ) in lock_release_all() (line 269 of C:\__sites\mysite\includes\lock.inc).
Fatal error: Uncaught exception 'PDOException' with message 'SQLSTATE[HY000]: General error: 2006 MySQL server has gone away' in C:\__sites\mysite\includes\database\database.inc:2136 Stack trace: #0 C:\__sites\mysite\includes\database\database.inc(2136): PDOStatement->execute(Array) #1 C:\__sites\mysite\includes\database\database.inc(664): DatabaseStatementBase->execute(Array, Array) #2 C:\__sites\mysite\includes\database\database.inc(2315): DatabaseConnection->query('SELECT expire, ...', Array, Array) #3 C:\__sites\mysite\includes\lock.inc(167): db_query('SELECT expire, ...', Array) #4 C:\__sites\mysite\includes\lock.inc(146): lock_may_be_available('schema:runtime:...') #5 C:\__sites\mysite\includes\bootstrap.inc(405): lock_acquire('schema:runtime:...') #6 C:\__sites\mysite\includes\bootstrap.inc(427): DrupalCacheArray->set(Array) #7 [internal function]: DrupalCacheArray->__destruct() #8 {main} thrown in C:\__sites\mysite\includes\database\database.inc on line 2136
Comment #4
sprite commentedI solve this problem with the following fix, post by someone in another thread:
This has to do with maximum allowed packet size in MySQL.
To solve, add in the [mysqld] section in my.ini: max_allowed_packet=100M and restart MySQL
(other thread)
http://drupal.org/node/1014172
Comment #5
wim leersSeems like it wasn't a HS problem after all.
Comment #6
SharonD214@aol.com commentedAwesome, Thanks
Sharon
Comment #7
Aksharpanziar commentedYou da best... :)
Comment #8
beumont commentedWorks for me as well! Their are more database configuration options you can set for performance:
https://www.drupal.org/node/259580