From: zimoun <zimon.toutoune@gmail.com>
To: Ben Sturmfels <ben@stumbles.id.au>
Cc: 25415@debbugs.gnu.org
Subject: 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 [thread overview]
Message-ID: <86czmnr8ej.fsf@gmail.com> (raw)
In-Reply-To: <86sfx5kjhp.fsf@gmail.com> (zimoun's message of "Tue, 12 Oct 2021 23:42:42 +0200")
Hi Ben,
I hope you are well.
On Tue, 12 Oct 2021 at 23:42, zimoun <zimon.toutoune@gmail.com> wrote:
> On Tue, 14 Sep 2021 at 13:51, zimoun <zimon.toutoune@gmail.com> wrote:
>> On Fri, 13 Jan 2017 at 10:29, Ben Sturmfels <ben@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
next prev parent reply other threads:[~2021-11-26 1:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 0:10 bug#25415: MySQL "server has gone away" when reloading database dump due to "max_allowed_packet" default Ben Sturmfels
2017-01-12 14:22 ` Ludovic Courtès
2017-01-12 23:29 ` Ben Sturmfels
2017-01-13 8:03 ` Ludovic Courtès
2021-09-14 11:51 ` zimoun
2021-10-12 21:42 ` zimoun
2021-11-26 1:51 ` zimoun [this message]
2022-01-04 23:00 ` zimoun
2022-06-23 9:54 ` zimoun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86czmnr8ej.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=25415@debbugs.gnu.org \
--cc=ben@stumbles.id.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.