Given that procjoin and procleave are lifecycle log messages, can these be logged in the CPG subsystem at a higher level than DEBUG ?
Issue
- Only the procjoin and procleave messages from the CPG Corosync subsystem needs to be logged as seen below.
# egrep -i "procjoin|procleave" /tmp/c.log
Nov 15 14:26:07 corosync [CPG ] got procjoin message from cluster node 1744939200
Nov 15 14:26:32 corosync [CPG ] got procleave message from cluster node 1744939200
Nov 15 14:26:39 corosync [CPG ] got procjoin message from cluster node 1744939200
Nov 15 14:26:48 corosync [CPG ] got procleave message from cluster node 1744939200
- At present, in order to get these messages in the logs, debugging needs to be enabled which also produces a lot of other messages from CPG system, specifically every multicast request gets logged which is not requied for day to day monitoring.
# tail -10 /tmp/c.log
Nov 16 15:52:12 corosync [CPG ] got mcast request on 0x19cac80
Nov 16 15:52:22 corosync [CPG ] got mcast request on 0x19cac80
Nov 16 15:52:32 corosync [CPG ] got mcast request on 0x19cac80
Nov 16 15:52:42 corosync [CPG ] got mcast request on 0x19cac80
Nov 16 15:52:52 corosync [CPG ] got mcast request on 0x19cac80
Nov 16 15:53:02 corosync [CPG ] got mcast request on 0x19cac80
Nov 16 15:53:12 corosync [CPG ] got mcast request on 0x19cac80
Nov 16 15:53:22 corosync [CPG ] got mcast request on 0x19cac80
Nov 16 15:53:32 corosync [CPG ] got mcast request on 0x19cac80
Nov 16 15:53:42 corosync [CPG ] got mcast request on 0x19cac80
Environment
- Red Hat Enterprise Linux 6
- MRG Messaging
- corosync < 1.4.1-15
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.