From: dal-blazej--- via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: 53904@debbugs.gnu.org
Subject: bug#53904: Using an http proxy, derivation failed
Date: Wed, 02 Mar 2022 15:50:08 +0100 [thread overview]
Message-ID: <877d9ccstb.fsf@onenetbeyond.org> (raw)
In-Reply-To: <87fsoomiu4.fsf@jpoiret.xyz> (Josselin Poiret's message of "Sat, 12 Feb 2022 12:21:07 +0100")
Hi debbugs,
The following mails was not CC to 53904@debbugs.gnu.org so let's correct
that :
* 1 dal to jpoiret
Hi Josselin,
Josselin Poiret <dev@jpoiret.xyz> writes:
> What went wrong while modifying the systemd unit?
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://):
#+begin_src conf :tangle "/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
Environment='GUIX_LOCPATH=/var/guix/profiles/per-user/root/guix-profile/lib/locale' LC_ALL=en_US.utf8 'https_proxy=http://localhost:8082/'
RemainAfterExit=yes
StandardOutput=syslog
StandardError=syslog
# See <https://lists.gnu.org/archive/html/guix-devel/2016-04/msg00608.html>.
# Some package builds (for example, go@1.8.1) may require even more than
# 1024 tasks.
TasksMax=8192
[Install]
WantedBy=multi-user.target
#+end_src
After reloading the daemons and restarting the daemon :
guix pull: error: failed to connect to `/var/guix/daemon-socket/socket': Connection refused
By the way, I previously tested the proxy itself via wget and it
works. I also tried some others variations on the unit file without more success.
* 2 jpoiret to dal
Hello,
dal-blazej@onenetbeyond.org writes:
> After reloading the daemons and restarting the daemon :
>
> guix pull: error: failed to connect to `/var/guix/daemon-socket/socket': Connection refused
>
> By the way, I previously tested the proxy itself via wget and it
> works. I also tried some others variations on the unit file without more success.
I'm not very familiar with the Debian Guix package, but can you check
that /var/guix/profiles/per-user/root/current-guix/bin/guix-daemon does
indeed exist? If not, you may need to log-in as root, and run `guix
pull` there. Did the systemd unit ever work, and if not, how do you run
the Guix daemon?
Best,
--
Josselin Poiret
* 3 dal to jpoiret
Thanks for your help Josselin.
I precise that I am able to run guix in a debian standaloneVM without proxy.
I feared to have messed up something in that template so I started again
from scratch.
- I modified /usr/lib/systemd/system/guix-daemon.service and
/usr/lib/systemd/system/guix-publish.service to use
https_proxy=http:///127.0.0.1:8082
> I'm not very familiar with the Debian Guix package, but can you check
> that /var/guix/profiles/per-user/root/current-guix/bin/guix-daemon does
> indeed exist?
- /var/guix/profiles/per-user/root/current-guix doesn't exist.
> If not, you may need to log-in as root, and run `guix pull` there.
- guix pull (as user or root) :
#+begin_exemple
Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
guix pull: error: Git error: failed to resolve address for
git.savannah.gnu.org: Temporary failure in name resolution
#+end_exemple
I am still able to use my proxy with wget.
> Did the systemd unit ever work, and if not, how do you run
> the Guix daemon?
- guix-daemon.service is now running without error.
- guix-publish.service throw an error (but I guess it is another issue):
#+begin_exemple
● guix-publish.service - Publish the GNU Guix store
Loaded: loaded (/lib/systemd/system/guix-publish.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2022-02-17 16:44:00 CET; 7min ago
Process: 7397 ExecStart=/usr/bin/guix publish --user=nobody --port=8181 (code=exited, status=1/FAILURE)
Main PID: 7397 (code=exited, status=1/FAILURE)
CPU: 184ms
Feb 17 16:44:00 localhost systemd[1]: Started Publish the GNU Guix store.
Feb 17 16:44:00 localhost guix[7397]: guix publish: error: open-file: No such file or directory: "/etc/guix/signing-key.pub"
Feb 17 16:44:00 localhost systemd[1]: guix-publish.service: Main process exited, code=exited, status=1/FAILURE
Feb 17 16:44:00 localhost systemd[1]: guix-publish.service: Failed with result 'exit-code'.
#+end_exemple
next prev parent reply other threads:[~2022-03-02 15:03 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 [this message]
2022-03-08 8:42 ` Ludovic Courtès
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
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=877d9ccstb.fsf@onenetbeyond.org \
--to=bug-guix@gnu.org \
--cc=53904@debbugs.gnu.org \
--cc=dal-blazej@onenetbeyond.org \
--cc=dev@jpoiret.xyz \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).