On Wed, Nov 13, 2013 at 8:49 AM, Berant Lemmenes <berant@xxxxxxxxxxxx> wrote:
>
> On Wed, Nov 13, 2013 at 8:05 AM, Alfredo Deza <alfredo.deza@xxxxxxxxxxx>
> wrote:
>>
>>
>> Oh, and I just noticed you did say Ubuntu, so sysvinit should have
>> *not* been enabled at all, this should've been
>> Upstart all along.
>>
>> Again, logs would be super useful! Hopefully you still have those around.
>>
>
> Alfredo,
>
> Attached is the complete ceph.log from all my ceph-deploy interactions.
> Looks like all the ceph_deploy.osd entries indicate upstart was used.
>
> Through the life of this cluster I upgraded to all the dumpling point
> releases, however I didn't do it via ceph-deploy, I used an Ansible playbook
> in order to orchestrate the various steps (setting noout, updating packages,
> restarting services etc...).
>
> My understanding of ceph-deploy though is that it is just executing the same
> apt commands (in my case), that I would be doing via ansible.
If you are just upgrading, you are probably right, there are a few
things ceph-deploy will call, mostly APT.
There are other things that ceph-deploy will do and simplify when
deploying OSDs though.
For example, when calling `ceph-deploy osd prepare` it will check for
the existence of the Keyring and it will create it if it does not
exist at
this path: /var/lib/ceph/bootstrap-osd/{cluster}.keyring
>From your logs, it looks like you have a lot of errors from attempting
to get monitors running and I can't see how/where ceph-deploy can
be causing them. Are those errors known issues for you? Where they
fixed or those are part of the overall issue?
This is just one of the items that caught my attention:
2013-10-29 15:56:03,982 [ceph11][ERROR ] 2013-10-29 15:56:06.303009
7feaafe8e780 -1 unable to find any IP address in networks:
192.168.200.0/24
>
> Thanks,
> Berant
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
