[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Upgrading Shepherd services
From: |
Attila Lendvai |
Subject: |
Re: Upgrading Shepherd services |
Date: |
Fri, 24 May 2024 17:19:51 +0000 |
> I see some services starting but no errors on the console. Also, there
> is absolutely nothing in /var/log/messages. Would it help to diagnose
> it using your Shepherd branch?
yep, in two ways: my branch has extensive logging (and currently its default
level is set to debug), and i also reworked and extended the error handling.
my expectation is that your machine should both start up, and also emit some
useful log why that specific service is failing.
if that is not the case, then i'd really love to see a self-contained
reproducer.
if you want to dig deeper towards a reproducer, then one option is to try to
write a guix system test that reproduces it (see gnu/tests/ for examples, and
`make check-system`).
to use my shepherd channel:
(channel
(name 'shepherd)
(url "https://codeberg.org/attila-lendvai-patches/shepherd.git")
(branch "attila")
(introduction
(make-channel-introduction
;; note that this commit id changes whenever i rebase and force-push my
commits
"13557ba988f4976f6581149ecdc06fce031258c7"
(openpgp-fingerprint
"69DA 8D74 F179 7AD6 7806 EE06 FEFA 9FE5 5CF6 E3CD"))))
and in your OS definition follow the instructions that are now in the shepherd
README.
HTH,
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“Gradualism in theory is perpetuity in practice.”
— Jared Howe
Re: Upgrading Shepherd services, Ludovic Courtès, 2024/05/17