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

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 25415 in the body.
You can then email your comments to 25415 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

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 #8 received at 25415 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Ben Sturmfels <ben <at> stumbles.id.au>
Cc: 25415 <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, 12 Jan 2017 15:22:39 +0100

Hi Ben,

Ben Sturmfels <ben <at> stumbles.id.au> skribis:

> 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?

Definitely.  I would add a ‘max-allowed-packet’ field in
<mysql-configuration> in (gnu services databases) and make sure it’s
honored.

Would you like to give it a try?

Thanks for your report!

Ludo’.

Message #11 received at 25415 <at> debbugs.gnu.org (full text, mbox):

From: Ben Sturmfels <ben <at> stumbles.id.au>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 25415 <at> debbugs.gnu.org
Subject: Re: bug#25415: MySQL "server has gone away" when reloading database
 dump due to "max_allowed_packet" default
Date: Fri, 13 Jan 2017 10:29:20 +1100

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

On 13/01/17 01:22, Ludovic Courtès wrote:

>> Could it be worth setting max_allowed_packet to 16M in Guix's
>> `mysql-configuration-file` function for consistency with Debian?
> 
> Definitely.  I would add a ‘max-allowed-packet’ field in
> <mysql-configuration> in (gnu services databases) and make sure it’s
> honored.
> 
> Would you like to give it a try?

Sure, I'll give it a shot!

It looks as though the MariaDB source comes with a settings file for
Debian that includes max-allowed-packet=16M:

  mariadb-XX.XX.XX/debian/additions/my.cnf

Would you recommend adding just max-allowed-packet, or would it be worth
applying all these settings in this file?

Ben

[signature.asc (application/pgp-signature, attachment)]

Message #14 received at 25415 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Ben Sturmfels <ben <at> stumbles.id.au>
Cc: 25415 <at> debbugs.gnu.org
Subject: Re: bug#25415: MySQL "server has gone away" when reloading database
 dump due to "max_allowed_packet" default
Date: Fri, 13 Jan 2017 09:03:41 +0100

Ben Sturmfels <ben <at> stumbles.id.au> skribis:

> On 13/01/17 01:22, Ludovic Courtès wrote:
>
>>> Could it be worth setting max_allowed_packet to 16M in Guix's
>>> `mysql-configuration-file` function for consistency with Debian?
>> 
>> Definitely.  I would add a ‘max-allowed-packet’ field in
>> <mysql-configuration> in (gnu services databases) and make sure it’s
>> honored.
>> 
>> Would you like to give it a try?
>
> Sure, I'll give it a shot!
>
> It looks as though the MariaDB source comes with a settings file for
> Debian that includes max-allowed-packet=16M:
>
>   mariadb-XX.XX.XX/debian/additions/my.cnf
>
> Would you recommend adding just max-allowed-packet, or would it be worth
> applying all these settings in this file?

I’m not famliar with MySQL/MariaDB, but any setting that sounds useful
to you is welcome.

Thanks,
Ludo’.

Message #17 received at 25415 <at> debbugs.gnu.org (full text, mbox):

From: zimoun <zimon.toutoune <at> gmail.com>
To: Ben Sturmfels <ben <at> stumbles.id.au>
Cc: 25415 <at> debbugs.gnu.org, Ludovic Courtès <ludo <at> gnu.org>
Subject: Re: bug#25415: MySQL "server has gone away" when reloading database
 dump due to "max_allowed_packet" default
Date: Tue, 14 Sep 2021 13:51:18 +0200

Hi,

Sorry for the delay about this old bug#25415 [1].

1: <http://issues.guix.gnu.org/issue/25415>

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:
>
>>> Could it be worth setting max_allowed_packet to 16M in Guix's
>>> `mysql-configuration-file` function for consistency with Debian?
>>
>> Definitely.  I would add a ‘max-allowed-packet’ field in
>> <mysql-configuration> in (gnu services databases) and make sure it’s
>> honored.
>>
>> Would you like to give it a try?
>
> Sure, I'll give it a shot!
>
> It looks as though the MariaDB source comes with a settings file for
> Debian that includes max-allowed-packet=16M:
>
>   mariadb-XX.XX.XX/debian/additions/my.cnf
>
> Would you recommend adding just max-allowed-packet, or would it be worth
> applying all these settings in this file?

Well, anything that suits you. :-)  Could you send a patch if it is
relevant?

All the best,
simon

Message #20 received at 25415 <at> debbugs.gnu.org (full text, mbox):

From: zimoun <zimon.toutoune <at> gmail.com>
To: Ben Sturmfels <ben <at> stumbles.id.au>
Cc: 25415 <at> debbugs.gnu.org, Ludovic Courtès <ludo <at> gnu.org>
Subject: Re: bug#25415: MySQL "server has gone away" when reloading database
 dump due to "max_allowed_packet" default
Date: Tue, 12 Oct 2021 23:42:42 +0200

Hi Ben,

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:
>>
>>>> Could it be worth setting max_allowed_packet to 16M in Guix's
>>>> `mysql-configuration-file` function for consistency with Debian?
>>>
>>> Definitely.  I would add a ‘max-allowed-packet’ field in
>>> <mysql-configuration> in (gnu services databases) and make sure it’s
>>> honored.
>>>
>>> Would you like to give it a try?
>>
>> Sure, I'll give it a shot!
>>
>> It looks as though the MariaDB source comes with a settings file for
>> Debian that includes max-allowed-packet=16M:
>>
>>   mariadb-XX.XX.XX/debian/additions/my.cnf
>>
>> Would you recommend adding just max-allowed-packet, or would it be worth
>> applying all these settings in this file?
>
> Well, anything that suits you. :-)  Could you send a patch if it is
> relevant?

Would you like to give a try to fix bug#25415 [1]? :-)

1: <http://issues.guix.gnu.org/issue/25415>

Cheers,
simon

Message #23 received at 25415 <at> debbugs.gnu.org (full text, mbox):

From: zimoun <zimon.toutoune <at> gmail.com>
To: Ben Sturmfels <ben <at> stumbles.id.au>
Cc: 25415 <at> debbugs.gnu.org, Ludovic Courtès <ludo <at> gnu.org>
Subject: Re: bug#25415: MySQL "server has gone away" when reloading database
 dump due to "max_allowed_packet" default
Date: Fri, 26 Nov 2021 02:51:48 +0100

Hi Ben,

I hope you are well.


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:
>>>
>>>>> Could it be worth setting max_allowed_packet to 16M in Guix's
>>>>> `mysql-configuration-file` function for consistency with Debian?
>>>>
>>>> Definitely.  I would add a ‘max-allowed-packet’ field in
>>>> <mysql-configuration> in (gnu services databases) and make sure it’s
>>>> honored.
>>>>
>>>> Would you like to give it a try?
>>>
>>> Sure, I'll give it a shot!
>>>
>>> It looks as though the MariaDB source comes with a settings file for
>>> Debian that includes max-allowed-packet=16M:
>>>
>>>   mariadb-XX.XX.XX/debian/additions/my.cnf
>>>
>>> Would you recommend adding just max-allowed-packet, or would it be worth
>>> applying all these settings in this file?

The bug#25415 [1] is about MySQL and a patch seems required.

Would you like give a try?

1: <http://issues.guix.gnu.org/issue/25415>


Cheers,
simon

Message #26 received at 25415 <at> debbugs.gnu.org (full text, mbox):

From: zimoun <zimon.toutoune <at> gmail.com>
To: Ben Sturmfels <ben <at> stumbles.id.au>
Cc: 25415 <at> debbugs.gnu.org, Ludovic Courtès <ludo <at> gnu.org>
Subject: Re: bug#25415: MySQL "server has gone away" when reloading database
 dump due to "max_allowed_packet" default
Date: Wed, 05 Jan 2022 00:00:11 +0100

Hi,

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:
>>>>
>>>>>> Could it be worth setting max_allowed_packet to 16M in Guix's
>>>>>> `mysql-configuration-file` function for consistency with Debian?
>>>>>
>>>>> Definitely.  I would add a ‘max-allowed-packet’ field in
>>>>> <mysql-configuration> in (gnu services databases) and make sure it’s
>>>>> honored.
>>>>>
>>>>> Would you like to give it a try?
>>>>
>>>> Sure, I'll give it a shot!
>>>>
>>>> It looks as though the MariaDB source comes with a settings file for
>>>> Debian that includes max-allowed-packet=16M:
>>>>
>>>>   mariadb-XX.XX.XX/debian/additions/my.cnf
>>>>
>>>> Would you recommend adding just max-allowed-packet, or would it be worth
>>>> applying all these settings in this file?
>
> The bug#25415 [1] is about MySQL and a patch seems required.
>
> Would you like give a try?
>
> 1: <http://issues.guix.gnu.org/issue/25415>

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. :-)

Cheers,
simon

Message #31 received at 25415-done <at> debbugs.gnu.org (full text, mbox):

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.