# Appropriate debug logging switch to enable to log events that keep Message spools in HA in sync

**URL:** <https://community.solace.com/t/appropriate-debug-logging-switch-to-enable-to-log-events-that-keep-message-spools-in-ha-in-sync/188>\
**Category:** Solace Event Broker\
**Tags:** logs\
**Created:** [February 19, 2020, 9:17pm UTC](https://community.solace.com/t/appropriate-debug-logging-switch-to-enable-to-log-events-that-keep-message-spools-in-ha-in-sync/188 "2020-02-19T21:17:26Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![rdesoju](https://avatars.discourse-cdn.com/v4/letter/r/a4c791/32.png) [@rdesoju](https://community.solace.com/u/rdesoju)\
**Post date:** [February 19, 2020, 9:17pm UTC](https://community.solace.com/t/appropriate-debug-logging-switch-to-enable-to-log-events-that-keep-message-spools-in-ha-in-sync/188/1 "2020-02-19T21:17:26Z")

</div>

Hi,  
I am looking for particular DEBUG logging switches that we can use to see the critical events that are exchanged between Primary, Standby and Monitoring node that keep Message Spools in Sync. And, events that detect message spools out of sync. Also, events that are initiated when monitoring node plays a role in leader election.

I already tried with REDUNDANCY, AD\_REDUN, MSGBUS, MATELINK etc.

Could someone please suggest the appropriate DEBUG logging switches?

Thanks,  
Raghu

---

<div class="post-metadata">

**Author:** ![marc](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/marc/32/2191_2.png) [@marc](https://community.solace.com/u/marc)\
**Post date:** [February 19, 2020, 9:59pm UTC](https://community.solace.com/t/appropriate-debug-logging-switch-to-enable-to-log-events-that-keep-message-spools-in-ha-in-sync/188/2 "2020-02-19T21:59:42Z")

</div>

Hi @rdesoju,  
A list of events can be found here: [SolOS-TR Message Bus Management Syslog Events](https://docs.solace.com/Solace-PubSub-Event-Reference/event_ref_boiler.html)  
From what you’re requesting I would start by looking at the events under SYSTEM → SYSTEM\_AD and SYSTEM → SYSTEM\_HA. For example I think you might be interested in `SYSTEM_HA_REDUN_GROUP_NODE_JOINED`

I would also recommend you take a look at events under VPN → VPN\_AD so you’re aware of message spool, endpoint usage, etc. at the individual vpn level.

Hope that helps!  
-Marc

---

<div class="post-metadata">

**Author:** ![TomF](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/tomf/32/1749_2.png) [@TomF](https://community.solace.com/u/TomF)\
**Post date:** [February 20, 2020, 10:31am UTC](https://community.solace.com/t/appropriate-debug-logging-switch-to-enable-to-log-events-that-keep-message-spools-in-ha-in-sync/188/3 "2020-02-20T10:31:06Z")

</div>

HA going out of sync isn’t a DEBUG level event and if you’re seeing it, it’s time to root cause it. It’s important to note the “leader” isn’t elected - this is a configuration option (primary) with the backup becoming active only if contact is lost with the primary. The redundancy and system\_ha events will tell you all about the sequence of events that causes this to happen, for instance the HA links going down due to a network problem, the primary being declared unreachable and the backup activating.

---

<div class="post-metadata">

**Author:** ![rdesoju](https://avatars.discourse-cdn.com/v4/letter/r/a4c791/32.png) [@rdesoju](https://community.solace.com/u/rdesoju)\
**Post date:** [February 20, 2020, 1:21pm UTC](https://community.solace.com/t/appropriate-debug-logging-switch-to-enable-to-log-events-that-keep-message-spools-in-ha-in-sync/188/4 "2020-02-20T13:21:16Z")

</div>

@TomF When the primary loses the contact, does backup become active as soon as it detects primary is not reachable? or does it wait for confirmation of Monitoring node in order to assert primary is truly not reachable?

---

<div class="post-metadata">

**Author:** ![TomF](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/tomf/32/1749_2.png) [@TomF](https://community.solace.com/u/TomF)\
**Post date:** [February 24, 2020, 4:39pm UTC](https://community.solace.com/t/appropriate-debug-logging-switch-to-enable-to-log-events-that-keep-message-spools-in-ha-in-sync/188/5 "2020-02-24T16:39:45Z")

</div>

@rdesoju The backup waits for confirmation from the monitor that the monitor cannot see the primary. The backup also checks it can’t see the primary. Only if both are true can the backup take activity.

In this case, the primary cannot see the monitor and it cannot see the backup. Since the backup is free to take activity, the primary now knows it must give up activity.

---

<div class="post-metadata">

**Author:** ![rdesoju](https://avatars.discourse-cdn.com/v4/letter/r/a4c791/32.png) [@rdesoju](https://community.solace.com/u/rdesoju)\
**Post date:** [February 24, 2020, 5:22pm UTC](https://community.solace.com/t/appropriate-debug-logging-switch-to-enable-to-log-events-that-keep-message-spools-in-ha-in-sync/188/6 "2020-02-24T17:22:47Z")

</div>

@TomF , Thanks for the clarification.
