BUG #18361: systemd[1]: postgresql-16.service: Killing process 25992 (postgres) with signal SIGKILL.

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: makhomed(at)gmail(dot)com
Subject: BUG #18361: systemd[1]: postgresql-16.service: Killing process 25992 (postgres) with signal SIGKILL.
Date: 2024-02-24 12:51:42
Message-ID: 18361-1a3f843f5f6ce694@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-pkg-yum

The following bug has been logged on the website:

Bug reference: 18361
Logged by: Gena Makhomed
Email address: makhomed(at)gmail(dot)com
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
○ 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=/usr/pgsql-16/bin/postgresql-16-check-db-dir
${PGDATA} (code=exited, status=0/SUCCESS)
Process: 26671 ExecStart=/usr/pgsql-16/bin/postgres -D ${PGDATA}
(code=exited, status=0/SUCCESS)
Main PID: 26671 (code=exited, status=0/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.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2024-02-24 21:33:05 BUG #18362: unaccent rules and Old Greek text
Previous Message Tom Lane 2024-02-23 19:33:49 Re: BUG #18360: Invalid memory access occurs when using geqo

Browse pgsql-pkg-yum by date

  From Date Subject
Next Message Gena Makhomed 2024-02-25 08:50:15 systemd[1]: postgresql-16.service: Killing process 25992 (postgres) with signal SIGKILL.
Previous Message Devrim Gündüz 2024-01-29 00:39:56 Re: RHEL8: barman broken by new psycopg2 package?