GNU bug report logs - #23274
Misleading error message when running guix-daemon as unprivileged user

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 23274 in the body.
You can then email your comments to 23274 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: bug-guix <at> gnu.org
Subject: Misleading error message when running guix-daemon as unprivileged user
Date: Mon, 11 Apr 2016 21:22:37 -0400

When trying to start the guix-daemon as an unprivileged user, the
following error message is printed:

error: cannot bind to socket `/var/guix/daemon-socket/socket': Address already in use

Would it make sense to try to provide a more helpful error message?

Message #10 received at 23274 <at> debbugs.gnu.org (full text, mbox):

From: Martin Castillo <castilma <at> uni-bremen.de>
To: 23274 <at> debbugs.gnu.org
Subject: Re: Misleading error message when running guix-daemon as unprivileged
 user
Date: Sat, 9 Dec 2017 16:28:58 +0100

[Message part 1 (text/plain, inline)]

Hi,

“Address already in use” makes me directly think that there is already
another daemon running. Strangely, starting another daemon as root
works. It seems to take the socket from the other daemon away. Is this
intended? Or can two daemons run in parallel without problems?

What is your use case? Do you want to run the daemon us unprivileged
user or did you forget to add sudo?

Martin

-- 
GPG: 7FDE 7190 2F73 2C50 236E  403D CC13 48F1 E644 08EC

[signature.asc (application/pgp-signature, attachment)]

Message #13 received at 23274 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Martin Castillo <castilma <at> uni-bremen.de>
Cc: 23274 <at> debbugs.gnu.org
Subject: Re: bug#23274: Misleading error message when running guix-daemon as
 unprivileged user
Date: Mon, 11 Dec 2017 10:35:50 +0100

Hi Martin,

Martin Castillo <castilma <at> uni-bremen.de> skribis:

> “Address already in use” makes me directly think that there is already
> another daemon running. Strangely, starting another daemon as root
> works. It seems to take the socket from the other daemon away. Is this
> intended? Or can two daemons run in parallel without problems?

What you’re seeing here is the error return by bind(2) while trying to
bind the listening socket to /var/guix/daemon-socket/socket.
guix-daemon doesn’t try to interpret the error in any way, it just shows
you what the OS reported.

So I’m not sure there’s really an issue here.

WDYT?

Ludo’.

Message #16 received at 23274 <at> debbugs.gnu.org (full text, mbox):

From: Martin Castillo <castilma <at> uni-bremen.de>
To: ludo <at> gnu.org
Cc: 23274 <at> debbugs.gnu.org
Subject: Re: bug#23274: Misleading error message when running guix-daemon as
 unprivileged user
Date: Mon, 11 Dec 2017 14:25:00 +0100

Hi,

I could have expressed myself  more clearly.

> “Address already in use” makes me directly think that there is already
>another daemon running.

This was in response to OP, saying that I don't think that needs to be changed.

The rest was about testing it with root and I (half) expected an error message that explicitly says, that another daemon is already running. If this was right, op would be right. But this is not the case and it seems like it is wanted the way it is.

So yes, there is no problem in my eyes, too. This can be closed.

Martin

Message #21 received at 23274-done <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Martin Castillo <castilma <at> uni-bremen.de>
Cc: 23274-done <at> debbugs.gnu.org
Subject: Re: bug#23274: Misleading error message when running guix-daemon as
 unprivileged user
Date: Mon, 11 Dec 2017 17:22:18 +0100

Hi Martin,

Martin Castillo <castilma <at> uni-bremen.de> skribis:

>> “Address already in use” makes me directly think that there is already
>>another daemon running.
>
> This was in response to OP, saying that I don't think that needs to be changed.
>
> The rest was about testing it with root and I (half) expected an error message that explicitly says, that another daemon is already running. If this was right, op would be right. But this is not the case and it seems like it is wanted the way it is.
>
> So yes, there is no problem in my eyes, too. This can be closed.

OK, I had completely misunderstood, thanks for clarifying.  Closing!

Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.