Re: No monitor sockets after upgrading to Emperor

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Thu, Nov 14, 2013 at 12:11 PM, Alfredo Deza <alfredo.deza@xxxxxxxxxxx> wrote:

>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?

Those were just false starts learning ceph-deploy as the previous cluster I had deployed was done using mkcephfs on bobtail. I had zero issues associated with using ceph-deploy and getting the cluster going.

The socket issue only became apparent when i started scraping metrics out of them to push to an opentsdb install, and I noticed that on reboot I stopped getting metrics even though the poller and the ceph daemons were running.

I just commented on Peter's thread (didn't mean to hijack it) as I was experiencing what seemed to be a similar 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

[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux