public inbox for [email protected]  

help / color / mirror / Atom feed

From: Aaron Pavely <[email protected]>
To: [email protected]
Subject: Re: Patroni 4.1.0 causes issues because of systemd notify
Date: Thu, 6 Nov 2025 22:06:31 -0600
Message-ID: <CAGs4muUsHP9ctE_Le2djfnf3ZzQp=_pdCiz9LkwaVtDoaUAsSg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

On Sun, Nov 2, 2025 at 2:27 PM Hauke Bruno Wollentin <[email protected]> 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

view thread (4+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Patroni 4.1.0 causes issues because of systemd notify
  In-Reply-To: <CAGs4muUsHP9ctE_Le2djfnf3ZzQp=_pdCiz9LkwaVtDoaUAsSg@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox