From: "Ludovic Courtès" <ludo@gnu.org>
To: dal-blazej@onenetbeyond.org
Cc: 53904@debbugs.gnu.org
Subject: bug#53904: Using an http proxy, derivation failed
Date: Tue, 08 Mar 2022 09:42:10 +0100 [thread overview]
Message-ID: <87wnh496ot.fsf@gnu.org> (raw)
In-Reply-To: <877d9ccstb.fsf@onenetbeyond.org> (dal-blazej@onenetbeyond.org's message of "Wed, 02 Mar 2022 15:50:08 +0100")
Hi,
dal-blazej@onenetbeyond.org skribis:
> The systemd unit file from debian looks like that
> (I only added the https_proxy, with localhost or 127.0.0.1, with or
> without the leading http://):
[...]
> [Service]
> ExecStart=/var/guix/profiles/per-user/root/current-guix/bin/guix-daemon --build-users-group=guixbuild
> Environment='GUIX_LOCPATH=/var/guix/profiles/per-user/root/guix-profile/lib/locale' LC_ALL=en_US.utf8 'https_proxy=http://localhost:8082/'
Looks good to me.
> After reloading the daemons and restarting the daemon :
>
> guix pull: error: failed to connect to `/var/guix/daemon-socket/socket': Connection refused
This suggests that guix-daemon is not running. Could it be that it
failed to start? Does ‘journalctl -u guix-daemon.service’ contain any
clue?
BTW, according to the output you pasted earlier (in particular the noisy
locale warnings), it seems that your daemon needs an update. Check out
<https://guix.gnu.org/manual/devel/en/html_node/Upgrading-Guix.html>.
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-03-08 8:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 19:21 bug#53904: Using an http proxy, derivation failed dal-blazej--- via Bug reports for GNU Guix
2022-02-12 11:21 ` Josselin Poiret via Bug reports for GNU Guix
2022-03-02 14:50 ` dal-blazej--- via Bug reports for GNU Guix
2022-03-08 8:42 ` Ludovic Courtès [this message]
2022-03-08 19:35 ` dal-blazej--- via Bug reports for GNU Guix
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=87wnh496ot.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=53904@debbugs.gnu.org \
--cc=dal-blazej@onenetbeyond.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.