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 1reADS-009mpG-KP for pgsql-pkg-yum@arkaria.postgresql.org; Sun, 25 Feb 2024 08:50:35 +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 1reADR-006raX-3N for pgsql-pkg-yum@arkaria.postgresql.org; Sun, 25 Feb 2024 08:50:33 +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 1reADQ-006rZQ-Kq for pgsql-pkg-yum@lists.postgresql.org; Sun, 25 Feb 2024 08:50:33 +0000 Received: from mail-ej1-x631.google.com ([2a00:1450:4864:20::631]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1reADM-000tU1-4h for pgsql-pkg-yum@lists.postgresql.org; Sun, 25 Feb 2024 08:50:31 +0000 Received: by mail-ej1-x631.google.com with SMTP id a640c23a62f3a-a26fa294e56so368196366b.0 for ; Sun, 25 Feb 2024 00:50:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1708851027; x=1709455827; 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=zk9M8yFI52MIApZNgJ1HTbaGY/JP/Ql/1aH9ETRcKhY=; b=PaoEUi+NJcZu80Nx8E97/x77VCYzzog63IjdNoBWZkkxOsdvAUSnuzqUTk1Cvu5vyF OUgIsEuqD2w2k0uGdvouepMa3B1SMD1ZOD28Lmbju587Da3ZuPoUIVm/VgyL4YL0jwPm tj60C24vgbv/Y9dzS0+OFN9fCded68W3THpDDAaMAFnP8WanB4EhMbJSnaepakbeWOD7 eG3LhJYvftPNREyNhayEV4YVq1sVd+qTZBnWIMvBLsOh3ihqMlBmXjsJXKmVK5W4vg9/ C5yjxz4NWx1zxoUZEpQvLdRAyeCGK5CH5lphAYLAlhs99sOLrK+oyz0neBj4G2ohQq0U P5cw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708851027; x=1709455827; 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=zk9M8yFI52MIApZNgJ1HTbaGY/JP/Ql/1aH9ETRcKhY=; b=LN+/Zk9EfGgxBf4DME/fLsKRvSYiP9kl6F1SgOiz0X60t62z69hEGKbcgR1BQZmP5M 53Z7vqWtxpU1ji3xfGrZK6uejKcJhqvWbxHhvGRAG5KYdHMEGcZ3pjxcpugzeNP6gA/F fEIfBc34IIcfMJkW87wcds/8c5JEu63pYTSO9JUlT50zJ2k7cJYcQ2FZfyg6qtVx07Qt eVeW6RcK/WsMQwc6+erIkW2glT0UfdNtlAVERVAqPZoWQWvVJLbiRz1ZIYH6L8G8/tk2 h07iME+GeaJqXFulAs+8G6uWgo0P8HCoAKc8aC6Yt9+Aj8yH02AkJ/+EpvCg+FnihG/x Up9w== X-Gm-Message-State: AOJu0YzC9rFwuN9CEvgyMKEZrQqRrj5WDezsRRHOp5udz6ZcqUZ6jMFQ +bK3CcSbAOBi84o6Xnl9dfC1uuM2I6eSTaoPraTfIAXzmU8X81tbtj+adcmKPpro4r/0c9JSlqs GiZEG7lSp7MjvolKXT1xP++dkGnhVUM4No6b/mQ== X-Google-Smtp-Source: AGHT+IHjKffqqFG9HqNKQnBtcalxV60xne11ZH88EFQdDor/DlsD5JIchyvQD4WeKGT6UTSPA2uOykGc+wFtVI6XT98= X-Received: by 2002:a17:906:81c2:b0:a43:bbf:1387 with SMTP id e2-20020a17090681c200b00a430bbf1387mr1407367ejx.4.1708851027037; Sun, 25 Feb 2024 00:50:27 -0800 (PST) MIME-Version: 1.0 References: <18361-1a3f843f5f6ce694@postgresql.org> In-Reply-To: <18361-1a3f843f5f6ce694@postgresql.org> From: Gena Makhomed Date: Sun, 25 Feb 2024 10:50:15 +0200 Message-ID: Subject: systemd[1]: postgresql-16.service: Killing process 25992 (postgres) with signal SIGKILL. To: pgsql-pkg-yum@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000070d2e6061230e298" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000070d2e6061230e298 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Previously posted to pgsql-bugs mail list as BUG #18361, but as I understand later, this may not be the PostgreSQL bug itself, but it may be the rpm/yum/dnf packaging bug? Can you please help to fix this bug, or find a workaround? Because killing postgres via SIGKILL is not a good idea. ---------- Forwarded message --------- =D0=9E=D1=82: PG Bug reporting form Date: =D1=81=D0=B1, 24 =D1=84=D0=B5=D0=B2=D1=80. 2024=E2=80=AF=D0=B3. =D0= =B2 14:52 Subject: BUG #18361: systemd[1]: postgresql-16.service: Killing process 25992 (postgres) with signal SIGKILL. To: The following bug has been logged on the website: Bug reference: 18361 PostgreSQL version: 16.2 Operating system: Rocky Linux release 9.3 Description: PostgreSQL 16.2 installed on the Rocky Linux release 9.3 server from official repository with official instruction from page https://www.postgresql.org/download/linux/redhat/ when I execute command # systemctl stop postgresql-16.service ; systemctl status postgresql-16.service I see, what PostgreSQL 16.2 was killed by SIGKILL. this is a bug, as I understand, because database will be corrupted. Is it possible to fix this bug and stop killing PostgreSQL with signal SIGKILL ? # systemctl stop postgresql-16.service ; systemctl status postgresql-16.service =E2=97=8B postgresql-16.service - PostgreSQL 16 database server Loaded: loaded (/usr/lib/systemd/system/postgresql-16.service; enabled= ; preset: disabled) Active: inactive (dead) since Sat 2024-02-24 12:47:19 UTC; 6ms ago Duration: 3.525s Docs: https://www.postgresql.org/docs/16/static/ Process: 26666 ExecStartPre=3D/usr/pgsql-16/bin/postgresql-16-check-db-= dir ${PGDATA} (code=3Dexited, status=3D0/SUCCESS) Process: 26671 ExecStart=3D/usr/pgsql-16/bin/postgres -D ${PGDATA} (code=3Dexited, status=3D0/SUCCESS) Main PID: 26671 (code=3Dexited, status=3D0/SUCCESS) CPU: 43ms Feb 24 12:47:15 postgres-16.example.net systemd[1]: Starting PostgreSQL 16 database server... Feb 24 12:47:15 postgres-16.example.net postgres[26671]: 2024-02-24 12:47:15.985 UTC [26671] LOG: redirecting log output to logging collector process Feb 24 12:47:15 postgres-16.example.net postgres[26671]: 2024-02-24 12:47:15.985 UTC [26671] HINT: Future log output will appear in directory "log". Feb 24 12:47:15 postgres-16.example.net systemd[1]: Started PostgreSQL 16 database server. Feb 24 12:47:19 postgres-16.example.net systemd[1]: Stopping PostgreSQL 16 database server... Feb 24 12:47:19 postgres-16.example.net systemd[1]: postgresql-16.service: Killing process 26672 (postgres) with signal SIGKILL. Feb 24 12:47:19 postgres-16.example.net systemd[1]: postgresql-16.service: Deactivated successfully. Feb 24 12:47:19 postgres-16.example.net systemd[1]: Stopped PostgreSQL 16 database server. --=20 *Please consider the environment before printing* --00000000000070d2e6061230e298 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Pre= viously posted to=20 pgsql-bugs mail list as BUG #18361, = but as I understand later, this may not be the PostgreSQL bug itself, but i= t may be the rpm/yum/dnf packaging bug?

Can you please help to fix this bug, or find a workaround?

Because killing postgres v= ia=20 SIGKILL is n= ot a good idea.


---------- Forwarde= d message ---------
=D0=9E=D1=82: PG Bug reporting form <noreply@postgresql.org>
Date: =D1=81= =D0=B1, 24 =D1=84=D0=B5=D0=B2=D1=80. 2024=E2=80=AF=D0=B3. =D0=B2 14:52
S= ubject: BUG = #18361: systemd[1]: postgresql-16.service: Killing process 25992 (postgres)= with signal SIGKILL.
To: <pgsql-bugs@lis= ts.postgresql.org>


The following bug has been logge= d on the website:

Bug reference:=C2=A0 =C2=A0 =C2=A0 18361
PostgreSQL version: 16.2
Operating system:=C2=A0 =C2=A0Rocky Linux release 9.3
Description:=C2=A0 =C2=A0 =C2=A0 =C2=A0

PostgreSQL 16.2 installed on the Rocky Linux release 9.3 server from
official repository with official instruction from page
https://www.postgresql.org/download/linux/redhat/

when I execute command

# systemctl stop postgresql-16.service ; systemctl status
postgresql-16.service

I see, what PostgreSQL 16.2 was killed by SIGKILL.

this is a bug, as I understand, because database will be corrupted.

Is it possible to fix this bug and stop killing PostgreSQL with signal
SIGKILL ?

# systemctl stop postgresql-16.service ; systemctl status
postgresql-16.service
=E2=97=8B postgresql-16.service - PostgreSQL 16 database server
=C2=A0 =C2=A0 =C2=A0Loaded: loaded (/usr/lib/systemd/system/postgresql-16.s= ervice; enabled;
preset: disabled)
=C2=A0 =C2=A0 =C2=A0Active: inactive (dead) since Sat 2024-02-24 12:47:19 U= TC; 6ms ago
=C2=A0 =C2=A0Duration: 3.525s
=C2=A0 =C2=A0 =C2=A0 =C2=A0Docs: https://www.postgresql.or= g/docs/16/static/
=C2=A0 =C2=A0 Process: 26666 ExecStartPre=3D/usr/pgsql-16/bin/postgresql-16= -check-db-dir
${PGDATA} (code=3Dexited, status=3D0/SUCCESS)
=C2=A0 =C2=A0 Process: 26671 ExecStart=3D/usr/pgsql-16/bin/postgres -D ${PG= DATA}
(code=3Dexited, status=3D0/SUCCESS)
=C2=A0 =C2=A0Main PID: 26671 (code=3Dexited, status=3D0/SUCCESS)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 CPU: 43ms

Feb 24 12:47:15 postgres-16.example.net systemd[1]: Starting Postg= reSQL 16
database server...
Feb 24 12:47:15 postgres-16.example.net postgres[26671]: 2024-02-2= 4
12:47:15.985 UTC [26671] LOG:=C2=A0 redirecting log output to logging colle= ctor
process
Feb 24 12:47:15 postgres-16.example.net postgres[26671]: 2024-02-2= 4
12:47:15.985 UTC [26671] HINT:=C2=A0 Future log output will appear in direc= tory
"log".
Feb 24 12:47:15 postgres-16.example.net systemd[1]: Started Postgr= eSQL 16
database server.
Feb 24 12:47:19 postgres-16.example.net systemd[1]: Stopping Postg= reSQL 16
database server...
Feb 24 12:47:19 postgres-16.example.net systemd[1]: postgresql-16.= service:
Killing process 26672 (postgres) with signal SIGKILL.
Feb 24 12:47:19 postgres-16.example.net systemd[1]: postgresql-16.= service:
Deactivated successfully.
Feb 24 12:47:19 postgres-16.example.net systemd[1]: Stopped Postgr= eSQL 16
database server.


--
Please consider= the environment before printing
--00000000000070d2e6061230e298--