From: Tommi Virtanen <tommi.virtanen@dreamhost.com>
To: Noah Watkins <jayhawk@cs.ucsc.edu>
Cc: ceph-devel@vger.kernel.org
Subject: Re: vstart -d -n not working in 0.25.1
Date: Thu, 17 Mar 2011 16:54:56 -0700 [thread overview]
Message-ID: <20110317235456.GA23005@dreamer> (raw)
In-Reply-To: <24DF3893-B686-4B01-AA71-BB249BBF5625@cs.ucsc.edu>
On Thu, Mar 17, 2011 at 04:01:13PM -0700, Noah Watkins wrote:
> I am having difficulties getting the standalone "test setup" working
> with 0.25.1, which was working with 0.24. Here is the following
> output from "./vstart -d -n".
>
> The logs don't seem to have anything interesting, and no cmon,cmds,
> or cosd is running after this startup script runs.
...
> ./monmaptool --create --clobber --add a ::1 127.0.1.1 128.114.52.36:6789 --add b ::1 127.0.1.1 128.114.52.36:6790 --add c ::1 127.0.1.1 128.114.52.36:6791 --print /tmp/ceph_monmap.13428
vstart.sh can't handle hosts with IPv6 right now -- in fact, it can't
even handle some IPv4 configurations of /etc/resolv.conf. A simple
test is to run: hostname --ip-address
If it outputs more than one IP address, vstart.sh won't work for you
right now. On this Ubuntu 10.04 box, I get "::1 127.0.1.1 10.0.1.102".
My /etc/hosts is
10.0.1.102 dreamer # Added by NetworkManager
127.0.0.1 localhost.localdomain localhost
::1 dreamer localhost6.localdomain6 localhost6
127.0.1.1 dreamer
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
I don't have a good solution right now.
I'd file a ticket, but the tracker is down currently :(
--
:(){ :|:&};:
next prev parent reply other threads:[~2011-03-17 23:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 23:01 vstart -d -n not working in 0.25.1 Noah Watkins
2011-03-17 23:54 ` Tommi Virtanen [this message]
2011-03-17 23:57 ` Noah Watkins
2011-03-18 0:02 ` Tommi Virtanen
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=20110317235456.GA23005@dreamer \
--to=tommi.virtanen@dreamhost.com \
--cc=ceph-devel@vger.kernel.org \
--cc=jayhawk@cs.ucsc.edu \
/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.