Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 19 Sep 2023 18:59:27 -0400
From:      Paul Procacci <pprocacci@gmail.com>
To:        Erwan David <erwan@rail.eu.org>
Cc:        FreeBSD <freebsd-questions@freebsd.org>
Subject:   Re: Ansible/vaultwarden restart after upgrade
Message-ID:  <CAFbbPuj8_%2BW9S=fcJ_v2DBTE0MdYSP5okNiDoNi4wLe0MLqj0A@mail.gmail.com>
In-Reply-To: <f5aa581c-4d1d-88c3-9c26-2e97315473e7@rail.eu.org>
References:  <f5aa581c-4d1d-88c3-9c26-2e97315473e7@rail.eu.org>

next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000ada7df0605be366c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Sep 19, 2023 at 6:40=E2=80=AFPM Erwan David <erwan@rail.eu.org> wro=
te:

> I have a some complicated problem.
>
> I upgrade packages through an ansible playbook which restarts the needed
> service after upgrade.
>
> it works, except for vaultwarden (from the ports), the task to restart is=
 :
>
> - name: restart
>   ansible.builtin.service:
>     name: "{{ item }}"
>     state: restarted
>   loop: "{{ services_to_restart | unique }}"
>
> and it is run in a jail through the jail connector of ansible
>
> When the service to restart is vaultwarden it hangs. When I kill the
> process I get error :
>
> failed: [vaultwarden] (item=3Dvaultwarden) =3D> {"ansible_loop_var": "ite=
m",
> "changed": false, "item": "vaultwarden", "module_stderr": "Terminated\n",
> "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the
> exact error", "rc": 143}
>
> which seems logical after a kill.
>
> This is freebsd specific, and ansible specific so I do not know where to
> ask.
>
> service vaultwarden restart works in the jail as well as service -j
> vaultwarden vaultwarden restart on the host (yes jail is caled vaultwarde=
n)
>
>
>
>
>
This problem may or may not depend on ansible.builtin.service.
You need to 1) add debugging to ansible via '-vvv' and then attempt to
duplicate this via the command line circumventing ansible to really see
where the problem lies.

Without the above it's all guesses.

Thanks,
Paul Procacci
--=20
__________________

:(){ :|:& };:

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

<div dir=3D"ltr"><div><div dir=3D"ltr"><br></div><br><div class=3D"gmail_qu=
ote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Sep 19, 2023 at 6:40=E2=
=80=AFPM Erwan David &lt;<a href=3D"mailto:erwan@rail.eu.org">erwan@rail.eu=
.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex">I have a some complicated problem.<br>
<br>
I upgrade packages through an ansible playbook which restarts the needed <b=
r>
service after upgrade.<br>
<br>
it works, except for vaultwarden (from the ports), the task to restart is :=
<br>
<br>
- name: restart<br>
=C2=A0=C2=A0ansible.builtin.service:<br>
=C2=A0=C2=A0=C2=A0=C2=A0name: &quot;{{ item }}&quot;<br>
=C2=A0=C2=A0=C2=A0=C2=A0state: restarted<br>
=C2=A0=C2=A0loop: &quot;{{ services_to_restart | unique }}&quot;<br>
<br>
and it is run in a jail through the jail connector of ansible<br>
<br>
When the service to restart is vaultwarden it hangs. When I kill the <br>
process I get error :<br>
<br>
failed: [vaultwarden] (item=3Dvaultwarden) =3D&gt; {&quot;ansible_loop_var&=
quot;: &quot;item&quot;, &quot;changed&quot;: false, &quot;item&quot;: &quo=
t;vaultwarden&quot;, &quot;module_stderr&quot;: &quot;Terminated\n&quot;, &=
quot;module_stdout&quot;: &quot;&quot;, &quot;msg&quot;: &quot;MODULE FAILU=
RE\nSee stdout/stderr for the exact error&quot;, &quot;rc&quot;: 143}<br>
<br>
which seems logical after a kill.<br>
<br>
This is freebsd specific, and ansible specific so I do not know where to as=
k.<br>
<br>
service vaultwarden restart works in the jail as well as service -j vaultwa=
rden vaultwarden restart on the host (yes jail is caled vaultwarden)<br>
<br>
<br>
<br>
<br>
</blockquote></div><br clear=3D"all"></div><div>This problem may or may not=
 depend on ansible.builtin.service.</div><div>You need to 1) add debugging =
to ansible via &#39;-vvv&#39; and then attempt to duplicate this via the co=
mmand line circumventing ansible to really see where the problem lies.</div=
><div><br></div><div>Without the above it&#39;s all guesses.</div><div><br>=
</div><div>Thanks,</div><div>Paul Procacci<br></div><div><span class=3D"gma=
il_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signatur=
e">__________________<br><br>:(){ :|:&amp; };:</div></div></div>

--000000000000ada7df0605be366c--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFbbPuj8_%2BW9S=fcJ_v2DBTE0MdYSP5okNiDoNi4wLe0MLqj0A>