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=-1.0 required=5.0 tests=MAILING_LIST_MULTI
	autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 18568 invoked from network); 16 Dec 2020 21:34:11 -0000
Received: from alyss.skarnet.org (95.142.172.232)
  by inbox.vuxu.org with ESMTPUTF8; 16 Dec 2020 21:34:11 -0000
Received: (qmail 14734 invoked by uid 89); 16 Dec 2020 21:34:30 -0000
Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm
Sender: <supervision@list.skarnet.org>
Precedence: bulk
List-Post: <mailto:supervision@list.skarnet.org>
List-Help: <mailto:supervision-help@list.skarnet.org>
List-Unsubscribe: <mailto:supervision-unsubscribe@list.skarnet.org>
List-Subscribe: <mailto:supervision-subscribe@list.skarnet.org>
List-Id: <supervision.list.skarnet.org>
Received: (qmail 14727 invoked from network); 16 Dec 2020 21:34:30 -0000
From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: =?utf-8?q?Joshua=20Ismael=20Haase=20Hern=c3=a1ndez?= <hahj87@gmail.com>,
 "supervision@list.skarnet.org" <supervision@list.skarnet.org>
Subject: Re: How to recover from s6-rc broken pipe?
Date: Wed, 16 Dec 2020 21:34:04 +0000
Message-Id: <em537b61d0-1ae3-423c-807e-a52d219815d0@elzian>
In-Reply-To: <CA+ypG2Y2ogrRxESR+r-_RkN9gUovRbk_vhbXr9DWQEd3kW0ZzQ@mail.gmail.com>
References: <CA+ypG2a_qGJtHhcS78TxQENpyPBQRhpfSDGMZETK0uqPYi7r-Q@mail.gmail.com>
 <em732a4d4a-739d-4752-8a7e-f08d0894b2bc@elzian>
 <CA+ypG2Y2ogrRxESR+r-_RkN9gUovRbk_vhbXr9DWQEd3kW0ZzQ@mail.gmail.com>
Reply-To: "Laurent Bercot" <ska-supervision@skarnet.org>
User-Agent: eM_Client/8.0.3385.0
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-VR-SPAMSTATE: OK
X-VR-SPAMSCORE: 0
X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedujedrudelvddgudehfecutefuodetggdotffvucfrrhhofhhilhgvmecupfgfoffgtffkveetuefngfdpqfgfvfenuceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffkjghfrhgfgggtgfesthhqredttderjeenucfhrhhomhepfdfnrghurhgvnhhtuceuvghrtghothdfuceoshhkrgdqshhuphgvrhhvihhsihhonhesshhkrghrnhgvthdrohhrgheqnecuggftrfgrthhtvghrnhepvdefgedtkeduieetgeefjeeivedtlefgvdefgfdvkefffeffueetgfdvudfglefgnecuffhomhgrihhnpegtohhmphhilhgvugdrnhgvfienucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhhouggvpehsmhhtphhouhht

>     sudo rsync -avr --delete compiled/ /etc/s6-rc/compiled/
>     sudo s6-rc-update /etc/s6-rc/compiled/

  There's your problem. You're overwriting the live database; that will
throw a wrench into everything.
  s6-rc-update needs to run while the live database is still the old
one. Only after s6-rc-update has completed can you delete the old
database.

  Do something like this instead:

stamp=3D`echo | s6-tai64n`
s6-rc-compile /etc/s6-rc/compiled-$stamp sources...
s6-rc-update /etc/s6-rc/compiled-$stamp
old=3D`readlink /etc/s6-rc/compiled`
ln -sf compiled-$stamp /etc/s6-rc/compiled.new
rename /etc/s6-rc/compiled.new /etc/s6-rc/compiled
rm -rf /etc/s6-rc/$old

--
  Laurent