From: Owen Synge <osynge@suse.com>
To: Sage Weil <sweil@redhat.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Fedora 22 systemd and rgw
Date: Tue, 04 Aug 2015 14:32:07 +0200 [thread overview]
Message-ID: <55C0B0C7.7050907@suse.com> (raw)
In-Reply-To: <55C0904A.8010902@suse.com>
On 08/04/2015 12:13 PM, Owen Synge wrote:
> On 08/03/2015 09:07 PM, Sage Weil wrote:
>> On Mon, 3 Aug 2015, Owen Synge wrote:
> I will check the rgw.
It is not working due to missing:
/usr/lib/ceph-radosgw/ceph-radosgw-prestart.sh
which is a useful check tool, available in this commit:
https://github.com/SUSE/ceph/commit/92ef2ecfe0c0c0b0df4c9349310f930057202305
I assume this got lost some where earlier, and should be placed in the
systemd directory in my opinion.
and some small permission issues resolved all is working fine.
(core dump on failing to read the key is a bit ugly)
Best regards
Owen
PS for other comments more important than this detail please see earlier
emails in this thread.
next prev parent reply other threads:[~2015-08-04 12:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 19:13 systemd status Sage Weil
2015-07-28 22:16 ` Travis Rhoden
2015-07-29 11:25 ` Alex Elsayed
2015-07-29 12:55 ` Sage Weil
2015-07-29 13:09 ` Wyllys Ingersoll
2015-07-29 14:08 ` Alex Elsayed
2015-07-29 14:19 ` Sage Weil
2015-07-29 14:30 ` Alex Elsayed
2015-07-29 14:53 ` Sage Weil
2015-07-29 15:17 ` Alex Elsayed
2015-07-29 16:50 ` Vasiliy Angapov
2015-07-31 13:29 ` Owen Synge
2015-07-30 12:45 ` Sage Weil
2015-07-30 19:40 ` Robert LeBlanc
2015-08-03 8:53 ` Owen Synge
2015-07-31 8:11 ` Owen Synge
2015-07-31 13:23 ` Owen Synge
2015-08-03 19:01 ` Fedora 22 systemd and ceph-deploy Owen Synge
2015-08-03 19:07 ` Sage Weil
2015-08-04 10:13 ` Owen Synge
2015-08-04 12:32 ` Owen Synge [this message]
2015-08-04 13:07 ` Fedora 22 systemd and rgw Sage Weil
2015-08-04 16:10 ` Owen Synge
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=55C0B0C7.7050907@suse.com \
--to=osynge@suse.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sweil@redhat.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.