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

Previous Next

Package: guix;

Reported by: Ben Sturmfels <ben <at> stumbles.id.au>

Date: Wed, 11 Jan 2017 00:31:01 UTC

Severity: normal

Done: zimoun <zimon.toutoune <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


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




This bug report was last modified 2 years and 334 days ago.

Previous Next


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