All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Willem Jan Withagen <wjw@digiware.nl>,
	Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Running src/ceph generates python error
Date: Fri, 19 Feb 2016 11:20:41 +0700	[thread overview]
Message-ID: <56C69819.5000809@dachary.org> (raw)
In-Reply-To: <56C66791.8040005@digiware.nl>

Hi,

I suspect this is something you changed in your branch. Is there a way to compare your branch with the current master ?

Cheers

On 19/02/2016 07:53, Willem Jan Withagen wrote:
> On 18-2-2016 23:05, Willem Jan Withagen wrote:
>> I'm trying to run
> 
> I was not quite complex in my message:
> Running:  test/erasure-code/test-erasure-code.sh
> 
> And I can get it actually working when I comment out the line:
> ../qa/workunits/ceph-helpers.sh: line 547
>     # ceph_args+=" --plugin-dir=.libs"
> 
> But the error seems to be because of an error in the python script
> called then refuses the about --plugin-dir option
> 
> --WjW
> 
>> And it terminates with:
>> ======
>> .......
>> .......
>> ../qa/workunits/ceph-helpers.sh:555: activate_osd:  mkdir -p
>> testdir/test-erasure-code/0
>> ../qa/workunits/ceph-helpers.sh:556: activate_osd:
>> CEPH_ARGS='--fsid=d9e9b487-d5e0-11e5-be15-1c6f6582ec12
>> --auth-supported=none -
>> -mon-host=127.0.0.1:7101  --osd-backfill-full-ratio=.99
>> --osd-failsafe-full-ratio=.99 --osd-journal-size=100 --osd-scrub-load-thre
>> shold=2000 --osd-data=testdir/test-erasure-code/0 --chdir=
>> --erasure-code-dir=.libs --plugin-dir=.libs --osd-class-dir=.libs --run
>> -dir=testdir/test-erasure-code --debug-osd=20
>> --log-file=testdir/test-erasure-code/$name.log
>> --pid-file=testdir/test-erasure-code/
>> $name.pid  '
>> ../qa/workunits/ceph-helpers.sh:556: activate_osd:  ceph-disk
>> --statedir=testdir/test-erasure-code --sysconfdir=testdir/test-erasu
>> re-code --prepend-to-path= activate --mark-init=none
>> testdir/test-erasure-code/0
>> ceph-disk: Error: ceph osd create failed: Command './ceph' returned
>> non-zero exit status 22: --plugin-dir=.libs not valid:  --plug
>> in-dir=.libs doesn't represent an int
>> Invalid command:  unused arguments: [u'--plugin-dir=.libs']
>> osd create {<uuid>} {<int[0-]>} :  create new osd (with optional UUID
>> and ID)
>> Error EINVAL: invalid command
>>
>> ======
>>
>> So it seems it does not like all the values that are put in the
>> ENV{CEPH_ARGS}.
>>
>> Is this just my problem?
>> And if so, what am I doing wrong?
> 
> --
> 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
> 

-- 
Loïc Dachary, Artisan Logiciel Libre
--
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

  reply	other threads:[~2016-02-19  4:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-18 22:05 Running src/ceph generates python error Willem Jan Withagen
2016-02-19  0:53 ` Willem Jan Withagen
2016-02-19  4:20   ` Loic Dachary [this message]
2016-02-19  7:22     ` Willem Jan Withagen

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=56C69819.5000809@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=wjw@digiware.nl \
    /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.