MIME-Version: 1.0
References: <Zl7NeNz4XsoEjCY0@falared> <CABVffEMPBDRyLmQR5y2=uXNUOcf70vkhc6=9NiiNRo54BQVvfg@mail.gmail.com>
In-Reply-To: <CABVffEMPBDRyLmQR5y2=uXNUOcf70vkhc6=9NiiNRo54BQVvfg@mail.gmail.com>
From: Hans Harder <hans@atbas.org>
Date: Tue, 4 Jun 2024 14:32:53 +0200
Message-ID: <CAKzsc6eCGKqFNRCv_=UY6gH_srdJPSHGb0qPxTyptdyYn53oRA@mail.gmail.com>
Subject: Re: Re: Get "segmentation fault" with mariabackup on Alpine 3.20
 amd64 version
To: Daniel Black <daniel@mariadb.org>
Cc: faustin@mariadb.org, ~alpine/devel@lists.alpinelinux.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

  >  Otherwise --cap-add SYS_PTRACE to the container start.
Can not add that to the lxc container start... so far I know

  > install gdb and debuginfo sym package for mariadb-backup
Added only gdb   with apk add gdb

Cannot find a debuginfo sym package for mariadb-backup

Created a jira story with a showrt summary and the gdb output :
https://jira.mariadb.org/browse/MDEV-34299

thx for quick response...




On Tue, Jun 4, 2024 at 10:27=E2=80=AFAM Daniel Black <daniel@mariadb.org> w=
rote:
>
> There was https://jira.mariadb.org/browse/MDEV-31251 that has been
> resolved in the last releases.
>
> Otherwise --cap-add SYS_PTRACE to the container start.
>
> install gdb and debuginfo sym package for mariadb-backup
>
> run:
>
> gdb -ex r --args mariabackup --backup -u root -p --targetdir=3D/root/back=
up/
>
> and `bt full` when it crashes.
>
> new bug report welcome.
>
> On Tue, 4 Jun 2024 at 18:16, Faustin Lammler <faustin@mariadb.org> wrote:
> >
> > FYI
> > I am off (with my laptop) this week, so ping me if any urgency.
> >
> > Cheers!
> >
> > ----- Forwarded message from Faustin Lammler <faustin@fala.red> -----
> >
> > Date: Tue, 4 Jun 2024 10:15:56 +0200
> > From: Faustin Lammler <faustin@fala.red>
> > To: Hans Harder <hans@atbas.org>
> > Cc: "~alpine/devel@lists.alpinelinux.org" <~alpine/devel@lists.alpineli=
nux.org>
> > Subject: Re: Get "segmentation fault" with mariabackup on Alpine 3.20 a=
md64 version
> > User-Agent: Mutt/2.2.13 (2024-03-09)
> >
> > Hi Hans!
> > I can confirm this (tested in podman containers with):
> > | podman run --name init-test --rm -d fauust/docker-systemd:alpine-3.20
> > | podman exec -it init-test sh
> > | mkdir /root/backup
> > | apk add mariadb mariadb-backup mariadb-client mariadb-openrc
> > | /etc/init.d/mariadb setup
> > | /etc/init.d/mariadb start
> > | mariabackup --backup -u root -p --targetdir=3D/root/backup/
> >
> > I could not find anything upstream
> > (https://jira.mariadb.org/browse/MDEV-20189?jql=3Dtext%20~%20%22mariaba=
ckup%20segfault%22)
> > but my first guess would be that this does not comes from Alpine
> > packaging. So, you might consider opening a jira issue there?
> >
> > Cheers!
> >
> > Hans Harder <hans@atbas.org>,
> > 04/06/2024 =E2=80=93 09:24:45 (+0200):
> >
> > > Did a fresh alpine container install on 3.20 with amd64
> > > after the initial setup-alpine I did:
> > >
> > > mkdir /root/backup
> > > apk add mariadb mariadb-backup mariadb-client mariadb-openrc
> > > /etc/init.d/mariadb setup
> > > /etc/init.d/mariadb start
> > > mariabackup --backup -u root -p --targetdir=3D/root/backup/
> > >
> > > Result:
> > > [00] 2024-06-04 08:58:55 Connecting to MariaDB server host: localhost=
,
> > > user: root, password: set, port: not set, socket: not set
> > > [00] 2024-06-04 08:58:55 Using server version 10.11.8-MariaDB
> > > mariabackup based on MariaDB server 10.11.8-MariaDB Linux (x86_64)
> > > [00] 2024-06-04 08:58:55 uses posix_fadvise().
> > > [00] 2024-06-04 08:58:55 cd to /var/lib/mysql/
> > > [00] 2024-06-04 08:58:55 open files limit requested 0, set to 1024
> > > [00] 2024-06-04 08:58:55 mariabackup: using the following InnoDB conf=
iguration:
> > > ..
> > > [00] 2024-06-04 08:58:55 Stop scanning aria tables.
> > > [00] 2024-06-04 08:58:55 Copying ./mysql/transaction_registry.ibd to
> > > /root/xtrabackup_backupfiles/mysql/transaction_registry.ibd
> > > Segmentation fault
> > >
> > > with strace mariabackup --backup -u root -p --targetdir=3D/root/backu=
p/
> > > writev(2, [{iov_base=3D"[00] 2024-06-04 09:20:42 Acquiri"...,
> > > iov_len=3D51}, {iov_base=3DNULL, iov_len=3D0}], 2[00] 2024-06-04 09:2=
0:42
> > > Acquiring BACKUP LOCKS...
> > > ) =3D 51
> > > poll([{fd=3D6, events=3DPOLLIN|POLLPRI}], 1, 0) =3D 0 (Timeout)
> > > sendto(6, "\36\0\0\0\3SET SESSION wsrep_sync_wait"..., 34, 0, NULL, 0=
) =3D 34
> > > recvfrom(6, "\7\0\0\1\0\0\0\2\0\0\0", 16384, 0, NULL, NULL) =3D 11
> > > poll([{fd=3D6, events=3DPOLLIN|POLLPRI}], 1, 0) =3D 0 (Timeout)
> > > sendto(6, "\23\0\0\0\3BACKUP STAGE START", 23, 0, NULL, 0) =3D 23
> > > recvfrom(6, "\7\0\0\1\0\0\0\2\0\0\0", 16384, 0, NULL, NULL) =3D 11
> > > futex(0x7f1cbac41904, FUTEX_WAKE_PRIVATE, 1) =3D 1
> > > nanosleep({tv_sec=3D0, tv_nsec=3D1000000}, [00] 2024-06-04 09:20:42
> > > Copying ./mysql/transaction_registry.ibd to
> > > /root/xtrabackup_backupfiles/mysql/transaction_registry.ibd
> > > 0x7ffd2c488300) =3D 0
> > > nanosleep({tv_sec=3D0, tv_nsec=3D1000000}, 0x7ffd2c488300) =3D 0
> > > nanosleep({tv_sec=3D0, tv_nsec=3D1000000}, 0x7ffd2c488300) =3D 0
> > > nanosleep({tv_sec=3D0, tv_nsec=3D1000000}, 0x7ffd2c488300) =3D 0
> > > nanosleep({tv_sec=3D0, tv_nsec=3D1000000},  <unfinished ...>) =3D ?
> > > +++ killed by SIGSEGV +++
> > > Segmentation fault
> > >
> > > Did this in a lxc container on WSL and on RH8.9  both got the Segment=
ation fault
> > >
> > > Did this also on 3.19 amd64  backup went ok
> > > Did this also on 3.20 arm64   backup went ok
> >
> > --
> > Faustin
> > GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79
> >
> >
> >
> > ----- End forwarded message -----
> >
> > --
> > Faustin Lammler
> > MariaDB Foundation
> > GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79