Hi Kai,
On Wed, Feb 7, 2018 at 2:45 AM, Kai Timmer wrote:
> Hi,
> sorry I totally forgot them. Here are some logs from a time where
> everything was fine:
> Jan 31 00:59:57 haproxy01.prod haproxy[53367]: x.x.x.x:48861
> [31/Jan/2018:00:59:57.728] https-in~ eyo.backend/eyobackend01 0/0/1/33/34
>
John,
Am 06.02.2018 um 17:20 schrieb John Cherouvim:
> suppose that the haproxy backend component must then start 3 connections
> to send the requests to apache. Are these connections shown in group #2
> or #3? And if that is either group #2 or #3, what is the other group
> supposed to be doing?
>
I'm trying to understand the output of netstat when haproxy is handling
requests waiting for the backend to finish processing. My setup is a VM
with LAN IP 192.168.10.50 hosting one haproxy and one apache httpd instance:
- apache httpd is listening on 127.0.0.1:12345 (not accessible from
outside
Hi,
sorry I totally forgot them. Here are some logs from a time where
everything was fine:
Jan 31 00:59:57 haproxy01.prod haproxy[53367]: x.x.x.x:48861
[31/Jan/2018:00:59:57.728] https-in~ eyo.backend/eyobackend01 0/0/1/33/34
304 170 - - 514/514/0/0/0 0/0 "GET /api/menu;wesessid=xxx HTTP/1.1"
On Mon, Feb 05, 2018 at 03:22:58PM -0800, Bryan Talbot wrote:
> Bisecting the 1.9 / master branch shows the build break (on OSX) with
>
> abeaff2d543fded7ffc14dd908d673c59d725155 is the first bad commit
> commit abeaff2d543fded7ffc14dd908d673c59d725155
> Author: Willy Tarreau
> Date: Mon Feb 5
5 matches
Mail list logo