I have tried to install ceph using ceph-deploy but sgdisk seems to
have too many issues so I did a manual install. After mkfs.btrfs on
the disks and journals and mounted them I then tried to start the osds
which failed. The first error was:
#/etc/init.d/ceph start osd.0
/etc/init.d/ceph: osd.0 not
We use ceph-disk without any issues on CentOS7. If you want to do a
manual deployment, verfiy you aren't missing any steps in
http://ceph.com/docs/master/install/manual-deployment/#long-form.
On Tue, Feb 24, 2015 at 5:46 PM, Barclay Jameson
wrote:
> I have tried to install ceph using ceph-deploy
Check firewall rules and selinux. It sometimes is a pain in the ... :)
25 lut 2015 01:46 "Barclay Jameson" napisał(a):
> I have tried to install ceph using ceph-deploy but sgdisk seems to
> have too many issues so I did a manual install. After mkfs.btrfs on
> the disks and journals and mounted th
Also, did you successfully start your monitor(s), and define/create the
OSDs within the Ceph cluster itself?
There are several steps to creating a Ceph cluster manually. I'm unsure if
you have done the steps to actually create and register the OSDs with the
cluster.
- Travis
On Wed, Feb 25, 20
I'm having a similar issue.
I'm following http://ceph.com/docs/master/install/manual-deployment/ to a T.
I have OSDs on the same host deployed with the short-form and they work
fine. I am trying to deploy some more via the long form (because I want
them to appear in a different location in the cr
I think that your problem lies with systemd (even though you are using
SysV syntax, systemd is really doing the work). Systemd does not like
multiple arguments and I think this is why it is failing. There is
supposed to be some work done to get systemd working ok, but I think
it has the limitation
But I already issued that command (back in step 6).
The interesting part is that "ceph-disk activate" apparently does it
correctly. Even after reboot, the services start as they should.
On Wed, Feb 25, 2015 at 3:54 PM, Robert LeBlanc
wrote:
> I think that your problem lies with systemd (even th
Step #6 in http://ceph.com/docs/master/install/manual-deployment/#long-form
only set-ups the file structure for the OSD, it doesn't start the long
running process.
On Wed, Feb 25, 2015 at 2:59 PM, Kyle Hutson wrote:
> But I already issued that command (back in step 6).
>
> The interesting part is
So I issue it twice? e.g.
ceph-osd -i X --mkfs --mkkey
...other commands...
ceph-osd -i X
?
On Wed, Feb 25, 2015 at 4:03 PM, Robert LeBlanc
wrote:
> Step #6 in
> http://ceph.com/docs/master/install/manual-deployment/#long-form
> only set-ups the file structure for the OSD, it doesn't start the
I just tried it, and that does indeed get the OSD to start.
However, it doesn't add it to the appropriate place so it would survive a
reboot. In my case, running 'service ceph status osd.16' still results in
the same line I posted above.
There's still something broken such that 'ceph-disk activat
I am using the long form and have it working. The one thing that I saw was
to change from osd_host to just host. See if that works.
On Feb 25, 2015 5:44 PM, "Kyle Hutson" wrote:
> I just tried it, and that does indeed get the OSD to start.
>
> However, it doesn't add it to the appropriate place
Heres the doc I used to get the info:
http://ceph.com/docs/master/rados/troubleshooting/troubleshooting-osd/
On Feb 25, 2015 5:55 PM, "Thomas Foster" wrote:
> I am using the long form and have it working. The one thing that I saw
> was to change from osd_host to just host. See if that works.
> O
Thank you Thomas. You at least made me look it the right spot. Their
long-form is showing what to do for a mon, not an osd.
At the bottom of step 11, instead of
sudo touch /var/lib/ceph/mon/{cluster-name}-{hostname}/sysvinit
It should read
sudo touch /var/lib/ceph/osd/{cluster-name}-{osd-num}/sys
On 02/26/2015 09:05 AM, Kyle Hutson wrote:
Thank you Thomas. You at least made me look it the right spot. Their long-form
is showing what to do for a mon, not an osd.
At the bottom of step 11, instead of
sudo touch /var/lib/ceph/mon/{cluster-name}-{hostname}/sysvinit
It should read
sudo touch
Just did it. Thanks for suggesting it.
On Wed, Feb 25, 2015 at 5:59 PM, Brad Hubbard wrote:
> On 02/26/2015 09:05 AM, Kyle Hutson wrote:
>
>> Thank you Thomas. You at least made me look it the right spot. Their
>> long-form is showing what to do for a mon, not an osd.
>>
>> At the bottom of step
On 02/26/2015 03:24 PM, Kyle Hutson wrote:
Just did it. Thanks for suggesting it.
No, definitely thank you. Much appreciated.
On Wed, Feb 25, 2015 at 5:59 PM, Brad Hubbard mailto:bhubb...@redhat.com>> wrote:
On 02/26/2015 09:05 AM, Kyle Hutson wrote:
Thank you Thomas. You at le
16 matches
Mail list logo
