Articles in this section

See more

How to set the value of max_allowed_packet or wait_timeout for MySQL on Plesk server?

Avatar
Alexander Tsmokalyuk
Updated
Follow
Plesk for Windows Plesk for Linux kb: how-to ABT: Group A

Applicable to:

  • Plesk for Linux
  • Plesk for Windows

Question

How to set the value of max_allowed_packet or wait_timeout for MySQL service (which serves client databases)?

Answer

Follow the steps below to achieve the same:

For Linux:
  1. Connect to Plesk server via SSH

  2. Set the max_allowed_packet or wait_timeout value in [mysqld] and [mysqldump] sections of my.cnf file.

    • For Debian/Ubuntu:

      CONFIG_TEXT: /etc/mysql/my.cnf

    • For CentOS/RHEL/CloudLinux:

      CONFIG_TEXT: /etc/my.cnf

    CONFIG_TEXT: [mysqld]
    wait_timeout = 31536000
    max_allowed_packet=32M
    ....
    [mysqldump]
    max_allowed_packet=32M

  3. Restart MySQL service:

    # service mysql restart || service mariadb restart || service mysqld restart 

     

For Windows:
  1. Connect to Plesk server via RDP

  2. Set the max_allowed_packet or wait_timeout value in [mysqld] and [mysqldump] sections of %plesk_dir%Databases\MySQL\my.ini file.

    CONFIG_TEXT: [mysqld]
    wait_timeout = 31536000
    max_allowed_packet=32M
    ....
    [mysqldump]
    max_allowed_packet=32M

    Note: wait_timeout=31536000 is the maximum supported value in MySQL server.

  3. After saving the file, restart MySQL process via Plesk Services Monitor (it can be found in system tray):

    mceclip0.png

Comments

9 comments

Sort by Date Votes
  • Avatar
    Marco Marsala (Edited )

    I increased max_allowed_packet editing the right my.cnf file, and I confirmed using phpMyAdmin that the new value is applying.

    Periodically, max_allowed_packet reset itself to 1024, even lower than MySQL default (that is 4M), crashing the majority of websites relying on MySQL.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    @Marco Marsala

    Hello!
    Such behavior is caused by MySQL Bug.

    See also MySQL forum topic regarding this issue.

    0
    Comment actions Permalink
  • Avatar
    Marco Marsala

    @Ivan Postnikov

    This is classified as “not a bug”. The forum topic says that 3rd party software is running a query to reset the value to 1024.

    My code never run such query. The only 3rd party running on the server is Plesk panel.

    Maybe this is a Plesk issue?

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    @Marco Marsala

    Hello!
    In this case, I would suggest submitting a ticket for Plesk Technical Support, as more detailed investigation is required.

    0
    Comment actions Permalink
  • Avatar
    DHH-SI

    Should Screenshot for Windows Plesk be updated so thick would be on "SQL Server" group or "MySQL56" service and not on "Plesk SQL Server"?

    0
    Comment actions Permalink
  • Avatar
    Alexander Tsmokalyuk

    @Almir The article has been updated, thank you!

    0
    Comment actions Permalink
  • Avatar
    Willy Cevallos

    Thank you

    0
    Comment actions Permalink
  • Avatar
    Edwynn Flores Martínez

    I use centos 7 with plesk 

    For CentOS

    Command: vi /etc/my.cnf

    This code is not visible.

    [mysqld]
    wait_timeout = 31536000
    max_allowed_packet=32M
    ....
    [mysqldump]
    max_allowed_packet=32M

    You need add this line 

    0
    Comment actions Permalink
  • Avatar
    Nelson Leiva

    Hello Edwynn Flores Martínez

    Yes, correct. It is needed to add these parameters in the /etc/my.cnf configuration file.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles