From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?utf-8?B?5a6L5paH5q2m?= <iyzsong@gmail.com>
Subject: Re: qemu-nbd: Failed to bind socket: No such file or directory
Date: Sun, 26 Apr 2015 12:07:09 +0800
Message-ID: <87pp6rwn0y.fsf@gmail.com>
References: <cd4795b07378aa8c33c1b7f50ff09253@hcoop.net>
	<87h9t7qwoz.fsf@gnu.org>
	<9e22916c65c4356f3c037983f777a110@hcoop.net>
	<87iodl5gmk.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:44539)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <iyzsong@gmail.com>) id 1YmDq5-0005mn-J3
	for guix-devel@gnu.org; Sun, 26 Apr 2015 00:06:42 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <iyzsong@gmail.com>) id 1YmDq4-00070Q-Of
	for guix-devel@gnu.org; Sun, 26 Apr 2015 00:06:41 -0400
In-Reply-To: <87iodl5gmk.fsf@gnu.org>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
To: Ludovic =?utf-8?Q?Court=C3=A8s?= <ludo@gnu.org>, =?utf-8?B?55m944GE?= =?utf-8?B?54aK77yg55u45pKy6YGT?= <guix-devel_gnu.org@sumou.com>
Cc: guix-devel@gnu.org

Ludovic Court=C3=A8s <ludo@gnu.org> writes:

> =E7=99=BD=E3=81=84=E7=86=8A=EF=BC=A0=E7=9B=B8=E6=92=B2=E9=81=93 <guix-dev=
el_gnu.org@sumou.com> skribis:
>
>> On 2015-03-26 22:24, ludo@gnu.org wrote:
>>> I have no idea, but I would recommend running:
>>>
>>>   sudo strace -o log qemu-nbd -c /dev/nbd0 disk.qcow2
>>>
>>> and then find out the socket name in =E2=80=98log=E2=80=99 above =E2=80=
=9CFailed to bind
>>> socket=E2=80=9D.
>>
>> Yeah, was exploring this... I'm attaching the strace log, I don't
>> understand what's causing it... Any ideas?
>
> [...]
>
>> --- SIGCHLD {si_signo=3DSIGCHLD, si_code=3DCLD_EXITED, si_pid=3D2063, si=
_status=3D0, si_utime=3D0, si_stime=3D0} ---
>> read(3, "Failed to bind socket: No such f"..., 1024) =3D 49
>> write(2, "Failed to bind socket: No such f"..., 49) =3D 49
>
> The problem seems to happen in a child process.  Can you add the =E2=80=
=98-f=E2=80=99
> flag to the =E2=80=98strace=E2=80=99 command line so we have details abou=
t child
> processes?
I tried 'strace -f', then find out that qemu-nbd need access to "/var/lock".
After "mkdir /var/lock", it works.
>
> TIA,
> Ludo=E2=80=99.