From: Chris Dunlop <chris@onthe.net.au>
To: ceph-devel@vger.kernel.org
Subject: Re: Simple test system not working
Date: Wed, 2 Feb 2011 02:39:20 +0000 (UTC) [thread overview]
Message-ID: <loom.20110202T021600-867@post.gmane.org> (raw)
In-Reply-To: 4D4890C3.3060408@hq.newdream.net
Samuel Just <samuelj <at> hq.newdream.net> writes:
> From the logs, it looks like the osd and mds are failing to bind to
> an address. Perhaps b3 is not a valid host name?
Thanks!
That wasn't it (b3 is valid), but you started me looking at the
networking side of things again (for the nth time) and this time
around I noticed there was no loopback interface on the box. That in
itself was odd, although it didn't immediately spring to mind that the
lack of a loopback would stop ceph working. But I added a loopback
anyway on the basis of "avoid oddness" and that got it all going. I
still don't know why a loopback is required for ceph, but apparently
it is!
FYI, with it working, the osd and mds are still bound to the wildcard
address rather than to a specific address (as they were before the
loopback was installed). Without loopback:
# lsof -n -i | egrep 'COMMAND|cmon|cmds|cosd'
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
cmon 3321 root 5u IPv4 8451 TCP 10.200.63.129:6789 (LISTEN)
cmds 3357 root 4u IPv4 8465 TCP *:6800 (LISTEN)
cmds 3357 root 5u IPv4 10044 TCP
10.200.63.129:59480->10.200.63.129:6789 (SYN_SENT)
cosd 3466 root 3u IPv4 8548 TCP *:6801 (LISTEN)
cosd 3466 root 5u IPv4 8549 TCP *:6802 (LISTEN)
cosd 3466 root 6u IPv4 8550 TCP *:6803 (LISTEN)
cosd 3466 root 13u IPv4 10046 TCP
10.200.63.129:59481->10.200.63.129:6789 (SYN_SENT)
Note that the DEVICE number for the SYN_SENT connections keeps
changing in this situation.
With the loopback:
# lsof -n -i | egrep 'COMMAND|cmon|cmds|cosd'
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
cmon 6633 root 5u IPv4 13277 TCP 10.200.63.129:6789 (LISTEN)
cmon 6633 root 6u IPv4 14353 TCP
10.200.63.129:6789->10.200.63.129:32884 (ESTABLISHED)
cmon 6633 root 7u IPv4 13367 TCP
10.200.63.129:6789->10.200.63.129:32883 (ESTABLISHED)
cmds 6669 root 4u IPv4 13294 TCP *:6800 (LISTEN)
cmds 6669 root 5u IPv4 13366 TCP
10.200.63.129:32883->10.200.63.129:6789 (ESTABLISHED)
cmds 6669 root 10u IPv4 13456 TCP
10.200.63.129:41828->10.200.63.129:6801 (ESTABLISHED)
cosd 6741 root 3u IPv4 14350 TCP *:6801 (LISTEN)
cosd 6741 root 5u IPv4 14351 TCP *:6802 (LISTEN)
cosd 6741 root 6u IPv4 14352 TCP *:6803 (LISTEN)
cosd 6741 root 13u IPv4 13401 TCP
10.200.63.129:32884->10.200.63.129:6789 (ESTABLISHED)
cosd 6741 root 14u IPv4 14467 TCP
10.200.63.129:6801->10.200.63.129:41828 (ESTABLISHED)
Cheers,
Chris.
next prev parent reply other threads:[~2011-02-02 2:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 6:48 Simple test system not working Chris Dunlop
2011-02-01 6:56 ` Chris Dunlop
2011-02-01 23:01 ` Samuel Just
2011-02-02 2:39 ` Chris Dunlop [this message]
[not found] ` <AANLkTinHREewy2QUt8cC33YzaTdS56VENBV6m2-kUuoM@mail.gmail.com>
2011-02-02 2:53 ` Fwd: " Neville Burnell
2011-02-02 5:35 ` Chris Dunlop
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20110202T021600-867@post.gmane.org \
--to=chris@onthe.net.au \
--cc=ceph-devel@vger.kernel.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.