From nobody Tue Sep 19 22:59:27 2023 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Rqxv30bbQz4t78P for ; Tue, 19 Sep 2023 22:59:43 +0000 (UTC) (envelope-from pprocacci@gmail.com) Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Rqxv24VNVz4HxV for ; Tue, 19 Sep 2023 22:59:42 +0000 (UTC) (envelope-from pprocacci@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x631.google.com with SMTP id a640c23a62f3a-99c93638322so67055466b.1 for ; Tue, 19 Sep 2023 15:59:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1695164380; x=1695769180; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=cFyoR5iI1oTc1Sr/tLG1Nbn+dgpMBCfyFn1s8et9Q2Q=; b=kUZ4IrSCUNsW0voNJSG6s4mcf/+nGwWjG3rPA6v7QaOYzI6dTGgsDRGlpNd2IpfJVo IS+vX0jfNQ1JNcRpBLWA7lzse1tInCEfz+dnX0MhEo2AN18DjyMyWZgPnyD0FhJOVq+K GZ1d2/ow03YjC8k8KNMhhtdMmth112bGiiSvlps37jSvhTtAKT9TLe/tNscZ05vLzU2o g3yhoPtb2HsW5Ai86vrrjSZJQWzwL7hfjZOjAwZ66xX4tnthJPjRm9kK8m2Vcm+EqbW7 nSlBQmfPYgOIme5hpruFEJbA1cnmKbm0iz8RYX02XwZrODCHXBRHsaMVasV/aAvfvOVW J68w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695164380; x=1695769180; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=cFyoR5iI1oTc1Sr/tLG1Nbn+dgpMBCfyFn1s8et9Q2Q=; b=Ob6thqNqncR0/xEd/ne8soUFFcjkiZ4oQRfHSq1lkoVkduud05uyiYKLLLcIWY5JrU HRTTL++NxZll2ON6D8ajNsuoGadkQd4mwgw0PtpLFtbV4yWMSLgQtWA1RZLcqKA+uuzZ /+zzGexq23cNSZhYCbu/VQhGCoTWMZm11qft+bhvB/kk1vuPURJy8/cYi1xiNfeyLmYV yIvKooB+9p/b36SlekGaH2UywyS3MqzN4dk3I8YC9eGKG+tTSLF7SW0KamfN1D9qBMDW IZxWEg+/xGNeXLw9tsxvgOcgocUBR7FkJF/lBth35hlUWZ7FhHYCSFdV3eWu5NnaIhKR zv6w== X-Gm-Message-State: AOJu0Yy1dwXOFuLxAJ+UfwAGghsLHcs7DRbF1kM9Ko5d3sY4EMcaaUIF qW6KA9WX3w9hrIAR/gHo5nvGCyCDCflymFYQUQ== X-Google-Smtp-Source: AGHT+IHrqmzCmQ6iCJrvJgA8iroLOWWzta2Pk0V7iUozTS0Fbf5Tbcv1SMe99HL3H4iMoQmphlUtkkU8R1NTboLOcAg= X-Received: by 2002:a17:906:8a6b:b0:9a2:295a:9bbc with SMTP id hy11-20020a1709068a6b00b009a2295a9bbcmr1045467ejc.37.1695164379538; Tue, 19 Sep 2023 15:59:39 -0700 (PDT) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Paul Procacci Date: Tue, 19 Sep 2023 18:59:27 -0400 Message-ID: Subject: Re: Ansible/vaultwarden restart after upgrade To: Erwan David Cc: FreeBSD Content-Type: multipart/alternative; boundary="000000000000ada7df0605be366c" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4Rqxv24VNVz4HxV --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 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


On Tue, Sep 19, 2023 at 6:40=E2= =80=AFPM Erwan David <erwan@rail.eu= .org> wrote:
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
=C2=A0=C2=A0ansible.builtin.service:
=C2=A0=C2=A0=C2=A0=C2=A0name: "{{ item }}"
=C2=A0=C2=A0=C2=A0=C2=A0state: restarted
=C2=A0=C2=A0loop: "{{ 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&= quot;: "item", "changed": false, "item": &quo= t;vaultwarden", "module_stderr": "Terminated\n", &= quot;module_stdout": "", "msg": "MODULE FAILU= RE\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 as= k.

service vaultwarden restart works in the jail as well as service -j vaultwa= rden vaultwarden restart on the host (yes jail is caled vaultwarden)





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 co= mmand line circumventing ansible to really see where the problem lies.

Without the above it's all guesses.

=
Thanks,
Paul Procacci
--
__________________

:(){ :|:& };:
--000000000000ada7df0605be366c--