unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Brantley, Michael" <Michael.Brantley@deshaw.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Problems with "guix offload test" after re-install
Date: Thu, 12 Oct 2017 10:05:24 +0200	[thread overview]
Message-ID: <87lgkgrdtn.fsf@gnu.org> (raw)
In-Reply-To: <a5ea58535cf54dfa8b8472ee7b0e2a51@mbxtoa2.winmail.deshaw.com> (Michael Brantley's message of "Wed, 11 Oct 2017 19:52:55 +0000")

Hello Michael,

"Brantley, Michael" <Michael.Brantley@deshaw.com> skribis:

> As this is my debut posting I just wanted to start by thanking the GUIX community for all your hard work!  :-)

Thank you!

> $ sudo -u guixuser guix environment
> [guixuser@guixbuild03 guix]$ bash -c "nohup guile --listen=37146 0<&- &>/dev/null"
>
> ... and then from another shell on this same host:
>
> $ telnet localhost 37146
> Trying 127.0.0.1...
> Connected to localhost.
> Escape character is '^]'.
> GNU Guile 2.2.2
> Copyright (C) 1995-2017 Free Software Foundation, Inc.
>
> Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
> This program is free software, and you are welcome to redistribute it
> under certain conditions; type `,show c' for details.
>
> Enter `,help' for help.
> scheme@(guile-user)> (begin
>                        (use-modules (guix))
>                        (with-store store
>                          (add-text-to-store store "test"
>                                             "Hello, build machine!")))
> acquiring global GC lock `/var/guix/gc.lock'
> acquiring read lock on `/var/guix/temproots/17043'
> acquiring write lock on `/var/guix/temproots/17043'
> downgrading to read lock on `/var/guix/temproots/17043'
> $1 = "/gnu/store/883yjkl46dxw9mzykykmbs0yzwyxm17z-test"
> scheme@(guile-user)> ,q
> Connection closed by foreign host.
> $
> $ telnet localhost 37146
> Trying 127.0.0.1...
> Connected to localhost.
> Escape character is '^]'.
> GNU Guile 2.2.2
> Copyright (C) 1995-2017 Free Software Foundation, Inc.
>
> Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
> This program is free software, and you are welcome to redistribute it
> under certain conditions; type `,show c' for details.
>
> Enter `,help' for help.
> scheme@(guile-user)> (begin
>                        (use-modules (guix))
>                        (with-store store
>                          (add-text-to-store store "test"
>                                             "Hello, build machine!")))
> ERROR: In procedure display:
> ERROR: In procedure display: Wrong type argument in position 2: #<closed: file c98f50>
>
> Entering a new prompt.  Type `,bt' for a backtrace or `,q' to continue.
> scheme@(guile-user) [1]>

Could you try “,bt” here to show the stack trace?  I wonder where that
exception comes from.

Are you sure guix-daemon is running on this machine, and listening to
the right socket file?

Thanks for the helpful debugging info!

Ludo’.

  reply	other threads:[~2017-10-12  8:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11 19:52 Problems with "guix offload test" after re-install Brantley, Michael
2017-10-12  8:05 ` Ludovic Courtès [this message]
2017-10-12 10:02   ` Brantley, Michael
2017-10-13 15:41     ` Ludovic Courtès

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=87lgkgrdtn.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=Michael.Brantley@deshaw.com \
    --cc=help-guix@gnu.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).