From: 宋文武 <iyzsong@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, 白い熊@相撲道 <guix-devel_gnu.org@sumou.com>
Cc: guix-devel@gnu.org
Subject: Re: qemu-nbd: Failed to bind socket: No such file or directory
Date: Sun, 26 Apr 2015 12:07:09 +0800 [thread overview]
Message-ID: <87pp6rwn0y.fsf@gmail.com> (raw)
In-Reply-To: <87iodl5gmk.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> 白い熊@相撲道 <guix-devel_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 ‘log’ above “Failed to bind
>>> socket”.
>>
>> Yeah, was exploring this... I'm attaching the strace log, I don't
>> understand what's causing it... Any ideas?
>
> [...]
>
>> --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=2063, si_status=0, si_utime=0, si_stime=0} ---
>> read(3, "Failed to bind socket: No such f"..., 1024) = 49
>> write(2, "Failed to bind socket: No such f"..., 49) = 49
>
> The problem seems to happen in a child process. Can you add the ‘-f’
> flag to the ‘strace’ command line so we have details about 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’.
next prev parent reply other threads:[~2015-04-26 4:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 4:26 qemu-nbd: Failed to bind socket: No such file or directory 白い熊@相撲道
2015-03-26 21:24 ` Ludovic Courtès
2015-03-28 0:29 ` 白い熊@相撲道
2015-03-28 14:41 ` Ludovic Courtès
2015-04-26 4:07 ` 宋文武 [this message]
2015-04-29 20:28 ` 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=87pp6rwn0y.fsf@gmail.com \
--to=iyzsong@gmail.com \
--cc=guix-devel@gnu.org \
--cc=guix-devel_gnu.org@sumou.com \
--cc=ludo@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.
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).