All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Mick <dan.mick@inktank.com>
To: Damien Churchill <damoxc@gmail.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: collectd plugin with cuttlefish
Date: Fri, 30 Aug 2013 17:38:44 -0700	[thread overview]
Message-ID: <52213B14.4030604@inktank.com> (raw)
In-Reply-To: <CAFtEh-fCrPCx19BkG-CN7KP=ag3czMbZ=xQuHKOecMsUF2Z36g@mail.gmail.com>

It's a bit surprising that it broke with cuttlefish; something might 
have happened in dumpling, but we wouldn't expect changes in cuttlefish.
It looks like collectd just couldn't talk to the monitor properly.
Maybe look at the mon's log and see what it thinks it saw?

On 08/30/2013 05:04 AM, Damien Churchill wrote:
> Hi,
>
> Has anything changed with the admin socket that would prevent the
> collectd plugin (compiled against 5.3.1 using the patches submitted to
> the collectd ML) from gathering stats? I've recompiled collectd with
> --enable-debug and receive the following output in the log:
>
> ceph_init
> name=mon_ceph1, asok_path=/var/run/ceph/ceph-mon.ceph1.asok
> entering cconn_main_loop(request_type = 0)
> did cconn_prepare(name=mon_ceph1,i=0,st=1)
> cconn_handle_event(name=mon_ceph1,state=1,amt=0,ret=4)
> did cconn_prepare(name=mon_ceph1,i=0,st=2)
> did cconn_prepare(name=mon_ceph1,i=0,st=2)
> ERROR: cconn_main_loop: timed out.
> cconn_main_loop: reached all Ceph daemons :)
> Initialization of plugin `ceph' failed with status -110. Plugin will
> be unloaded.
> plugin_unregister_read: Marked `ceph' for removal.
>
> Thanks in advance!
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

      reply	other threads:[~2013-08-31  0:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30 12:04 collectd plugin with cuttlefish Damien Churchill
2013-08-31  0:38 ` Dan Mick [this message]

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=52213B14.4030604@inktank.com \
    --to=dan.mick@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=damoxc@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 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.