sclorg / postgresql-container

PostgreSQL container images based on Red Hat Software Collections and intended for OpenShift and general usage. Users can choose between Red Hat Enterprise Linux, Fedora, and CentOS based images.
http://softwarecollections.org
Apache License 2.0
163 stars 212 forks source link

postgres constantly restarted inside container #541

Open nhirshler opened 8 months ago

nhirshler commented 8 months ago

Container platform

No response

Version

15:1-20

OS version of the container image

RHEL 8

Bugzilla, Jira

No response

Description

Postgres seems to be restarting constantly inside the container. I see the following output in postgres log file. I'm not sure what causes this constant restart. If I connect to the database I can run select and insert without any issues however, these interruptions are creation a problem in node application that is trying to work with the database. Any idea how to find the source of the problem?

2023-12-18 11:25:48.847 UTC [743] DEBUG: shmem_exit(0): 4 before_shmem_exit callbacks to make 2023-12-18 11:25:48.847 UTC [745] DEBUG: shmem_exit(0): 4 before_shmem_exit callbacks to make 2023-12-18 11:25:48.847 UTC [743] DEBUG: shmem_exit(0): 6 on_shmem_exit callbacks to make 2023-12-18 11:25:48.847 UTC [744] DEBUG: shmem_exit(0): 4 before_shmem_exit callbacks to make 2023-12-18 11:25:48.847 UTC [743] DEBUG: proc_exit(0): 2 callbacks to make 2023-12-18 11:25:48.847 UTC [743] DEBUG: exit(0) 2023-12-18 11:25:48.847 UTC [743] DEBUG: shmem_exit(-1): 0 before_shmem_exit callbacks to make 2023-12-18 11:25:48.847 UTC [743] DEBUG: shmem_exit(-1): 0 on_shmem_exit callbacks to make 2023-12-18 11:25:48.847 UTC [743] DEBUG: proc_exit(-1): 0 callbacks to make 2023-12-18 11:25:48.847 UTC [745] DEBUG: shmem_exit(0): 6 on_shmem_exit callbacks to make 2023-12-18 11:25:48.847 UTC [744] DEBUG: shmem_exit(0): 6 on_shmem_exit callbacks to make 2023-12-18 11:25:48.847 UTC [745] DEBUG: proc_exit(0): 2 callbacks to make 2023-12-18 11:25:48.847 UTC [745] DEBUG: exit(0) 2023-12-18 11:25:48.847 UTC [744] DEBUG: proc_exit(0): 2 callbacks to make 2023-12-18 11:25:48.847 UTC [744] DEBUG: exit(0) 2023-12-18 11:25:48.847 UTC [745] DEBUG: shmem_exit(-1): 0 before_shmem_exit callbacks to make 2023-12-18 11:25:48.847 UTC [744] DEBUG: shmem_exit(-1): 0 before_shmem_exit callbacks to make 2023-12-18 11:25:48.847 UTC [745] DEBUG: shmem_exit(-1): 0 on_shmem_exit callbacks to make 2023-12-18 11:25:48.847 UTC [744] DEBUG: shmem_exit(-1): 0 on_shmem_exit callbacks to make 2023-12-18 11:25:48.847 UTC [744] DEBUG: proc_exit(-1): 0 callbacks to make 2023-12-18 11:25:48.847 UTC [745] DEBUG: proc_exit(-1): 0 callbacks to make 2023-12-18 11:25:48.847 UTC [746] DEBUG: shmem_exit(0): 4 before_shmem_exit callbacks to make 2023-12-18 11:25:48.847 UTC [746] DEBUG: shmem_exit(0): 6 on_shmem_exit callbacks to make 2023-12-18 11:25:48.847 UTC [746] DEBUG: proc_exit(0): 2 callbacks to make 2023-12-18 11:25:48.847 UTC [746] DEBUG: exit(0) 2023-12-18 11:25:48.847 UTC [746] DEBUG: shmem_exit(-1): 0 before_shmem_exit callbacks to make 2023-12-18 11:25:48.847 UTC [746] DEBUG: shmem_exit(-1): 0 on_shmem_exit callbacks to make 2023-12-18 11:25:48.847 UTC [746] DEBUG: proc_exit(-1): 0 callbacks to make 2023-12-18 11:25:48.849 UTC [1] DEBUG: reaping dead processes 2023-12-18 11:25:48.849 UTC [1] DEBUG: server process (PID 744) exited with exit code 0 2023-12-18 11:25:48.849 UTC [1] DEBUG: server process (PID 743) exited with exit code 0 2023-12-18 11:25:48.849 UTC [1] DEBUG: server process (PID 745) exited with exit code 0 2023-12-18 11:25:48.849 UTC [1] DEBUG: server process (PID 746) exited with exit code 0 2023-12-18 11:25:48.849 UTC [1] DEBUG: reaping dead processes

Reproducer

No response

fila43 commented 6 months ago

Thank you for your report, but it's really hard to find the problem. Would it be possible to provide the reproducer?