GNU bug report logs - #25415
MySQL "server has gone away" when reloading database dump due to "max_allowed_packet" default

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: zimoun <zimon.toutoune <at> gmail.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#25415: closed (MySQL "server has gone away" when reloading
 database dump due to "max_allowed_packet" default)
Date: Thu, 23 Jun 2022 10:03:04 +0000

[Message part 1 (text/plain, inline)]

Your message dated Thu, 23 Jun 2022 11:54:10 +0200
with message-id <86wnd77lj1.fsf <at> gmail.com>
and subject line Re: bug#25415: MySQL "server has gone away" when reloading database dump due to "max_allowed_packet" default
has caused the debbugs.gnu.org bug report #25415,
regarding MySQL "server has gone away" when reloading database dump due to "max_allowed_packet" default
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
25415: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25415
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Ben Sturmfels <ben <at> stumbles.id.au>
To: bug-guix <at> gnu.org
Subject: MySQL "server has gone away" when reloading database dump due to
 "max_allowed_packet" default
Date: Wed, 11 Jan 2017 11:10:03 +1100

Hi there!

I'm using GuixSD 0.12.0 and ran `guix package --install=mysql` (which
I gather gave me MariaDB 10.1.19), then created a database and tried to
reload a database dump of a decent sized existing database:

  zcat dump.sql.gz | mysql DBNAME

which failed with:

  ERROR 2006 (HY000) at line 2266: MySQL server has gone away

Reloading the same dump works for me on default MySQL in Trisquel 7.
The database dump was created on Debian with `mysqldump --no-create-db
DBNAME`.

On Guix, I was able to reload the dump by running mysqld with a custom
config file with max_allowed_packet=16M under [mysqld].

It appears that the default value for `max_allowed_packet` under
Debian/Trisquel is "16M", where under Guix it is "4M". The mysqldump
defaults bunche a whole lot of records into a single insert statement
for performance, which is why I'm getting a value > 4M.

Could it be worth setting max_allowed_packet to 16M in Guix's
`mysql-configuration-file` function for consistency with Debian?

Regards,
Ben

[Message part 3 (message/rfc822, inline)]

From: zimoun <zimon.toutoune <at> gmail.com>
To: 25415-done <at> debbugs.gnu.org
Subject: Re: bug#25415: MySQL "server has gone away" when reloading database
 dump due to "max_allowed_packet" default
Date: Thu, 23 Jun 2022 11:54:10 +0200

On Wed, 05 Jan 2022 at 00:00, zimoun <zimon.toutoune <at> gmail.com> wrote:
> On Fri, 26 Nov 2021 at 02:51, zimoun <zimon.toutoune <at> gmail.com> wrote:
>> On Tue, 12 Oct 2021 at 23:42, zimoun <zimon.toutoune <at> gmail.com> wrote:
>>> On Tue, 14 Sep 2021 at 13:51, zimoun <zimon.toutoune <at> gmail.com> wrote:
>>>> On Fri, 13 Jan 2017 at 10:29, Ben Sturmfels <ben <at> stumbles.id.au> wrote:
>>>>> On 13/01/17 01:22, Ludovic Courtès wrote:

> The bug is open since 2017 without any inputs despite my 3 questions.
> Therefore, I will close it in one month from now if there is no more
> interest in.  The backlog is already enough long. :-)

Done.


Cheers,
simon

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.