<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Conjur Self-Hosted 13.10 rootless Podman: PostgreSQL doesn’t start after container restart, container exits with code 4 in Secrets Management</title>
    <link>https://live.paloaltonetworks.com/t5/secrets-management/conjur-self-hosted-13-10-rootless-podman-postgresql-doesn-t/m-p/1431333#M2269</link>
    <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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/&amp;lt;uid&amp;gt;/containers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;The first systemctl --user restart often fails (“did not take the steps required by its unit configuration”), and the second attempt works.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a recommended systemd unit for rootless Podman on 13.10 (stop sequence and timeout)?&lt;/P&gt;&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 18 Nov 2026 14:17:47 GMT</pubDate>
    <dc:creator>J.Banaszek598502</dc:creator>
    <dc:date>2026-11-18T14:17:47Z</dc:date>
    <item>
      <title>Conjur Self-Hosted 13.10 rootless Podman: PostgreSQL doesn’t start after container restart, container exits with code 4</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/conjur-self-hosted-13-10-rootless-podman-postgresql-doesn-t/m-p/1431333#M2269</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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/&amp;lt;uid&amp;gt;/containers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;The first systemctl --user restart often fails (“did not take the steps required by its unit configuration”), and the second attempt works.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a recommended systemd unit for rootless Podman on 13.10 (stop sequence and timeout)?&lt;/P&gt;&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Nov 2026 14:17:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/conjur-self-hosted-13-10-rootless-podman-postgresql-doesn-t/m-p/1431333#M2269</guid>
      <dc:creator>J.Banaszek598502</dc:creator>
      <dc:date>2026-11-18T14:17:47Z</dc:date>
    </item>
  </channel>
</rss>

