* ceph admin command: debuggging
@ 2013-08-08 14:04 Andreas Bluemle
2013-08-08 19:32 ` Dan Mick
2013-08-08 22:09 ` Sage Weil
0 siblings, 2 replies; 4+ messages in thread
From: Andreas Bluemle @ 2013-08-08 14:04 UTC (permalink / raw)
To: Ceph Development
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?
Thanks for any help
Andreas Bluemle
--
Andreas Bluemle mailto:Andreas.Bluemle@itxperts.de
ITXperts GmbH http://www.itxperts.de
Balanstrasse 73, Geb. 08 Phone: (+49) 89 89044917
D-81541 Muenchen (Germany) Fax: (+49) 89 89044910
Company details: http://www.itxperts.de/imprint.htm
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ceph admin command: debuggging
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
1 sibling, 0 replies; 4+ messages in thread
From: Dan Mick @ 2013-08-08 19:32 UTC (permalink / raw)
To: Andreas Bluemle; +Cc: Ceph Development
There are a number of subsystems that the clients use, so a number of
knobs that matter. The "logging/authentication name" (the type.id
name), by default, is 'client.admin'. Some of the relevant logging
knobs are ms/monc; of course there are usually effects caused by the
daemons too, so the mon/osd logs will contain things triggered by the
client.
What sort of things are you looking for specifically?
On 08/08/2013 07:04 AM, 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?
>
>
> Thanks for any help
>
> Andreas Bluemle
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ceph admin command: debuggging
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
1 sibling, 1 reply; 4+ messages in thread
From: Sage Weil @ 2013-08-08 22:09 UTC (permalink / raw)
To: Andreas Bluemle; +Cc: Ceph Development
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)
sage
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ceph admin command: debuggging
2013-08-08 22:09 ` Sage Weil
@ 2013-08-12 5:21 ` Andreas Bluemle
0 siblings, 0 replies; 4+ messages in thread
From: Andreas Bluemle @ 2013-08-12 5:21 UTC (permalink / raw)
To: Sage Weil; +Cc: Ceph Development
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2013-08-12 5:21 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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.