Additional uncaught exception thrown while handling exception.

I am also facing same problem in my project. I had configured drupal 7 in my local window machine. Sometimes page become blank and by pressing F5 it comes again.

some times I found same error message in my project.

Please give me solution....

That may make the event not happen, but it doesn't address the UX issue of telling the ordinary user what to do. All error messages should start out with advice to an ordinary user of what they should do. They can then put up more info that pertains to a system administrator, labeled as such so the ordinary user can ignore it. The other side of this coin is the obnoxious "Ask your system administrator.", but what if I am the system administrator? There are no clues about what to do next. I am sure that more info was available in the code where the error message was formatted and could have been included.

im in the same boat! Help! called go daddy and a tacky as heck guy was playing the smart ass instead of helping....

I was able to resolve mine after updating to the current beta of the media module + banner rotation modules.

From what I understand the media module is changing rapidly. there is a chance that you auto-updated your site to a newer version of a module incompatible with your current version of the media module. thats how I got myself in trouble. : )

I no longer remember any details about what I was doing that caused me to get the error message, and likely at this point many months later, that particular bug is gone. My issue is purely a UX issue about how to write error messages so that all levels of users from non-techy user, to site admin user, to developer, all get messages at a level of detail that is relevant and understandable by them. This particular one, was probably only understandable by a developer.

where's the .cnf file located? i'm working on a localhost

It works! Thanks!
I use xampp on windows 7. Encountered the same problem.
Changed max_allowed_packet to 20M in xampp\mysql\bin\my.ini , finish.

Hi,

You can make the changes in code in my.ini with reference of attached patch.

I came across the same issue and fixed it by increasing the 'max_allowed_packet' limit to '16M'

here are the steps i followed on my xampp, localhost

1. Go to xampp\mysql\bin
2. Open my.ini
3. Change "max_allowed_packet" from "1m" to "16m" (or larger)
4. Save my.ini Now restart MySql through the XAMPP control panel.

hi i have the same issue but its even worst i can't access my content menu and can't run cron please help my job depends on it

Additional uncaught exception thrown while handling exception.

Original

PDOException: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away: SELECT uid, name, picture, data FROM {users} WHERE uid IN (:uids_4, :uids_34, :uids_35, :uids_36, :uids_37, :uids_38, :uids_39, :uids_41, :uids_42, :uids_44, :uids_55, :uids_56, :uids_57, :uids_58, :uids_59, :uids_78, :uids_79, :uids_80, :uids_81, :uids_83, :uids_85, :uids_96, :uids_97, :uids_98, :uids_101, :uids_107, :uids_110, :uids_113, :uids_120, :uids_129, :uids_135, :uids_138, :uids_140, :uids_142, :uids_143, :uids_144, :uids_150, :uids_151, :uids_152, :uids_166, :uids_167, :uids_168, :uids_173, :uids_182, :uids_183, :uids_185, :uids_186, :uids_187, :uids_188, :uids_190); Array ( [:uids_4] => 1 [:uids_34] => 1 [:uids_35] => 1 [:uids_36] => 1 [:uids_37] => 1 [:uids_38] => 1 [:uids_39] => 1 [:uids_41] => 1 [:uids_42] => 1 [:uids_44] => 1 [:uids_55] => 1 [:uids_56] => 1 [:uids_57] => 1 [:uids_58] => 1 [:uids_59] => 1 [:uids_78] => 7 [:uids_79] => 7 [:uids_80] => 7 [:uids_81] => 7 [:uids_83] => 7 [:uids_85] => 7 [:uids_96] => 7 [:uids_97] => 7 [:uids_98] => 7 [:uids_101] => 7 [:uids_107] => 7 [:uids_110] => 7 [:uids_113] => 7 [:uids_120] => 7 [:uids_129] => 7 [:uids_135] => 7 [:uids_138] => 7 [:uids_140] => 7 [:uids_142] => 7 [:uids_143] => 7 [:uids_144] => 7 [:uids_150] => 7 [:uids_151] => 7 [:uids_152] => 15 [:uids_166] => 7 [:uids_167] => 7 [:uids_168] => 7 [:uids_173] => 7 [:uids_182] => 15 [:uids_183] => 15 [:uids_185] => 15 [:uids_186] => 15 [:uids_187] => 15 [:uids_188] => 15 [:uids_190] => 15 ) in user_node_load() (line 3563 of /var/www/html/modules/user/user.module).

Additional

PDOException: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away: INSERT INTO {watchdog} (uid, type, message, variables, severity, link, location, referer, hostname, timestamp) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3, :db_insert_placeholder_4, :db_insert_placeholder_5, :db_insert_placeholder_6, :db_insert_placeholder_7, :db_insert_placeholder_8, :db_insert_placeholder_9); Array ( [:db_insert_placeholder_0] => 7 [:db_insert_placeholder_1] => php [:db_insert_placeholder_2] => %type: !message in %function (line %line of %file). [:db_insert_placeholder_3] => a:6:{s:5:"%type";s:12:"PDOException";s:8:"!message";s:1843:"SQLSTATE[HY000]: General error: 2006 MySQL server has gone away: SELECT uid, name, picture, data FROM {users} WHERE uid IN (:uids_4, :uids_34, :uids_35, :uids_36, :uids_37, :uids_38, :uids_39, :uids_41, :uids_42, :uids_44, :uids_55, :uids_56, :uids_57, :uids_58, :uids_59, :uids_78, :uids_79, :uids_80, :uids_81, :uids_83, :uids_85, :uids_96, :uids_97, :uids_98, :uids_101, :uids_107, :uids_110, :uids_113, :uids_120, :uids_129, :uids_135, :uids_138, :uids_140, :uids_142, :uids_143, :uids_144, :uids_150, :uids_151, :uids_152, :uids_166, :uids_167, :uids_168, :uids_173, :uids_182, :uids_183, :uids_185, :uids_186, :uids_187, :uids_188, :uids_190); Array ( [:uids_4] => 1 [:uids_34] => 1 [:uids_35] => 1 [:uids_36] => 1 [:uids_37] => 1 [:uids_38] => 1 [:uids_39] => 1 [:uids_41] => 1 [:uids_42] => 1 [:uids_44] => 1 [:uids_55] => 1 [:uids_56] => 1 [:uids_57] => 1 [:uids_58] => 1 [:uids_59] => 1 [:uids_78] => 7 [:uids_79] => 7 [:uids_80] => 7 [:uids_81] => 7 [:uids_83] => 7 [:uids_85] => 7 [:uids_96] => 7 [:uids_97] => 7 [:uids_98] => 7 [:uids_101] => 7 [:uids_107] => 7 [:uids_110] => 7 [:uids_113] => 7 [:uids_120] => 7 [:uids_129] => 7 [:uids_135] => 7 [:uids_138] => 7 [:uids_140] => 7 [:uids_142] => 7 [:uids_143] => 7 [:uids_144] => 7 [:uids_150] => 7 [:uids_151] => 7 [:uids_152] => 15 [:uids_166] => 7 [:uids_167] => 7 [:uids_168] => 7 [:uids_173] => 7 [:uids_182] => 15 [:uids_183] => 15 [:uids_185] => 15 [:uids_186] => 15 [:uids_187] => 15 [:uids_188] => 15 [:uids_190] => 15 ) ";s:9:"%function";s:16:"user_node_load()";s:5:"%file";s:38:"/var/www/html/modules/user/user.module";s:5:"%line";i:3563;s:14:"severity_level";i:3;} [:db_insert_placeholder_4] => 3 [:db_insert_placeholder_5] => [:db_insert_placeholder_6] => http://www.icare.com/admin/content [:db_insert_placeholder_7] => http://www.icare.com/admin/modules [:db_insert_placeholder_8] => 173.162.124.90 [:db_insert_placeholder_9] => 1340815281 ) in dblog_watchdog() (line 157 of /var/www/html/modules/dblog/dblog.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 /var/www/html/includes/session.inc).

hey thanks for the reply i found out the node i created gave me an error and the only way to fix it it was going inside the database phpmyadmin and erase that node as for the error i think it happened because i dropped a couple of images through ckeditor and after that couldnt access the content area

I'm running into this rather frequently in trying to do a site re-build on my test server (virtual install of Ubuntu running LAMPP). All I am doing at this point is enabling modules at this point, so I've been wondering if there is a timing (memory) issue going on somewhere. I know there used to be a tweak I had to do for my installs of XAMPP when I was running that on my Windows machine to resolve oddball memory issues. Even worse, I can't find my notes on this as it has been such a long time since I've run into this since going to the virtual install. I could have sworn it involved modifying the .htaccess file found in the Drupal root directory, but I don't see that in these installs for Drupal 7.

Oh, and just doing a refresh of the page is NOT getting rid of the error as someone indicated at the top of this issue report.

using MAMP, do no works for me, problem stills

i am getting crazy with this error ¡¡¡

I have this error:

Additional uncaught exception thrown while handling exception.

Original

PDOException: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away: SELECT * FROM {commerce_flat_rate_service}; Array ( ) in commerce_flat_rate_commerce_shipping_service_info() (line 120 of C:\xampp\htdocs\comercio\profiles\commerce_kickstart\modules\contrib\commerce_flat_rate\commerce_flat_rate.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 409 of C:\xampp\htdocs\comercio\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 209 of C:\xampp\htdocs\comercio\includes\session.inc).

how to fix this problem with having cpanel access only?

Thank you so!! Good solution for me ;-)
*****
Muchas gracias!! Buena solucion para mi ;-)

#30 and #32 worked for me. THANKS!!!

Error 2006 is very common in Drupal 7 but not a problem with the build as some speculate.

Symptoms:

Original

PDOException: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away: DELETE FROM {cache} WHERE (cid LIKE :db_condition_placeholder_0 ESCAPE '\\') ; Array ( [:db_condition_placeholder_0] => entity\_info:% ) in cache_clear_all() (line 163 of D:\wamp\www\dev7\includes\cache.inc).

Additional

PDOException: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away: SELECT filename FROM {registry} WHERE name = :name AND type = :type; Array ( [:name] => OgMembershipTypeUIController [:type] => interface ) in _registry_check_code() (line 3091 of D:\wamp\www\dev7\includes\bootstrap.inc).

Primary Problem:

1) The server timed out and closed the connection which is the most common cause.

Solutions to Problem 1:

1) The first thing to check is the wait_timeout variable in the my.cnf or my.ini config file. You may need to increase the time for it to work. By just increasing the memory allocation may allow more data through-put but may not provide enough time window for the data to be processed. You may try setting the wait_timeout to about 600 seconds and adjust it even higher once error 2006 has vanished. When you restart mysql the wait_timeout should be near 28800 seconds or just about 8 hours or so.

2) The server might have received a package of data too large to process which is the second common problem. The best way to resolve this common problem is to go into the my.cnf or my.ini files and change the max_allowed_packet to 64M and that should resolve the problem. It is best to do both in order to resolve this issue.