On a WAMP stack, I'm getting the error below repeated several times (about 10 at login, to be exact, and they remain). Ideas?
Warning: MySQL server has gone away query: INSERT INTO watchdog (uid, type, message, variables, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', '%message in %file on line %line.', 'a:4:{s:6:\"%error\";s:12:\"user warning\";s:8:\"%message\";s:2324:\"MySQL server has gone away\nquery: UPDATE cache SET data = 'a:8:{s:6:\"ctools\";a:1:{s:16:\"ctools_export_ui\";O:8:\"stdClass\":3:{s:8:\"filename\";s:53:\"modules/ctools/plugins/export_ui/ctools_export_ui.inc\";s:8:\"basename\";s:20:\"ctools_export_ui.inc\";s:4:\"name\";s:16:\"ctools_export_ui\";}}s:21:\"ctools_access_ruleset\";a:1:{s:21:\"ctools_access_ruleset\";O:8:\"stdClass\":3:{s:8:\"filename\";s:80:\& in C:\wamp\www\drupal\includes\database.mysqli.inc on line 135
I have tried extending time limits in php.ini. At first, I thought some out-of-scheme tables in the database were the cause, but that only removed the notice temporarily. I think upon addition of a new CCK content type (with several unlimited multi-value fields), the problem came back. Though that could be illogical, of course :)
Status report results leave me several more avenues to explore (continue to clean up mismatched and extra tables, an undefined path to a TCPDF library, and the following note: "Field priorities.timestamp: no Schema type for mysql type timestamp."
Why am I posting before all options are exhausted? Even if the "fixing" of those status report error messages yields something, I am not sure I have a technical explanation of what went wrong. IF IF IF this is something obvious and a more code-focused explanation for this newbie is on the tip of one's keyboard, I'm most interested. Owise, thanks for reading, and I'll keep on keeping on with cleaning up my status report.
Many thanks to all!
Comments
have you tried disabling
have you tried disabling syslog and database logging?
i have also read that this is a MySQL server issue.. check this out http://drupal.org/node/259580
no, but I certainly will
i would never in a million years, given my newbie status, thought of those possibilities....didn't even know about them. more to learn. very cool. thanks!
Had this same problem
I had this problem on a site a few months ago. In looking for a fix, I found that some people were able to fix this by boosting the max_allowed_packet size, but that didn't help me. A little more digging, and I found that wait_timeout and interactive_timeout were both set to 30 seconds - boosting that was what fixed it.
I would take a look at max_allowed_packet and if that doesn't fix it, check that wait_timeout and interactive_timeout aren't set too low. I doubt it would be those, based on how often you're seeing the error, but you might want to confirm that they aren't set really low.
phew
thanks! i was running out of options, and now my checklist is a new sign of hope. :) of several possibilities. i'll try to leave Emily Dickinson out of this :)
…Emily Dickinson?
…Emily Dickinson?
file names -- it's the first line that get's into greeting cards
having a little trouble finding those variables? my.ini, php.ini, the database include file itself???? sorry such detail required.....
657
I dwell in Possibility--
A fairer House than Prose--
More numerous of Windows--
Superior--for Doors--
Of Chambers as the Cedars--
Impregnable of Eye--
And for an Everlasting Roof
The Gambrels of the Sky--
Of Visitors--the fairest--
For Occupation--This--
The spreading wide my narrow Hands
To gather Paradise--
--Emily Dickinson
With a default wamp install
With a default wamp install it's my.ini, if you have the icon in the system tray left click, head to mysql and it should be in that menu. I just recently had the same issue and this cleared it right up for me. Make sure you restart mysql after editing the file.
timout
thanks....it was those _timeout variables that stumped me....I'll keep at it....
In a wamp install they are
In a wamp install they are not in the file by default (at least I don't think and in the most current build). Add them at the end of the [wampmysqld] section.
gone for now....
they went away for now....it must have been the max_packet whatev that did it because the only timeout variable I found is still commented out, though I did up
max_input_time = 600 (nothing like over correcting) in the php.ini file....i'll have to figure out some other time :-) how all those various my.ini files work together .... have a great weekend y'all.....