Skip to content

Fix PostgreSQL startup failure in non-systemd environments #6595

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 20, 2025

Conversation

KangweiZhu
Copy link
Contributor

PostgreSQL fails to start in non-systemd environments (e.g. Docker, GitLab Runner) because it cannot create the socket lock file at /run/postgresql/.s.PGSQL.5432.lock if the directory does not exist. This will also block openQA bootstrap process.

The specific error is:
pg_ctl: could not start server
Examine the log output.

Reproduce:
docker run -it --rm --name openqa-test opensuse/tumbleweed bash
zypper --non-interactive install openQA-bootstrap
/usr/share/openqa/script/openqa-bootstrap

PostgreSQL fails to start in non-systemd environments (e.g. Docker, GitLab Runner)
because it cannot create the socket lock file at /run/postgresql/.s.PGSQL.5432.lock
if the directory does not exist. This will also block openQA bootstrap process.

The specific error is:
    pg_ctl: could not start server
    Examine the log output.

Reproduce:
    docker run -it --rm --name openqa-test opensuse/tumbleweed bash
    zypper --non-interactive install openQA-bootstrap
    /usr/share/openqa/script/openqa-bootstrap
@okurz
Copy link
Member

okurz commented Jul 20, 2025

Hi @KangweiZhu thanks a lot for your contribution. This looks good.

+1

@mergify mergify bot merged commit 606fa3c into os-autoinst:master Jul 20, 2025
51 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants