From: "Joshua Ismael Haase Hernández" <hahj87@gmail.com>
To: supervision@list.skarnet.org
Subject: How to recover from s6-rc broken pipe?
Date: Wed, 16 Dec 2020 11:56:45 -0600 [thread overview]
Message-ID: <CA+ypG2a_qGJtHhcS78TxQENpyPBQRhpfSDGMZETK0uqPYi7r-Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
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?
next reply other threads:[~2020-12-16 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 17:56 Joshua Ismael Haase Hernández [this message]
2020-12-16 20:11 ` Laurent Bercot
[not found] ` <CA+ypG2Y2ogrRxESR+r-_RkN9gUovRbk_vhbXr9DWQEd3kW0ZzQ@mail.gmail.com>
2020-12-16 21:34 ` Laurent Bercot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+ypG2a_qGJtHhcS78TxQENpyPBQRhpfSDGMZETK0uqPYi7r-Q@mail.gmail.com \
--to=hahj87@gmail.com \
--cc=supervision@list.skarnet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).