From: Dan Mick <dan.mick@inktank.com>
To: hemant surale <hemant.surale@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Delivery Status Notification (Failure)
Date: Mon, 29 Oct 2012 13:19:48 -0700 [thread overview]
Message-ID: <508EE4E4.7060802@inktank.com> (raw)
In-Reply-To: <CAGfy=6mwAD6A4Z3GXzmMwJnu7W0uPan1m1FYAnRuna9a3rDG=A@mail.gmail.com>
Last time you asked this, I responded (on 18 Oct):
So, clearly something went wrong with the installation step, and this
file was not created. How did you install after building?
On 10/29/2012 02:27 AM, hemant surale wrote:
> Hi Folks ,
>
> I have executed all required steps to build Ceph from source but now
> when I execute "service Ceph start" it shows
>
> ---------------------------------------//Error--------------------------------------------
> root@atish-virtual-machine:/ceph_data# service ceph start
> /etc/init.d/ceph: 37: .: Can't open /usr/lib/ceph/ceph_common.sh
> -------------------------------------------------------------------------------------------
>
>
> Please help me out .
next prev parent reply other threads:[~2012-10-29 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGfy=6=se6CXExQyyA7TrAjUVkGqRwGL=E1wqo4h4_6ORzS-MA@mail.gmail.com>
[not found] ` <f46d0438909985742c04cc3f658c@google.com>
2012-10-18 11:19 ` Delivery Status Notification (Failure) hemant surale
2012-10-29 9:27 ` hemant surale
2012-10-29 20:19 ` Dan Mick [this message]
[not found] ` <CAGfy=6nj9v14JHa1KX4ffYnNCKoXB-dHNeAUqMqZRAE0+oFhnA@mail.gmail.com>
[not found] ` <DBD4A33F-98A2-452B-A854-4DD6D846E0A0@inktank.com>
[not found] ` <CAGfy=6kNDhdPQB4WdYN2adZHxAJtXfySfch3-_PjHSGBWknmKg@mail.gmail.com>
[not found] ` <CAGfy=6mesQn=wGQiXgKDwKd3zjYWNtYdn+xY=StSKgDqiNa9NA@mail.gmail.com>
2012-10-30 9:02 ` Fwd: " hemant surale
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=508EE4E4.7060802@inktank.com \
--to=dan.mick@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=hemant.surale@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox