From: Andreas Bluemle <andreas.bluemle@itxperts.de>
To: Sage Weil <sage@inktank.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: ceph admin command: debuggging
Date: Mon, 12 Aug 2013 07:21:28 +0200 [thread overview]
Message-ID: <20130812072128.7a0bab97@andylap> (raw)
In-Reply-To: <alpine.DEB.2.00.1308081508360.986@cobra.newdream.net>
Hi Sage,
On Thu, 8 Aug 2013 15:09:27 -0700 (PDT)
Sage Weil <sage@inktank.com> wrote:
> On Thu, 8 Aug 2013, Andreas Bluemle wrote:
> > Hi,
> >
> > maybe this is the wrong list - but I am looking for
> > logging support for the /usr/bin/ceph adminstration
> > comamand.
> >
> > This is build from the same source as the ceph daemons are.
> >
> > For the daemons, logging is controlled for the different
> > comoponents of a daemon on behalf of configuration file
> > directives (e.g. "debug ms" for the message I/O).
> >
> > Can this be applied to the /usr/bin/ceph command, too?
> > And where would the log file go?
>
> You are probably looking for:
>
> --log-to-stderr (make log output go to stderr)
> --log-file <filename>
>
> and you can make some noise with
>
> --debug-ms 1
> --debug-monc 10
>
> (for example)
>
Thanks; I'll give that a try.
Andreas Bluemle
> sage
> --
> 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
>
>
--
Andreas Bluemle mailto:Andreas.Bluemle@itxperts.de
Heinrich Boell Strasse 88 Phone: (+49) 89 4317582
D-81829 Muenchen (Germany) Mobil: (+49) 177 522 0151
prev parent reply other threads:[~2013-08-12 5:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 14:04 ceph admin command: debuggging Andreas Bluemle
2013-08-08 19:32 ` Dan Mick
2013-08-08 22:09 ` Sage Weil
2013-08-12 5:21 ` Andreas Bluemle [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=20130812072128.7a0bab97@andylap \
--to=andreas.bluemle@itxperts.de \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@inktank.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox