Add post-start hook to remove stale PostgreSQL sockets#620
Closed
PiRomant wants to merge 1 commit intogreenbone:mainfrom
Closed
Add post-start hook to remove stale PostgreSQL sockets#620PiRomant wants to merge 1 commit intogreenbone:mainfrom
PiRomant wants to merge 1 commit intogreenbone:mainfrom
Conversation
Contributor
|
IMHO it is better to address this issue already in the pg-gvm container directly. See greenbone/pg-gvm#119 |
auto-merge was automatically disabled
March 24, 2026 14:28
Pull request was closed
Author
|
@bjoernricks, but with my approach, the deletion operation runs as the root user. At one point I faced an issue where a similar clearing from redis did not work. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Added post_start exec action to the postgres service that safely removes common socket/lock files before PostgreSQL binds.
No data loss risk - only removes ephemeral socket/lock files.
Container now starts reliably even after abrupt SIGKILL
Tested: Verified volume cleanup works after forced inserted socket and lock files in
greenbone-community-edition_psql_socket_volbefore container started.Why
PostgreSQL often fails to start due to stale socket files (like .s.PGSQL.5432) or lock files left from improper shutdowns, causing errors about existing sockets or locks.
Abstract sockets (
@/tmp) avoid this entirely but can’t share across containers.Checklist