# Peers section logging

**URL:** <https://discourse.haproxy.org/t/peers-section-logging/6114>\
**Category:** Help!\
**Created:** [January 15, 2021, 10:49pm UTC](https://discourse.haproxy.org/t/peers-section-logging/6114 "2021-01-15T22:49:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pawelgawel](https://avatars.discourse-cdn.com/v4/letter/p/779978/32.png) [@pawelgawel](https://discourse.haproxy.org/u/pawelgawel)\
**Post date:** [January 15, 2021, 10:49pm UTC](https://discourse.haproxy.org/t/peers-section-logging/6114/1 "2021-01-15T22:49:49Z")

</div>

Hi!

I’ve got a weird problem with haproxy peering. Everything is working fine, haproxy instances are syncing stick tables between them correctly up until some point where it stops completely and the `proto_err` counter starts to go up. There’s not a single error pushed to the logs. Is there a way to get any logs about what’s going on with the haproxy peering?

Here’s partial output from the peers state:

```auto
0x55939dff3380: [12/Dec/2020:09:24:58] id=mypeers state=0 flags=0x3 resync_timeout=22d7h task_calls=1093943
  0x55939dff92f0: id=haproxy-1(remote) addr=X:1024 status=ESTA reconnect=4s confirm=0 tx_hbt=773183 rx_hbt=771493 no_hbt=18 new_conn=10136 proto_err=4395
        flags=0x20000000 appctx:0x7ffb4801fea0 st0=7 st1=0 task_calls=2186 state=EST
        last_local_table:0x55939e007260 id=jitsi-meet local_id=1 remote_id=1
        shared tables:
          0x55939e007260 local_id=1 remote_id=1 flags=0x0 remote_data=0x80001
              last_acked=0 last_pushed=46352 last_get=0 teaching_origin=46269 update=46352
              table:0x55939dffcc20 id=jitsi-meet update=46352 localupdate=46352 commitupdate=46352 syncing=0

```

---

<div class="post-metadata">

**Author:** ![lukastribus](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lukastribus](https://discourse.haproxy.org/u/lukastribus)\
**Post date:** [January 15, 2021, 11:41pm UTC](https://discourse.haproxy.org/t/peers-section-logging/6114/2 "2021-01-15T23:41:59Z")

</div>

Please file a bug at:

> **[haproxy/haproxy](https://github.com/haproxy/haproxy/issues)**
>
> s

---

<div class="post-metadata">

**Author:** ![pawelgawel](https://avatars.discourse-cdn.com/v4/letter/p/779978/32.png) [@pawelgawel](https://discourse.haproxy.org/u/pawelgawel)\
**Post date:** [January 19, 2021, 7:20pm UTC](https://discourse.haproxy.org/t/peers-section-logging/6114/3 "2021-01-19T19:20:35Z")

</div>

@lukastribus I will, but we have just upgraded to 2.3.0 and we need to have a way for monitoring the protocol errors or the peering state in general. It seems that it’s possible to get trace logs out of the peers module:

> <https://github.com/haproxy/haproxy/blob/81d7092dbd25db04cc72d2dca77647d548342256/src/peers.c#L2714>

Does anyone know how to enable tracing for the peers module? When I execute “show trace” it doesn’t list peers as one fo the trace sources:

```auto
root@haproxy-1:/# echo "show trace" | socat stdio UNIX-CONNECT:/var/run/hapee-lb.sock
Supported trace sources and states (.=stopped, w=waiting, R=running) :
 [.] h2 -> none [drp 0] [HTTP/2 multiplexer]
 [.] fcgi -> none [drp 0] [FastCGI multiplexer]
 [.] stream -> none [drp 0] [Applicative stream]
 [.] h1 -> none [drp 0] [HTTP/1 multiplexer]

```