From: Hilton Chain <hako@ultrarare.space>
To: Tanguy LE CARROUR <tanguy@bioneland.org>
Cc: help-guix@gnu.org
Subject: Re: Problem with Shepherd after `guix home reconfigure`
Date: Tue, 22 Aug 2023 23:18:15 +0800 [thread overview]
Message-ID: <875y57w1fs.wl-hako@ultrarare.space> (raw)
In-Reply-To: <169271226794.29627.13908806565940408141@localhost>
On Tue, 22 Aug 2023 21:51:07 +0800,
Tanguy LE CARROUR wrote:
>
> Hi Hilton,
>
> First of, I have to apologize to Shep[H]erd for the typo! Soooorry! 😅
> I've just fixed it in the subject.
>
>
No worry :)
> > Thank you for reporting the issue!
> >
> > This is caused by a missing module in mcron's service definition, and
> > now it should be fixed in 552d0703776c532f25498d5cb852c3c497cb9252.
> >
> > Please run `guix pull', then reconfigure the home environment.
>
> Much better! Thanks! 👍
>
> I still have an error message, though:
If you happen to use the system mcron service as well, please pull to
the latest commit again, my bad :(
> ```
> $ guix home reconfigure
> # […]
> Loading /gnu/store/zbfyaxxigns5lqyxhxzxhm92w54ns1cz-shepherd.conf.
> herd: error: exception caught while executing 'load' on service 'root':
> In procedure fport_write: Input/output error
> ```
>
> I've just tried something that, as weird as it sounds, I had never done before:
> `herd stop mcron`! And… it just hangs forever!? I guess it not the
> expected behaviour?! 🤔
> I `ctrl+c`-ed it and, now, `herd status` also hangs forever!? 😞
> I'll see if everything goes back to normal after the next reboot…
I don't know much about Shepherd but rebooting seems to be the only
solution when it hangs...
next prev parent reply other threads:[~2023-08-22 15:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 10:33 Problem with Sheperd after `guix home reconfigure` Tanguy LE CARROUR
2023-08-22 12:40 ` Hilton Chain
2023-08-22 13:23 ` Andreas Enge
2023-08-22 14:44 ` Hilton Chain
2023-08-22 13:51 ` Problem with Shepherd " Tanguy LE CARROUR
2023-08-22 15:18 ` Hilton Chain [this message]
2023-08-22 16:56 ` Tanguy LE CARROUR
2023-08-23 3:19 ` Hilton Chain
2023-08-23 6:29 ` Tanguy LE CARROUR
2023-08-23 8:09 ` nils
2023-08-25 6:59 ` Tanguy LE CARROUR
2023-08-25 7:34 ` Hilton Chain
2023-08-28 6:27 ` Tanguy LE CARROUR
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875y57w1fs.wl-hako@ultrarare.space \
--to=hako@ultrarare.space \
--cc=help-guix@gnu.org \
--cc=tanguy@bioneland.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 read-only IMAP folder(s) and NNTP newsgroup(s).