postgres constantly restarted inside container
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
No files, tests, or entry points are named. Start by reviewing the PostgreSQL container configuration and complete logs around the reported exit code 0, then correlate them with container runtime events and the Node application's connection failures. Done means identifying a reproducible cause and a concrete change that prevents the interruptions.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- PLpgSQL
- Stars
- 178
- Forks
- 220
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from sclorg/postgresql-container
-
Difficulty 2/5 1-2 days Newbie friendliness 72/100
sclorg/postgresql-container#661 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
sclorg/postgresql-container#669 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
sclorg/postgresql-container#668 ·
-
Dockerfile failing Open
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
sclorg/postgresql-container#656 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
sclorg/postgresql-container#654 ·
All issues in sclorg/postgresql-container
Similar issues
-
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
[BUG] A column whose default is the empty string is drawn in the ER diagram as having no default Openbug database-provider good first issue hacktoberfest
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
libredb/libredb-studio#1030 · 6 comments ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug redshift
Difficulty 2/5 1-3 hours Newbie friendliness 88/100