> On 5 Nov 2019, at 11:30, Frederic Lecaille <flecai...@haproxy.com> wrote:
>
> On 11/5/19 11:06 AM, Frederic Lecaille wrote:
>> On 11/4/19 1:52 PM, Willy Tarreau wrote:
>>> Hi Yves,
>>>
>>> On Mon, Nov 04, 2019 at 10:47:23AM +0100, Yves Lafon wrote:
>>>> Hi,
>>>> Trying to debug why some replications are stuck between peers, I was
>>>> wondering if it was possible to have low-level logging of connections or at
>>>> least TCP states in the peers section to figure out what is happening.
>>>> There are some information using 'show peers', but it will lack some
>>>> information (like if there was multiple reconnect attempts in a row).
>>>
>>> Now that our peers sections are full-featured proxies, I think it should
>>> not be hard to implement the "log" directive there at least to enable
>>> logging of incoming connections. It's probably as simple as just setting
>>> the log_wait field to non-zero. And I agree that peers remain one of the
>>> least verbose area of the code, yet are responsible for some long head
>>> scratching :-/
>>>
>>> Willy
>>>
>> Hi,
>> Here is a patch to support "log" directive in "peers" section.
>> I hope this will help.
>> Fred.
>
> I have missed the case where the listener of the "peers" section is declared
> after "log" lines. In such case ->peers_fe is NULL when entering the "log"
> line parser.
>
> So, this last patch is better.
>
> Fred.
> <0001-MINOR-peers-Add-log-directive-to-peers-section.patch>
Thanks, I’ll try this.
--
Baroula que barouleras, au tiéu toujou t'entourneras.
~~Yves
