Posted by kenorb on July 9, 2009 at 12:17pm
5 followers
| Project: | Administration menu |
| Version: | 6.x-3.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (duplicate) |
Issue Summary
This should be optimized somehow.
Currently I've got query:
UPDATE cache_menu SET data = 'a:2:{s:4:\\\"tree\\\";a:127:{i:6202;a:2:{s:4:\\\"link\\\";a:37:{s:14:\\\"load_functions\\\";s:0:\\\"\\\";s:16:\\\"to_arg_functions\\\";s:0:\\\"\\\";s:15:\\\"access_callback...more than 1MB long which generates the watchdog error:
"INSERT INTO watchdog\n (uid, type, message, variables, severity, link, location, referer, hostname, timestamp)\n VALUES\n (1, 'php', '%message in %file on line %line.', 'a:4:{s:6:\\\"%error\\\";s:12:\\\"user warning\\\";s:8:\\\"%message\\\";s:1879771:\\\"MySQL server has gone away\\nquery: UPDATE cache_menu SET data = 'a:2:{s:4:\\\\"tree\\\\";a:127:{i:6202;a:2:{s:4:\\\\"link\\\\";a:37:{s:14:\\\\"load_functions\\\\";s:0:\\\\"\\\\";s:16:\\\\"to_arg_functions\\\\";s:0:\\\\"\\\\";s:15:\\\\"access_callback\\\\";s:11:\\\\"user_access\\\\";s:16:\\\\"access_arguments\\\\";s:42:\\\\"a:1:{i:0;s:24:\\\\"view advanced help index\\\\";}\\\\";s:13:\\\\"page_callback\\\\";s:24:\\\\"advanced_help_index_page\\\\";s:14:\\\\"page_arguments\\\\";s:6:\\\\"a:0:{}\\\\";s:5:\\\\"title\\\\";s:13:\\\\"Advanced help\\\\";s:14:\\\\"title_callback\\\\";s:1:\\\\"t\\\\";s:15:\\\\"title_arguments\\\\";s:0:\\\\"\\\\";s:4:\\\\"type\\\\";s:1:\\\\"6\\\\";s:11:\\\\"description\\\\";s:0:\\\\"\\\\";s:9:\\\\"menu_name\\\\";s:10:\\\\"admin_menu\\\\";s:4:\\\\"mlid\\\\";s:4:\\\\"6202\\\\";s:4:\\\\"plid\\\\";s:1:\\\\"0\\\\";s:9:\\\\"link_path\\\\";s:19:\\\\"admin/advanced_help\\\\";s:11:\\\\"router_path\\\\";s:19:\\\\"admin/advanced_help\\\\";s:10:\\\\"link_title\\\\";s:13:\\\\"Advanced help\\\\";s:7:\\\\"options\\\\";s:6:\\\\"a:0:{}\\\\";s:6:\\\\"module\\\\";s:6:\\\\"system\\\\";s:6:\\\\"hidden\\\\";s:1:\\\\"0\\\\";s:8:\\\\"external\\\\";s:1:\\\\"0\\\\";s:12:\\\\"has_children\\\\";s:1:\\\\"0\\\\";s:8:\\\\"expanded\\\\";s:1:\\\\"0\\\\";s:6:\\\\"weight\\\\";s:1:\\\\"9\\\\";s:5:\\\\"depth\\\\";s:1:\\\\"1\\\\";s:10:\\\\"customized\\\\";s:1:\\\\"0\\\\";s:2:\\\\"p1\\\\";s:4:\\\\"6202\\\\";s:2:\\\\"p2\\\\";s:1:\\\\"0\\\\";s:2:\\\\"p3\\\\";s:1:\\\\"0\\\\";s:2:\\\\"p4\\\\";s:1:\\\\"0\\\\";s:2:\\\\"p5\\\\";s:1:\\\\"0\\\\";s:2:\\\\"p6\\\\";s:1:\\\\"0\\\\";s:2:\\\\"p7\\\\";s:1:\\\\"0\\\\";s:2:\\\\"p8\\\\";s:1:\\\\"0\\\\";s:2:\\\\"p9\\\\";s:1:\\\\"0\\\\";s:7:\\\\"updated\\\\";s:1:\\\\"0\\\\";s:15:\\\\"in_active_trail\\\\";b:0;}s:5:\\\\"below\\\\";b:0;}i:6204;a:2:{s:4:\\\\"link\\\\";a:37:{s:14:\\\\"load_functions\\\\";s:0:\\\\"\\\\";s:16:\\\\"to_arg_functions\\\\";s:0:\\\\"\\\\";s:15:\\\\"access_callback\\\\";s:11:\\\\"user_access\\\\";s:16:\\\\"access_arguments\\\\";s:45:\\\\"a:1:{i:0;s:27:\\\\"access administration pages\\\\";}more than 2MB size.
Comments
#1
See screenshot.
#2
cache_menu belongs to Drupal core, and this query belongs to Drupal core. admin_menu is not related in any way here. Please search for existing issues for Drupal core instead.
#3
#327066: Warning: MySQL server has gone away: recursive error reporting
#4
hi, i always has this problem when building site using localhost. the trick is to disable all modules that you are not using. i repeat - ALL modules you dont use. it has something to do with prosessing memory.
#5
I disabled all modules that I don't use and have increased packet size and memory limit and still have lots of these kinds of warnings. I am using Drupal 6.22.
#6
Same here. Subscribing