All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wido den Hollander <wido@widodh.nl>
To: Sage Weil <sage@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: bobtail release candidates
Date: Mon, 26 Nov 2012 21:25:26 +0800	[thread overview]
Message-ID: <50B36DC6.6000308@widodh.nl> (raw)
In-Reply-To: <alpine.DEB.2.00.1211250953400.23552@cobra.newdream.net>

Hi,

On 11/26/2012 01:57 AM, Sage Weil wrote:
> Hi all,
>
> There are automatic builds of the prerelease bobtail code available under
> the 'next' branch.
>
> For debs,
> 	http://ceph.com/docs/master/install/debian/#add-development-testing-packages
>
> For example, for Ubuntu 12.04 precise,
> 	http://gitbuilder.ceph.com/ceph-deb-precise-x86_64-basic/ref/next/
>
> And RPMs for el6,
> 	http://gitbuilder.ceph.com/ceph-rpm-centos6-x86_64-basic/ref/next/RPMS/x86_64/
>
> Any testing and early feedback is greatly appreciated.
>

I just gave it a try on a small setup I'm toying with and noticed this 
after the package upgrade:

[599557.873110] init: /etc/init/ceph-mds.conf:9: Expected token
[599557.880938] init: /etc/init/ceph-osd.conf:9: Expected token
[599557.900269] init: /etc/init/ceph-mon.conf:9: Expected token

I'm not so familiar with upstart, but line 9 contains:

limit nofile 8192

I also got this message when starting my OSDs:

"No osd devs defined!"

I indeed haven't defined any devs, I've mounted the drives in the fstab.

Should I change this, or?

Wido


> Thanks!
> sage
> --
> 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:[~2012-11-26 13:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-25 17:57 bobtail release candidates Sage Weil
2012-11-26 13:25 ` Wido den Hollander [this message]
2012-11-26 16:22   ` Sage Weil
2012-11-26 13:47 ` Wido den Hollander
2012-11-26 13:59   ` Joao Eduardo Luis
2012-11-26 14:26   ` Sam Lang
2012-11-26 14:36     ` Wido den Hollander
2012-11-26 15:01       ` Sam Lang
2012-11-26 17:35         ` Dan Mick

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=50B36DC6.6000308@widodh.nl \
    --to=wido@widodh.nl \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sage@inktank.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.