Ludovic Courtès <[email protected]> writes:
> Could you show the output of ‘sudo herd status guix-daemon’ to see the
> ‘guix-daemon’ command line?
I use Guix on a foreign distribution, so guix-daemon is run by systemd.
Here is the output of the command `sudo systemctl status guix-daemon':
● guix-daemon.service - Build daemon for GNU Guix
Loaded: loaded (/etc/systemd/system/guix-daemon.service; enabled;
preset: disabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running) since Tue 2026-07-14 15:40:53 CEST; 1 day 8h
ago
Invocation: 9045adb269ff475e82eedfa49857c09f
Main PID: 3893499 (guix-daemon)
Tasks: 11 (limit: 8192)
Memory: 1.2M (peak: 77M, swap: 14.6M, swap peak: 14.7M)
CPU: 1.853s
CGroup: /system.slice/guix-daemon.service
├─3893499 guix-daemon --build-users-group=guixbuild
--discover=yes
└─3893511
/gnu/store/r3b2kp6gjbms6aff758fqyccl5kpllbh-guile-wrapper/bin/guile
--no-auto-compile /gnu/store/48h8hrxigbg4f4y63yla9ny25x8ahdhx-guix-command
discover
And, here is the output of the command `sudo systemctl cat guix-daemon':
# /etc/systemd/system/guix-daemon.service
# This is a "service unit file" for the systemd init system to launch
# 'guix-daemon'. Drop it in /etc/systemd/system or similar to have
# 'guix-daemon' automatically started.
[Unit]
Description=Build daemon for GNU Guix
[Service]
ExecStart=/var/guix/profiles/per-user/root/current-guix/bin/guix-daemon \
--build-users-group=guixbuild --discover=yes
Environment='GUIX_LOCPATH=/var/guix/profiles/per-user/root/guix-profile/lib/locale'
LC_ALL=en_US.utf8
StandardOutput=syslog
StandardError=syslog
# Work around a nasty systemd ‘feature’ that kills the entire process tree
# (including the daemon!) if any child, such as cc1plus, runs out of memory.
OOMPolicy=continue
# Despite the name, this is rate-limited: a broken daemon will eventually
fail.
Restart=always
# See <https://lists.gnu.org/archive/html/guix-devel/2016-04/msg00608.html>.
# Some package builds (for example, [email protected]) may require even more than
# 1024 tasks.
TasksMax=8192
[Install]
WantedBy=multi-user.target
# /usr/lib/systemd/system/service.d/10-timeout-abort.conf
# This file is part of the systemd package.
# See https://fedoraproject.org/wiki/Changes/Shorter_Shutdown_Timer.
#
# To facilitate debugging when a service fails to stop cleanly,
# TimeoutStopFailureMode=abort is set to "crash" services that fail to stop
in
# the time allotted. This will cause the service to be terminated with
SIGABRT
# and a coredump to be generated.
#
# To undo this configuration change, create a mask file:
# sudo mkdir -p /etc/systemd/system/service.d
# sudo ln -sv /dev/null
/etc/systemd/system/service.d/10-timeout-abort.conf
> Looks like X.509 certificates are missing from /etc/ssl/certs, which in
> turn causes Git to bail out.
>
> Could you make sure /etc/ssl/certs is populated, for instance with
> ‘nss-certs’?
The content of `/etc/ssl/certs' is:
* ca-bundle.crt
* ca-bundle.trust.crt
* ca-certificates.crt
As I'm using Fedora 44, there is some changes regarding SSL and TLS:
https://fedoraproject.org/wiki/Changes/droppingOfCertPemFile
Best regards
-------
Gendre Sébastien
