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 1tmvbi-000Hw9-B2 for pgsql-general@arkaria.postgresql.org; Tue, 25 Feb 2025 14:08: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 1tmvbh-002W80-92 for pgsql-general@arkaria.postgresql.org; Tue, 25 Feb 2025 14:08:21 +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 1tmvbg-002W7p-Ub for pgsql-general@lists.postgresql.org; Tue, 25 Feb 2025 14:08:20 +0000 Received: from mail-io1-xd2f.google.com ([2607:f8b0:4864:20::d2f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tmvbd-0000h2-2P for pgsql-general@lists.postgresql.org; Tue, 25 Feb 2025 14:08:20 +0000 Received: by mail-io1-xd2f.google.com with SMTP id ca18e2360f4ac-855923e7f53so401344039f.2 for ; Tue, 25 Feb 2025 06:08:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1740492498; x=1741097298; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=74JRHt4oN0bDD7xq9PoiMTiSbzeSYUgFlwrwMYFs56c=; b=OU2EHvvKX6jrLq5xma3JtdqneDjyisG8WfOUw++Cmw8y5GtgDu9jNEQXj/caDGGRsi uO85yK8mBwL2THP1a+xIaY6N19ss/AAFIoibDBzUq+VmvSKrWI/06O7iRPoZ6S17i3X7 MvNvr9qq6q8cCSRoVO2a7VLZnc37aYp6ylzHxG4aEmT6uvQIheqLf3HMCmlho6c0SwjH l67SvUIAHRkvzM2dPptDmaFSD+bNHO9BT5rDqgtaSyVgf9LxwtY+pD6ynul34wMTAPqS u0U/pKbi9PHCi7adcEvPatXWsazVCGkveIlrra2aQq/jYLl0BEgrDlvHMT42vQ90TTG3 mUew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1740492498; x=1741097298; h=cc: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=74JRHt4oN0bDD7xq9PoiMTiSbzeSYUgFlwrwMYFs56c=; b=S2fqmyE5iEho14gXut577VFO/eeU7msJErEJ/B01mDVYQ65YrmWQW67ML/fiOYP4eX QyyJykF6tDw01lZOeg4u5MUG3aWSmXhShdFHXQcTjMZHI3uQRzTY5l7NcvjKV9seBkde wPbQBI05e0cSSHPwHINFWzT8peSZvJ0Vo6OrB0zfF5YNl7/fjHAmcPnowZrp68rpzjEt Vp4DNJuCJCb23XLbkTdMsZD2A0JWc7z6VFDoC7rNISRN9cYFIOtowpKmyciCbK/FAkIL iBykcP64VSeP15BrNcIFSSWlyKNVlXgglwIew56iTeXjFR2DsEBuawXC4aBFE3JiTxA3 pBFw== X-Gm-Message-State: AOJu0YyL3XE/BCdPjD7OmLFG8gNuXY9b1YtPbsIEXV2iEuDCUZ4x7X9e e6PA2S5D6KouGFiy3HDbhQD9kMsxFDP4jqADRnr0FlvTLShLDmZqBac1Nepvv3fwWnrAdgZsM5X 0Fe/aD0xPgvgWiqaivk4fEBpylpyfNBzNICo= X-Gm-Gg: ASbGncv7Rb7xjcdDaEkuEMwA+sPuCNDu0BlHR4j1TGnMvIA63P+fdIubL0E/bNmXUPl gMzRRFWRuF8D8TkKAtWuPk6dmsv8KZXf8oNErFLTJTwoHz2Axru/aPF8IovhUQeQlQCYabkDzDj 6vZMlDSi+ysmvHm7+eB+bBOA58onJgtObjXBO3FxQb8A== X-Google-Smtp-Source: AGHT+IGLuWlhNn1uqw8gEERoZXg0NG0FXTCHIZN0M8pwNXM1Mgbl3hm8nBOLPPNw32NqxrCSjZrjPsUm7+rNaMgltNo= X-Received: by 2002:a05:6e02:1b06:b0:3d0:443d:a5a4 with SMTP id e9e14a558f8ab-3d2fc0c5499mr33111035ab.2.1740492497961; Tue, 25 Feb 2025 06:08:17 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Greg Sabino Mullane Date: Tue, 25 Feb 2025 09:07:40 -0500 X-Gm-Features: AQ5f1Jo552JY-TOW7clrEyGNdv1wBKZIAe1EWcNu6VqghNZgYRlCpBWAC48u68c Message-ID: Subject: Re: Postgres 16 unexpected shutdown To: postgres@arcict.com Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000134e02062ef7fdf0" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000134e02062ef7fdf0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Feb 25, 2025 at 8:51=E2=80=AFAM wrote: > Does this sound familiar anyone? Any ideas what might prompt Postgres to > stop? > Postgres needs full read and write access to its own data directory. If it doesn't, it will eventually PANIC, as your logs show. See if you can figure out what else happened around 2025-02-22 08:05:49.427 CET, which seems to be when the problem started according to your logs. Cheers, Greg -- Crunchy Data - https://www.crunchydata.com Enterprise Postgres Software Products & Tech Support --000000000000134e02062ef7fdf0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Feb 25, 2025 at 8:51=E2=80=AFAM &= lt;postgres@arcict.com> wrote= :
Does this sound familiar anyone? Any ideas= what might prompt Postgres to stop?

Po= stgres needs full read and write access to its own data directory. If it do= esn't, it will eventually PANIC, as your logs show.

See if you can figure out what else happened around 2025-02-22 08:05:= 49.427 CET, which seems to be when the problem started according to your lo= gs.

Cheers,
Greg

--
Enterprise Postgres Software = Products & Tech Support

--000000000000134e02062ef7fdf0--