Module causes Drupal status messages to build up

Thanks for tracking this down, but is this really the ultimate solution? Is there any particular reason why the call to menu_tree_all_data is hitting the max_allowed_packet limit?

In my installation, I have updated the my.cnf file for MySQL to include max_allowed_packet = 5M, I've restarted MySQL, and the status message problem persists.

I have the same problem in a local installation. Changing the max_allowed_packet directive doesn't do nothing.
It wasn't occuring to me before on a linux instalation, and now on Mac with Mamp, it occure, and like other people say, it is caused by admin menu, but this module is very useful, so i hope someone find a solution.

This issue cannot be fixed in admin_menu 1.x. The new 3.x entirely re-uses Drupal core's menu system to build its menu.

I had the same problem with 6.x-1.5 when I was importing content types through Node import 6.x-1.0-rc4 module. I've imported many content types and then suddenly.. right after importing a content type.. boom.. the messagesssssss... they are indeed driving me K-razy too. So I'm now using 6.x-3.x-dev and so far no problems. But I'll write again if I encounter this again with 6.x-3.x-dev.

Edited: yeah well when I'm editing a content type (admin/content/type/mycontenttype/edit) I'm getting a message like this: user warning: Got a packet bigger than 'max_allowed_packet' bytes query: UPDATE cache_menu SET data = "and here a 50 pages string of stuff that I don't understand".. so yeah, still in development huh? Is there a way to minimize or reset that packet stuff? I've got now 175 tables in my db (don't know if that is much or not).. Also, when I then click on the manage fields button my admin menu disappears. Hope this info is useful to the developers. ;-)

I'm switching back to admin_menu 6.x-1.5 as in 6.x-3.x-dev the "create content" link disappeared and I get a "huge" message every time I click on Edit a content type or create a new node.. so I can stand the annoying remaining messages now..

Hi fellas

I solved it by doing a "Wipe and Rebuild", thats a button in the settings of admin menu

I also dincreased the max_allowed_packet but I don't know if that was also a required step. Tried it also if it does not work

I know you guys have the great intention to code something brilliant and it was for a long time for me. I'm also aware that you are in need for serious help but I'm not a coder at all so I'm uninstalling this module, this issue just drives me nuts and I think it's odd to state: "won't fix"... . So sorry. I hope to become one of your users again.

@BassPlaya: The problem really is the menu system in Drupal 6 (see also the project page). If it makes you happy in any way, I can tell you that admin_menu works just awesomely in D7 ;)

Maybe I'm judging too fast... it might be so that it is just some kind of MySQL setting... I'm still figuring out what "exactly" caused this.. to be continued. I've created on my local server a "my.cnf" file that I copied from the following path: Applications/MAMP/Library/share/mysql/my-small.cnf
I changed the ports from 9999 to 8888 and changed the "max_allowed_packet" to 16M instead of 1M. I renamed it to "my.cnf" when I copied it to Applications/MAMP/Library/ and then restarted the servers. That worked. But my site is soooooooo slowwwaaah..darn slow.
I enabled the Administration menu again and now it seems that the messages are gone.
I'll follow up later to see if I can speed up my site and if I could set the max_allowed_packet back to 1M to see what caused it.

@ sun: I suspect that the actual cause lies with the node import module as I had the problem twice (reinstalled a working db) after importing a certain amount of nodes. I'm trying to figure it out..
D7 you say, well yeah but not everybody's ready for that you know, certainly not the modules but YES I'm looking forward to D7 :-)

A max_allowed_packet of 16M is ok, and usually needed for various Drupal modules. admin_menu adds to the game, but not exclusively. max_allowed_packet has no impact on performance though.

You used my-small.cnf as template. That's intended for really small, only occasionally used database servers only. I'd recommend to use the default + tweak max_allowed_packet.

The performance of MySQL can be analyzed + tweaked via https://launchpad.net/mysql-tuning-primer

Hye Sun,

Thanx for the advice. I've created this my.cnf file from the my-medium.cnf file under the share folder and increased the max_allowed_packet to 16M which solved my problem. For people who don't know how to do this on a local install with MAMP, check out this link: http://drupal.org/node/66187
I must say that node-import module, admin_menu module and imagecache module were the ones where I started getting this annoying bug.. I'm not sure what it will do for my hosting once uploaded.. I'll keep you guys posted here, I might bump into some useful info later on..

Ran into this problem too, ensured the following was in my.cnf and restarted MySQL:

[mysqld]
max_allowed_packet=16M 

Worked like a charm.

For people this isn't working for, make sure the setting is in my.cnf's [mysqld] section, and if 5M doesn't work, try a higher number (16M is the default for the mysql client program, so should be perfectly suitable for a local Drupal install). Also, make sure to verify the setting has taken effect (ie, on phpMyAdmin's Variables page)

This thread helped me sort the problem so I wanted to pass along the steps I used to fix it. I wrote it all up here: http://bit.ly/az6OZP on my blog. It's specific to my Media Temple (dv) setup, but should be general enough and have enough sources to help others as well. It's definitely solved by using the MySQL configuration change. Not using the Admin Menu module was a problem for me - I use it all the time - so I was happy to sort it out without scrapping the module.

Hope that helps.

Jason