Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Keep running into into the "max_allowed_packet" error msg, which to data I've just guessed at what the number should be....

I'd like to stop guessing, and know how to see what the number should be -- and it appears that info might be in the database table info in the "Data_length" column.

Is that correct, and if so, how do I calculate the value to enter in the MySQL config to avoid the error before I get it.

(If it matters, I keep getting these errors on DB restores.)

Questions, feedback, requests -- just comment, thanks!!

Additional info: The database is INNOdb, not MyISAM.


In an effort to find a way to benchmark the "max_packet" I did the following, ran the restore, got the error with the line number causing the error, dumped that line into a text file to measure the file size.


ERROR 1153 (09S01) at line 2742: Got a packet bigger than "max_allowed_packet" bytes

SED code:


Problem is... that line is only 8mb, "max_allowed_packet" is set to 100mb.

share|improve this question
up vote 1 down vote accepted

I'm not 100% sure how to profile a max_allowed_packet situation. But I know I have gotten a ~3 gig database export to import on a max_allowed_packet size of 100mb. What I usually do is just set it arbitrarily high, import the data then set it back down to 1M and restart mysqld.

share|improve this answer
@lilott8: Interesting, but that's just guessing -- and I'm guessing if you're resetting to 1M after import, there's no need to set it to 100mb on import; reason being that error does not just happen on import, but also on INSERT based on my experience. All that said, I really have no idea -- hence the request for a way to know how to find answer. – blunders Mar 4 '11 at 15:42
Right, it would happen on both an import and an INSERT. The mysqldump script will be utilizing the INSERT command. We can start to think through this.... In your error logs there should be something regarding the problematic INSERT statements. If not turn all logging on full force through your Run a few test cases and see what's in those logs. You can then start setting your max_allowed_packet size based on those INSERTS. – lilott8 Mar 4 '11 at 15:46
@lilott8: +1 That's a pretty brute force approach, plus I'm loading almost 100-million rows; which is taking an few hours, don't have time being debugging the max-packet-size that way. Thanks though!!! – blunders Mar 4 '11 at 15:58
well, everything I read just says: "put it as high as needed" so I don't know that there is a way to calculate this value. I think best guessing might be the only way to go. Which is a bummer. I'll keep looking but it doesn't look too promising :( Are you getting any other errors that might suggest key or index buffer sizes could be the problem? Or just what you've described already? – lilott8 Mar 4 '11 at 16:44
The max_allowed_packet defines the (select or insert) size of a Query statement. So you're effectively allowing a query to take place that is 120MB big. An example: If you have a large 70M file stored in the DB as a BLOB you can select it and insert it with a max_allowed_packet size of 100MB. Does that make sense or help? – lilott8 Mar 4 '11 at 17:03

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.