From: Samuel Just <samuelj@hq.newdream.net>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Simple test system not working
Date: Tue, 01 Feb 2011 15:01:23 -0800 [thread overview]
Message-ID: <4D4890C3.3060408@hq.newdream.net> (raw)
In-Reply-To: <loom.20110201T072445-567@post.gmane.org>
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?
-Sam
On 01/31/2011 10:48 PM, Chris Dunlop wrote:
> G'day,
>
> I'm just starting with ceph and am having trouble getting a test ceph
> installation going on debian lenny with a self-compiled 2.6.37. Ceph
> itself is latest unstable (73e76723) compiled using dpkg-buildpackage.
> The mon, mds and osd are all on the same machine. The ceph base /data
> directory is ext2 mounted with user_xattr. The ceph filesystem is
> created using the attached ceph.conf and:
>
> /sbin/mkcephfs -v -c /etc/ceph/ceph.conf --allhosts --mkbtrfs -k
> /etc/ceph/keyring.bin
>
> Once ceph has been started, trying a mount on a (separate) client
> machine (2.6.37 kernel) hangs before eventually giving an error:
>
> # mount -t ceph b3:/ /mnt
> mount error 5 = Input/output error
>
> On the server side, it seems that the cmon isn't accepting connections
> from the mds or osd. E.g. repeated instances of this in the osd log,
> and similar "mark_down"s in the mds log:
>
> 2011-02-01 17:18:47.463897 4a254950 -- 0.0.0.0:6801/7854 mark_down
> 10.200.63.129:6789/0 -- 0xca8a00
> 2011-02-01 17:18:47.463924 4a254950 -- 0.0.0.0:6801/7854 --> mon0
> 10.200.63.129:6789/0 -- auth(proto 0 26 bytes) v1 -- ?+0 0xcd9800
>
> The mon log (amongst a whole bunch of other stuff) repeats:
>
> 2011-02-01 17:18:51.445785 42c73950 mon.0@0(leader).mds e1 e1: 0/0/1 up
> 2011-02-01 17:18:51.445790 42c73950 mon.0@0(leader).osd e1 e1: 0 osds: 0 up, 0 in
>
> The attached logs.zip has the full logs from one attempted start.
>
> Is there something obvious I'm doing wrong?
>
> Thanks for any assistance!
>
> Chris
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-02-01 23:02 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 [this message]
2011-02-02 2:39 ` Chris Dunlop
[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=4D4890C3.3060408@hq.newdream.net \
--to=samuelj@hq.newdream.net \
--cc=ceph-devel@vger.kernel.org \
--cc=samuel.just@dreamhost.com \
/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.