Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rV7PF-00ExMI-Ee for pgsql-bugs@arkaria.postgresql.org; Wed, 31 Jan 2024 10:01:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rV7PE-00D9OD-MU for pgsql-bugs@arkaria.postgresql.org; Wed, 31 Jan 2024 10:01:20 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rUudE-009SQg-NS for pgsql-bugs@lists.postgresql.org; Tue, 30 Jan 2024 20:22:56 +0000 Received: from mail-wm1-x336.google.com ([2a00:1450:4864:20::336]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rUud8-004Ctq-39 for pgsql-bugs@lists.postgresql.org; Tue, 30 Jan 2024 20:22:55 +0000 Received: by mail-wm1-x336.google.com with SMTP id 5b1f17b1804b1-40e7e2e04f0so48701095e9.1 for ; Tue, 30 Jan 2024 12:22:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1706646169; x=1707250969; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=9R1yRjrCVgOBqcC4EYmv93TncYXh4DCFff5nv5VeHWI=; b=HqhDhFfrElxzFqqzZA2CKRRVR6ApF5BhWDjmv06fcQzEjZ5t5ZwpCsIpc8/91Rm6BG tMBG0YaH2/y7okpR/Ob6QOFjHrjxtHdLX5pXf4peFORWU4pS2oYckO3mJCDTAKLVytwW 1JD0eSSqH+5e+1HNhdDPKBzJc4mycCdUe7l88V3eZ7oMz1hRXyubGhuDRbTS80zW1oLV nwTfR+yCnLFnnUH8ra2Yu/5/lH26jByt24UPo6UKbbKbXxxWk45W4vMoEq7GmYxB0eHy X+PHuA9OFW7bQ6+0wyDA2P1t8ehZIX2e4SggjRVtpbYlbQ5Pp1GpC+zNGiiLuSwTG1p5 5U9Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706646169; x=1707250969; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=9R1yRjrCVgOBqcC4EYmv93TncYXh4DCFff5nv5VeHWI=; b=lkAe1OHV0NsA4GP6fWO+GbKwJfegFm6CKEMhFmJaUkeWWYMzwfGJYqN4rot1ed8xQk gRn/5QY4ynh4Z4J6FTyjJd9zcNvu2C4lf2pnRDY3UWVieKyX2zbGNoVH4ttg6yMQk9o4 j5JyK2TKWiFgOTNVuIldDQZAP7Q7Tcv4Elcj1fbjG5yasN8BE6U6t8Szt1xqzY42FVP2 ysbas1zi5axKuvLZTDuSwPs3OWz3qEJh3bbeUXgyudfHrO+VwCX8iGor5fHNYJgq7jfB 9xsZmXZDA95+xzfd0QYEgrYpm+N1MLghK6dsKwdr0uKJ39P7IcW+xgGaNk7iPqf1tBxe Sqmg== X-Gm-Message-State: AOJu0Yzz4ATZbChW5/afV5SuGP3Nb5vB4ZQsVhVcCaOMz4f7CFbXgFLS 9VSqorA29+aTULXe1Uc9ojMTteywJvygR+Hnhjn+iERo5nKteMqUJm53JERUWGNlIUhoEpC76vm EF0Nj+FiV1IbAtWx/hhsURKbEUuw= X-Google-Smtp-Source: AGHT+IHXVHnuSan9VaB6Sr/2PiKTyQ8vDHMqJmPtwSg9sZaUiiCoCDM8vxEctWqcRG9LnctGgHXf2fXxsMBX4AxfaAA= X-Received: by 2002:a5d:444a:0:b0:33a:e5a9:c22d with SMTP id x10-20020a5d444a000000b0033ae5a9c22dmr6862157wrr.25.1706646168501; Tue, 30 Jan 2024 12:22:48 -0800 (PST) MIME-Version: 1.0 References: <18315-99f2ada874e7c8ef@postgresql.org> In-Reply-To: <18315-99f2ada874e7c8ef@postgresql.org> From: =?UTF-8?Q?Ivan_Kalafati=C4=87?= Date: Tue, 30 Jan 2024 21:22:12 +0100 Message-ID: Subject: Re: BUG #18315: Segmentation fault on connection (repmgr, psql) To: ikalafat@gmail.com, pgsql-bugs@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000a1819206102f86d9" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000a1819206102f86d9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Additional info: in the meantime, I've tried adding require_auth=3Dnone and gssencmode=3Ddisable connection string parameters (separately, not together at once) for the repmgr/client connections that are "trusted" through pg_hba.conf, but the problem persisted. On Tue, 30 Jan 2024 at 16:17, PG Bug reporting form wrote: > The following bug has been logged on the website: > > Bug reference: 18315 > Logged by: Ivan Kalafati=C4=87 > Email address: ikalafat@gmail.com > PostgreSQL version: 16.1 > Operating system: Debian 12 > Description: > > Hi, > > I am intermittently getting following errors (taken from var/log/syslog), > on > pg_basebackup, repmgrd and psql (so far) > > > repmgr[1147164] general protection fault ip:7fb9950981b5 sp:7ffecf4418f8 > error:0 in libkrb5.so.3.3[7fb99506a000+5f000] > also this: > > pg_basebackup[4191295] general protection fault ip:7f344e9771b5 > sp:7ffe8c625c28 error:0 in libkrb5.so.3.3[7f344e949000+5f000] > > and this > > psql[4045720] general protection fault ip:7f89130931b5 sp:7fffd40a0268 > error:0 in libkrb5.so.3.3[7f8913065000+5f000] > > Looks like that the error is related to GSSAPI/kerberos auth? I have trie= d > replacing "host" type within pg_hba.conf to "hostnogssenc", but problem > persists. > > Running Debian 12 with all updates, repmgr, timescaledb extensions (fresh > install). PostgreSQL 16.1 (Debian 16.1-1.pgdg120+1) > Looks like the server itself is not affected (isn't crashing etc). > > Is there anything that I could do to disable GSSAPI/kerberos and/or > circumvent this issue? Also, how can I provide more info for this issue t= o > be resolved. > > Thanks. > > --000000000000a1819206102f86d9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Additional info: in the meantime, I've tried adding=C2= =A0require_auth=3Dnone and=C2=A0gssencmode=3Ddisable connection string para= meters (separately, not together at once) for the repmgr/client connections= that are "trusted" through pg_hba.conf, but the problem persiste= d.

On Tue, 30 Jan 2024 at 16:17, PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has be= en logged on the website:

Bug reference:=C2=A0 =C2=A0 =C2=A0 18315
Logged by:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Ivan Kalafati=C4=87
Email address:=C2=A0 =C2=A0 =C2=A0 ikalafat@gmail.com
PostgreSQL version: 16.1
Operating system:=C2=A0 =C2=A0Debian 12
Description:=C2=A0 =C2=A0 =C2=A0 =C2=A0

Hi,

I am intermittently getting following errors (taken from var/log/syslog), o= n
pg_basebackup, repmgrd and psql (so far)


repmgr[1147164] general protection fault ip:7fb9950981b5 sp:7ffecf4418f8 error:0 in libkrb5.so.3.3[7fb99506a000+5f000]
also this:

pg_basebackup[4191295] general protection fault ip:7f344e9771b5
sp:7ffe8c625c28 error:0 in libkrb5.so.3.3[7f344e949000+5f000]

and this

psql[4045720] general protection fault ip:7f89130931b5 sp:7fffd40a0268
error:0 in libkrb5.so.3.3[7f8913065000+5f000]

Looks like that the error is related to GSSAPI/kerberos auth? I have tried<= br> replacing "host" type within pg_hba.conf to "hostnogssenc&qu= ot;, but problem
persists.

Running Debian 12 with all updates, repmgr, timescaledb extensions (fresh install). PostgreSQL 16.1 (Debian 16.1-1.pgdg120+1)
Looks like the server itself is not affected (isn't crashing etc).

Is there anything that I could do to disable GSSAPI/kerberos and/or
circumvent this issue? Also, how can I provide more info for this issue to<= br> be resolved.=C2=A0

Thanks.

--000000000000a1819206102f86d9--