From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: qemu-nbd: Failed to bind socket: No such file or directory Date: Sat, 28 Mar 2015 15:41:23 +0100 Message-ID: <87iodl5gmk.fsf@gnu.org> References: <87h9t7qwoz.fsf@gnu.org> <9e22916c65c4356f3c037983f777a110@hcoop.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54355) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YbrvW-0001pL-8v for guix-devel@gnu.org; Sat, 28 Mar 2015 10:41:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YbrvS-0000mY-2G for guix-devel@gnu.org; Sat, 28 Mar 2015 10:41:30 -0400 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:41250) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YbrvR-0000mU-VQ for guix-devel@gnu.org; Sat, 28 Mar 2015 10:41:25 -0400 In-Reply-To: <9e22916c65c4356f3c037983f777a110@hcoop.net> (=?utf-8?B?Ig==?= =?utf-8?B?55m944GE54aK77yg55u45pKy6YGTIidz?= message of "Sat, 28 Mar 2015 01:29:06 +0100") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: =?utf-8?B?55m944GE54aK77yg55u45pKy6YGT?= Cc: guix-devel@gnu.org =E7=99=BD=E3=81=84=E7=86=8A=EF=BC=A0=E7=9B=B8=E6=92=B2=E9=81=93 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 about = child processes? TIA, Ludo=E2=80=99.