From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 25591 invoked from network); 16 Dec 2020 17:57:02 -0000 Received: from alyss.skarnet.org (95.142.172.232) by inbox.vuxu.org with ESMTPUTF8; 16 Dec 2020 17:57:02 -0000 Received: (qmail 11949 invoked by uid 89); 16 Dec 2020 17:57:25 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Received: (qmail 11939 invoked from network); 16 Dec 2020 17:57:25 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=ZkisX/QFQJMMdaw+WAIGcDi/f5d43Gs7ya6CJEwyILY=; b=SRBcyhA8vWnvKMkBk6lnXAF6wJ6A2fJYJc13xo+SnYtidu0cKZbI0hWubnPKin/Yk7 i6ZaOLyn5bANwqoiNexB+4VkzuoBeJuwS+Dfb9LZU2Lhv6m50Abj+/Mv6U9Jj1XGIXHl duIHjk0Gzc6qp4krAsiE/Nc8YFUUIIDpRvFFrBrJYLTbYws0GfWwJG57LTL5fHcjwMqy GZpq80UPDLAQ1MnROAZJ69F9vpln9XNVfm8lIPsyyvlkh6ZspxUrAbkoxbi43d+JeNzZ 0mA+Ex9rsqnN44mwhCtmZuofuUGZk4BHfDAhnjgiiMdABzq5zUKZOY59JT8XLdojOmzL JZXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=ZkisX/QFQJMMdaw+WAIGcDi/f5d43Gs7ya6CJEwyILY=; b=tBgtP8ypst/kzhsZ9Df+NXBqy4U/CMVHKVqQCmgY3kWFXaPkvW19YRc1vU8jvL1kh1 ch7Lm2o0bQnmJx2kJMl5qKOfJ1OxP3TgKQpzzZmAqtQqNPmo77zr07Y4BLg2QaTH3/dW 49+Fb+2StHT7+vXjLItatGegqoj5rUWzhjZFbW7bGMFHA3gz/M9Z5splNE0a0Ab6nREN 13aNjQl6ViPeGF8p86SzGWkNPLu+Arsziznhqf6sIWaG9I2hh+cnyfripmUzSfSPHjiZ zNnghjlNpME524o6tJJW+eBhXc+SD6pdT1HTFXegg99zuADlT0u1zB/FIr2ALoMnKIqQ nCcQ== X-Gm-Message-State: AOAM532d44GFiaoG5w075SG0MBfGUNv/wiUKTT4T1KbTrLymzWmXBeI0 qFzxg6inxK6g8VNGBbA9qmQluMaE0qt6VmoQ0t8h8KfUE+I= X-Google-Smtp-Source: ABdhPJyr4Nnv1ddfMd+9rQUL6xpvE93CJdjo8j0JKa6OiqKecA9duAymeEvjh4kuVnX0en/hrg/KFoFkIYlC1JhvQjY= X-Received: by 2002:a9f:26c5:: with SMTP id 63mr35335222uay.25.1608141416909; Wed, 16 Dec 2020 09:56:56 -0800 (PST) MIME-Version: 1.0 From: =?UTF-8?Q?Joshua_Ismael_Haase_Hern=C3=A1ndez?= Date: Wed, 16 Dec 2020 11:56:45 -0600 Message-ID: Subject: How to recover from s6-rc broken pipe? To: supervision@list.skarnet.org Content-Type: multipart/alternative; boundary="000000000000e7515105b6989985" --000000000000e7515105b6989985 Content-Type: text/plain; charset="UTF-8" I'm using s6-rc to manage services and have been changing databases. For some unknown reason sometimes the update fails with the error: s6-rc-update: fatal: unable to read /run/s6-rc/state: Broken pipe When that happens, I cannot use s6-rc anymore: /run/s6-rc does not exists, but s6-rc declares it as if it does: sudo s6-rc-init /run/s6 s6-rc-init: fatal: unable to supervise service directories in /run/s6-rc/servicedirs: File exists Creating the s6-rc symlink does not improve the situation. How should I recover from this error? --000000000000e7515105b6989985--