CEPH filesystem development
 help / color / mirror / Atom feed
From: Joe Buck <jbbuck@gmail.com>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Proposed change to vstart.sh
Date: Mon, 22 Oct 2012 09:35:12 -0700	[thread overview]
Message-ID: <508575C0.9080700@gmail.com> (raw)
In-Reply-To: <50856F74.8020001@inktank.com>

Sam,

Here's the last few lines printed when I start vstart.sh

./vstart.sh: 397: ./vstart.sh: btrfs: not found
add osd0 7cf25a23-32dd-4b82-b9d4-d514eb857d02
2012-10-22 09:31:46.788605 7ff87bb4e780 -1 unable to authenticate as 
client.admin
2012-10-22 09:31:46.790370 7ff87bb4e780 -1 ceph_tool_common_init failed.

I'm invoking vstart.sh like so (my version has the patch I sent out this 
morning applied):
./vstart.sh -d -n -l -X

The line in vstart.sh that seems to tank is:

$SUDO $CEPH_ADM osd create $uuid

-Joe Buck

On 10/22/2012 09:08 AM, Sam Lang wrote:
> On 10/22/2012 10:13 AM, Joe Buck wrote:
>> On 10/21/2012 02:35 PM, Sage Weil wrote:
>
>>> Also, we should fix the auth none usage at some point.  :)
>
> I made some changes a while back to fix the auth none problems with 
> vstart 
> (https://github.com/ceph/ceph/commit/0f7c516f3e1f37c5869f8fbff67f53ca0c90568c). 
>  The -x help text inversion was a bug on my part.
>
> Joe what errors do you get with auth none?  I'm able to do vstart.sh 
> -n -l (without the -x/-X changes) successfully.
>
> -sam
>
>>>
>>> sage
>>
>


  parent reply	other threads:[~2012-10-22 16:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-21 21:31 Proposed change to vstart.sh Joe Buck
2012-10-21 21:35 ` Sage Weil
2012-10-22  6:05   ` Dan Mick
2012-10-22 15:13   ` Joe Buck
2012-10-22 16:08     ` Sam Lang
2012-10-22 16:14       ` Yehuda Sadeh
2012-10-22 16:19         ` Sam Lang
2012-10-22 16:28           ` Yehuda Sadeh
2012-10-23 11:46             ` Sam Lang
2012-10-22 16:35       ` Joe Buck [this message]
2012-10-22 16:40         ` Sage Weil
2012-10-23  5:22           ` Dan Mick
2012-10-22 17:54         ` Sam Lang
2012-10-22 18:07           ` Joe Buck

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=508575C0.9080700@gmail.com \
    --to=jbbuck@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox