max_allowed_packet error despite being set to 256M

[GherkinDilds]

I have recently been getting max_allowed_packets errors. I figured it was just a typically MySQL config issue, with a simple tweak to my.cnf.

I checked my my.cnf and found that max_allowed_packet was set to 256M, much higher than the recommended 18M.

What could be causing this? It happened after enabling a module on my Drupal site.

The error is giant (several scroll length) and starts with "user warning: Got a packet bigger than 'max_allowed_packet' bytes query: UPDATE cache_update SET data =....."

See previous thread dealing with issue (#1153 - Got a packet bigger than 'max_allowed_packet' bytes on database import)

[Ron]

Since last time support just did an import for you, we never really found out what was causing the issue. I think they said they increased it to 17M instead of 16M, and that it worked fine. If I recall, you had already said that your configuation file had a higher value. I don't recall, did you run the mysql command

show session variables like "%packet%";

to see what your server was actually reporting for max packet size in spite of your config setting?

[Ron]

My shared server:

mysql> show session variables like "%packet%";
+--------------------+----------+
| Variable_name      | Value    |
+--------------------+----------+
| max_allowed_packet | 52428800 |
+--------------------+----------+
1 row in set (0.01 sec)

mysql>

[JPC-Bilal]

Hi GherkinDilds,

Please open a support ticket if you have not already done and Techs will assist you there regarding the issue you are facing. Thank you.

[GherkinDilds]

Hi GherkinDilds,

Please open a support ticket if you have not already done and Techs will assist you there regarding the issue you are facing. Thank you.

I think checked my my.cnf max_allowed_packets was set at 256M. I think the warning is strictly Drupal related and seems to have corrected itself. It may have been because of my high number of modules.

[GherkinDilds]

Backpedalling.

The error seems to be reoccurring. I am not sure whether it is a MySQL/server issue or strictly Drupal related. Suggestions appreciated.