Conjur Self-Hosted 13.10 rootless Podman: PostgreSQL doesn’t start after container restart, container exits with code 4

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Conjur Self-Hosted 13.10 rootless Podman: PostgreSQL doesn’t start after container restart, container exits with code 4

L1 Bithead

Hello

 

Enviroment is Conjur Self-Hosted 13.10.0 (FIPS, seccomp), RHEL 9.8, Podman 5.8.2, rootless, systemd user unit from podman generate systemd --name, auto-failover cluster. Admins log in via sudo + su - conjur. There is no login session, so XDG_RUNTIME_DIR is not set and every systemctl --user call needs XDG_RUNTIME_DIR=/run/user/$(id -u). Podman runRoot is /run/user/<uid>/containers.

 

The default unit stops the container with podman stop -t 10, which ends in SIGKILL. After the next start PostgreSQL doesn’t start (runsv pg is running, but there is no postgres process, and stale sockets remain in /var/run/postgresql). evoke-cluster loops on “No such file or directory” for the socket, and nginx/possum stay down. Once we also hit a PANIC on pg_logical/replorigin_checkpoint.tmp.

With a graceful stop (sv stop for all services, then pg), PostgreSQL stops cleanly. PID 1 then still takes ~60 s to exit and exits with code 4, so the unit ends up failed.

The first systemctl --user restart often fails (“did not take the steps required by its unit configuration”), and the second attempt works.

 

Is there a recommended systemd unit for rootless Podman on 13.10 (stop sequence and timeout)?

This is a production environment. Every restart is risky: OS patching, upgrades, even a single service restart. Over the last two weeks restarts caused a chain of failovers. 

 

0 REPLIES 0
  • 2 Views
  • 0 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!