MIME-Version: 1.0
References: <emf4c21a82-984c-4bc4-91e8-79bdf35bc018@79dd1d3b.com>
In-Reply-To: <emf4c21a82-984c-4bc4-91e8-79bdf35bc018@79dd1d3b.com>
From: Aaron Pavely <aaron@pavely.net>
Date: Thu, 6 Nov 2025 22:06:31 -0600
Message-ID: 
 <CAGs4muUsHP9ctE_Le2djfnf3ZzQp=_pdCiz9LkwaVtDoaUAsSg@mail.gmail.com>
Subject: Re: Patroni 4.1.0 causes issues because of systemd notify
To: pgsql-pkg-debian@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000002805200642f94fa5"
Archived-At: 
 <https://www.postgresql.org/message-id/CAGs4muUsHP9ctE_Le2djfnf3ZzQp%3D_pdCiz9LkwaVtDoaUAsSg%40mail.gmail.com>
Precedence: bulk

--0000000000002805200642f94fa5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sun, Nov 2, 2025 at 2:27=E2=80=AFPM Hauke Bruno Wollentin <me@hauke.ninj=
a> 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=E2=80=99t 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=3Dsimple` in the systemd unit file works pretty =
fine.
>
> I=E2=80=99m 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

--0000000000002805200642f94fa5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">On Sun, Nov 2, 2025 at 2=
:27=E2=80=AFPM Hauke Bruno Wollentin &lt;me@hauke.ninja&gt; wrote:</div><di=
v class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><=
div>


<div style=3D"background-color:white;color:black"><div>Hi all,</div><div><b=
r></div><div>while spinning up new Patroni cluster with version 4.1.0 (whic=
h has been added to the Debian repo 2 days ago), my clusters won=E2=80=99t =
bootstrap properly anymore.</div><div><br></div><div>At first, logs looks c=
lear but anyways, all systemd operations like start/stop/restart will run i=
nto a timeout, causing the service to stop which then will break the cluste=
r at all.</div><div><br></div><div>It seems like the new systemd notify fea=
ture is causing this, since using Patroni 4.0.7 with `Type=3Dsimple` in the=
 systemd unit file works pretty fine.</div><div><br></div><div>I=E2=80=99m =
on Debian 12 and psql 17.</div></div></div></blockquote><div>=C2=A0</div><d=
iv>Just a quick question: Has the python3-systemd package been installed as=
 well?</div><div><br>There are multiple issues from the upstream Patroni Gi=
tHub repository reporting similar problems since the release of 4.1.0,=C2=
=A0and the corresponding solution is installing that python3-systemd packag=
e. It is not (yet) listed as a patroni package dependency, so it may have b=
een missed given the new functionality in 4.1.0.<br><br>Ref:<br><a href=3D"=
https://github.com/patroni/patroni/issues/3480" target=3D"_blank">https://g=
ithub.com/patroni/patroni/issues/3480</a><br><a href=3D"https://github.com/=
patroni/patroni/issues/3482" target=3D"_blank">https://github.com/patroni/p=
atroni/issues/3482</a></div><div><br></div><div>-- Aaron Pavely</div></div>=
</div>
</div>

--0000000000002805200642f94fa5--