unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: bug-guix@gnu.org
Subject: Re: Daemon: nix-connection-error
Date: Sat, 22 Jun 2013 22:01:31 +0200	[thread overview]
Message-ID: <87vc55gbj8.fsf@gnu.org> (raw)
In-Reply-To: <874ncq15fs.fsf@karetnikov.org> (Nikita Karetnikov's message of "Sat, 22 Jun 2013 20:22:15 +0400")

Nikita Karetnikov <nikita@karetnikov.org> skribis:

>> Also why do this as root?  It’s a Bad Idea.)
>
> Because I use Guix in a chroot.  Can it still be harmful?

Usually one never logs in as root.  You should only escalate as root
when needed, typically via sudo.

>> Any hints in test-suite.log or tests/*.log?
>
> No.

There’s probably an error message in test-suite.log in such cases.

>> Could you check the permissions on /nix/var/nix/daemon-socket/socket?
>
> srw-rw-rw- 1 root root 0 2013-06-22 01:34 socket
>
> I've found out that the following works:
>
> # ./pre-inst-env guix-daemon --build-users-group=nixbld &
> # ./pre-inst-env guix build -K hello
>
> But 'make check' fails for some reason.

‘make check’ uses a different store (see the ‘test-env’ script.)

It may be that $top_builddir/test-tmp/var/XXX/daemon-socket/socket is
created with the wrong user or permissions.

Could you check whether this works:

  ./test-env guile -c '(use-modules (guix store)) (pk (open-connection))'

If it fails, can you prefix that command line with ‘strace -f -o log’,
and post the output of ‘grep daemon-socket log’?

TIA,
Ludo’.

  reply	other threads:[~2013-06-22 20:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-22  2:28 Daemon: nix-connection-error Nikita Karetnikov
2013-06-22 15:01 ` Ludovic Courtès
2013-06-22 16:22   ` Nikita Karetnikov
2013-06-22 20:01     ` Ludovic Courtès [this message]
2013-06-22 23:45       ` Nikita Karetnikov
2013-06-23  9:39         ` Ludovic Courtès
2013-06-23 17:06           ` Nikita Karetnikov
2013-06-23 20:20             ` Ludovic Courtès
2013-06-23 21:46               ` Nikita Karetnikov
2013-06-23 23:05                 ` 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=87vc55gbj8.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-guix@gnu.org \
    --cc=nikita@karetnikov.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 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).