[Pacemaker] how to enable verbose logging for failed

[Andrew Beekhof]

On Sat, May 12, 2012 at 11:41 PM, Igor Zinovik <zinovik.igor at gmail.com> wrote:
>  Hello.
>
> How can i increase verbosity level for resource that fails to start:
> # egrep -ei '(warn|error)' /var/log/pacemaker.log
> May 12 17:25:12 ldap2 lrmd: [6279]: WARN: Core dumps could be lost if
> multiple dumps occur.
> May 12 17:25:12 ldap2 lrmd: [6279]: WARN: Consider setting non-default
> value in /proc/sys/kernel/core_pattern (or equivalent) for maximum
> supportability
> May 12 17:25:12 ldap2 lrmd: [6279]: WARN: Consider setting
> /proc/sys/kernel/core_uses_pid (or equivalent) to 1 for maximum
> supportability
> May 12 17:25:13 ldap2 corosync[6270]:  [pcmk  ] ERROR:
> pcmk_wait_dispatch: Child process mgmtd exited (pid=6283, rc=100)
> May 12 17:28:02 ldap2 crmd: [6282]: info: process_lrm_event: LRM
> operation slapd_mirrormode_monitor_10000 (call=5, rc=1, cib-update=14,
> confirmed=false) unknown error
> May 12 17:28:04 ldap2 crmd: [6282]: info: process_lrm_event: LRM
> operation slapd_mirrormode_monitor_10000 (call=8, rc=1, cib-update=17,
> confirmed=false) unknown error
> May 12 17:28:05 ldap2 crmd: [6282]: info: process_lrm_event: LRM
> operation slapd_mirrormode_monitor_10000 (call=11, rc=1,
> cib-update=20, confirmed=false) unknown error
>
> In slapd log i do not see any messages which shows the culprit of failure.

Is it producing any? Did you grep for "slapd" too?

>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org