[Pacemaker] debugging levels
Alan Jones
falancluster at gmail.com
Fri Apr 2 01:13:12 UTC 2010
This worked. Let me know if there is a better way. From crm.h:
#ifdef ALAN_JONES_WANTS_HIS_LOG_MESSAGES
#define do_crm_log_unlikely(level, fmt, args...) do { \
if(__likely(crm_log_level < (level))) { \
continue; \
} else if((level) < LOG_DEBUG_2) { \
cl_log(level, "%s: " fmt, __PRETTY_FUNCTION__ , ##args); \
} else { \
cl_log(LOG_DEBUG, "debug%d: %s: " fmt, \
level-LOG_INFO, __PRETTY_FUNCTION__ , ##args); \
} \
} while(0)
#else
#define do_crm_log_unlikely(level, fmt, args...) do { \
(void)(level); \
cl_log(LOG_INFO, fmt, ##args); \
} while(0)
#endif
On Thu, Apr 1, 2010 at 4:03 PM, Alan Jones <falancluster at gmail.com> wrote:
> Hi,
> I would like to set debugging levels higher than zero with
> pacemaker/corosync.
>
> [root at fc12-a heartbeat]# ./crmd version
> CRM Version: 1.0.5 (ee19d8e83c2a5d45988f1cee36d334a631d84fc7)
> [root at fc12-a heartbeat]# corosync -v
> Corosync Cluster Engine, version '1.1.2' SVN revision '2539'
> Copyright (c) 2006-2009 Red Hat, Inc.
>
> What I would like is to only write log messages to private files and not
> syslog
> and to enable debug log messages from pacemaker, particularly the pengine.
> So far I have corosync writing to its own log file and pacemaker writing to
> both syslog and through ha_logd to ha-log and ha-debug. However, both
> outputs
> are the same.
>
> It seems there are only two configuration options for pacemaker as started
> by
> corosync: use_logd which I've enabled and use_mgmtd which I don't
> understand.
> There is no documentation for the service section of corosync.conf that I
> could
> find, except for lib/ais/plugin.c which has no comments.
>
> - How to I turn off output to syslog by pacemaker?
> - How to I enable all those nice debug prints in pacemaker source to go to
> some file?
>
> Thanks!
> Alan
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100401/799e9b27/attachment-0002.htm>
More information about the Pacemaker
mailing list