Home / Blogs / webthingee's blog / Drupal Bytes when Max Packets Allowed

Drupal Bytes when Max Packets Allowed

Submitted by webthingee on Thu, 04/02/2009 - 11:00

It seems like every time I set up a new site I eventually see the same screen... not the welcome screen, tho I do see that every time. I'm talking about the

The max_packets_allowed screen!

If you are finding this post, you probably need to find a way to fix it... you probably don't want me to cram in some lame images and funny words... so I'll get right to it... here's my secret to fixing it quick.

  1. Call Hosting Company
  2. Tell them to set my.cnf, remind them it's part of mysql
  3. Please find the section called [mysqld]
  4. and Please change/add max_allowed_packet = 64M
  5. If they bock, I tell them that it is a requirement of the framework I am running on the site... and they usually do it in a few minutes.

Some additional resources if needed

tags: 
drupal
mysql

Comments

9
Submitted by Anonymous (not verified) on Thu, 04/02/2009 - 16:38

Ah, the days of calculating the precise way to ask for support. Sounds like my experience with a whm/cpanel reliant company where the 1st level support knew little beyond the interface they were using.
Submitted by Anonymous (not verified) on Thu, 04/02/2009 - 17:38

Another "fix" is to disable dblog.module.
Submitted by Anonymous (not verified) on Thu, 04/02/2009 - 18:38

The only time I've hit this limit is when I forgot to turn off the Macro recorder in the Developer module. It stores every form submission in a serialized variable, which causes the {variables} table to be huge! Remember, if you're hitting that limit, that means that you're transferring at least 1MB of data from the database during the request, so you may have other performance problems, especially with unserialize() calls. While there are cases where you need to modify my.cnf, it's worth the time to double check your tables to ensure nothing has grown too large. --Andrew
Submitted by Anonymous (not verified) on Fri, 04/03/2009 - 00:37

Dude, either you've got some crazy site that you shouldn't be trying to run on shared hosting, you've got a host that's setup to be doing little more than static HTML pages, or there's a bug in one of your contrib modules or custom code. Drupal + standard contrib modules should never hit this error on a half-decent host, even an eighth-decent host.
Submitted by Anonymous (not verified) on Fri, 04/03/2009 - 08:59

This is all so much easier. I just call myself
Submitted by Mark Elster (not verified) on Wed, 04/22/2009 - 09:44

Yesterday, I came across this issue. Disabling the dblog module is a good solution. However, I started to miss all of the "Recent log entries" goodness. Thanks webthingee. You saved the day! :)
Submitted by evden eve nakliyat (not verified) on Tue, 01/26/2010 - 17:42

Good work! Your post/article is an excellent example of why I keep comming back to read your excellent quality content that is forever updated. Thank you!
Submitted by vtt (not verified) on Wed, 10/28/2009 - 14:30

Thank you for the article ;) Sylvain <a href="http://www.vtt-occasion.fr">Vente vtt</a>
Submitted by dantel modelleri (not verified) on Mon, 02/22/2010 - 12:18

Thanks cooL:=)