Download & Extend

Max_Allowed_Packet Error Upon Module Activation

Project:Private
Version:6.x-1.1
Component:Code
Category:support request
Priority:critical
Assigned:Unassigned
Status:closed (fixed)

Issue Summary

When attempting to activate this module, I received the following error:

Warning: Got a packet bigger than 'max_allowed_packet' bytes query: INSERT INTO watchdog (uid, type, message, variables, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', '%message in %file on line %line.', 'a:4:{s:6:\"%error\";s:12:\"user warning\";s:8:\"%message\";s:2366442:\"Got a packet bigger than 'max_allowed_packet' bytes\nquery: UPDATE batch SET token = '125cbd2e31dbea8884643546864565cb', batch = 'a:10:{s:4:\\"sets\\";a:2:{i:0;a:10:{s:7:\\"sandbox\\";a:0:{}s:7:\\"results\\";a:0:{}s:7:\\"success\\";b:0;s:5:\\"title\\";s:37:\\"Rebuilding content access permissions\\";s:10:\\"operations\\";a:1:{i:0;a:2:{i:0;s:36:\\"_node_access_rebuild_batch_operation\\";i:1;a:0:{}}}s:8:\\"finished\\";s:35:\\"_nod in /var/home/domain/domain.com/www/site/includes/database.mysql.inc on line 128

Warning: Got a packet bigger than 'max_allowed_packet' bytes query: INSERT INTO watchdog (uid, type, message, variables, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', '%message in %file on line %line.', 'a:4:{s:6:\"%error\";s:12:\"user warning\";s:8:\"%message\";s:3112038:\"Got a packet bigger than 'max_allowed_packet' bytes\nquery: UPDATE sessions SET uid = 1, cache = 0, hostname = '127.0.0.1', session = 'views|N;messages|a:2:{s:6:\\"status\\";a:1:{i:0;s:42:\\"The configuration options have been saved.\\";}s:5:\\"error\\";a:1:{i:0;s:2366547:\\"user warning: Got a packet bigger than 'max_allowed_packet' bytes\\nquery: UPDATE batch SET token = '125cbd2e31dbea8882323467586565cb', batch = 'a:10:{s:4:\\\\"sets\\\\"; in /var/home/domain/domain.com/www/site/includes/database.mysql.inc on line 128

Comments

#1

Category:bug report» support request
Status:active» fixed

This is a mysql configuration and is probably not related to the "private" module itself, but related to your hosting configuration in general.

If you search the forums you'll see hundreds of examples of situations like this.

http://www.google.com/search?q=site%3Adrupal.org%20max_allowed_packet

#2

Status:fixed» closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

nobody click here