• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

how to increase max_allowed_packet?

Sven L.

Regular Pleskian
Hi,

migrating some stuff from 9.5.4 to 11.5 and i get an warning in the migration manager about max_allowed_packet

i have tried to find some information how to increase this limit (seems like it's at 1M and i would like it to be 2-4M) but everything points me to old folders that no longer seem to be relevant.

how can i achieve this in plesk 11.5?
 
Just add

Code:
max_allowed_packet=4M

in your /etc/my.cnf (in [mysqld] section) and then do:

service mysqld restart
(or whatever you need to do to restart MySQL in your Linux flavour)
 
does this change survive through updates or will I have to do that everytime?

Plesk doesn't touch MySQL settings so you are safe there.

Indeed, as a rule of thumb, it doesn't touch any configuration file in /etc/ unless it is necessary in order to achieve what you ask it to do (e.g. /etc/named/* when you add/edit a domain, and similarly with apache).

The design methodology of Plesk is to decouple it as much as possible from OS, so that updates to Plesk have a minimal impact on your system's settings. Of course there are some big changes during installation - just not during updates. (by updates I mean MU installation not full version upgrades, which sometimes have to make bigger changes)
 
Back
Top