-
Notifications
You must be signed in to change notification settings - Fork 641
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publishing a draft of table field causes internal server error #6122
Comments
i get this error from the web.log:
|
@karltriest The MySQL docs have a whole page dedicated to that "MySQL server has gone away" message (https://dev.mysql.com/doc/refman/8.0/en/gone-away.html), but 9 times out of 10 when we see it, it's because you need to bump your MySQL server's max_allowed_packet and/or wait_timeout settings to higher values. |
@angrybrad I changed the MySQL options to max_allowed_packet to 67108864 (64MB), (default/was 4MB) supposedly the default for wait_timeout on mysql is 28800 (8 hours), so i don't think that was an issue but I added in 28800 just in case. Unfortunately the bug persists. |
@karltriest did you verify the settings took? i.e. If they did, the other setting I've setting that works is bumping |
@angrybrad turns out that it was the max_allowed_packet setting, and the server needed a reboot in order for the setting to take. |
@karltriest glad you're all sorted! |
Description
making a draft of a table field then publishing that draft causes "An internal server error occurred."
Steps to reproduce
*note: publishing the exact same data without first making a draft works fine
Additional info
Activity Log | 1.0.1
Amazon SES | 1.3.0
Craft Color Mixer | 1.0.9
Logs | 3.0.3
Redactor | 2.6.1
Sprout Forms | 3.11.7
Transient | 1.0.0
Twig Perversion | 2.1.0
Error Log
The text was updated successfully, but these errors were encountered: