Re[2]: Patroni 4.1.0 causes issues because of systemd notify

On Sun, Nov 2, 2025 at 2:27 PM Hauke Bruno Wollentin <me@hauke.ninja> wrote:

Hi all,

while spinning up new Patroni cluster with version 4.1.0 (which has been added to the Debian repo 2 days ago), my clusters won’t bootstrap properly anymore.

At first, logs looks clear but anyways, all systemd operations like start/stop/restart will run into a timeout, causing the service to stop which then will break the cluster at all.

It seems like the new systemd notify feature is causing this, since using Patroni 4.0.7 with `Type=simple` in the systemd unit file works pretty fine.

I’m on Debian 12 and psql 17.

 

Just a quick question: Has the python3-systemd package been installed as well?

There are multiple issues from the upstream Patroni GitHub repository reporting similar problems since the release of 4.1.0, and the corresponding solution is installing that python3-systemd package. It is not (yet) listed as a patroni package dependency, so it may have been missed given the new functionality in 4.1.0.

Ref:
https://github.com/patroni/patroni/issues/3480
https://github.com/patroni/patroni/issues/3482

-- Aaron Pavely