Re: Upgrade from 1.7 to 2.0 = increased CPU usage

2019-07-18 Thread Lukas Tribus
Hello Elias,


On Wed, 17 Jul 2019 at 17:52, Elias Abacioglu
 wrote:
>
> Ok, I just tried HAProxy 2.0.2.
> I see weird CPU behaviour there too.
> On threaded mode:
> When I restart or reload haproxy it goes between 11-38% idle on core 2 and 3.
> But then after a couple of minutes it goes to using almost 100% of core 2 and 
> 3.

Ok, thanks.

Could you attach strace -tt -p to a process occupying 100% and
provide a few seconds of it’s output (it will be large)?

There is also a similar report on discourse:
https://discourse.haproxy.org/t/2-0-1-cpu-usage-at-near-100-after-upgrade-from-1-5/4065/

I'm CC'ing Willy.


Regards,

Lukas



Re: Random 502's and instant 504's after upgrading

2019-07-18 Thread Christopher Faulet

Le 18/07/2019 à 16:50, Sander Klein a écrit :

On 2019-07-18 09:15, Sander Klein wrote:

Hi,

Last night I tried upgrading from haproxy 1.9.8 to 2.0.2. After
upgrading I get random 502's and random instant 504's when visiting
pages.



Just tested with 'no option http-use-htx' in the defaults section and
then my problems went away. Seems like a bug in HTX. Any info needed for
this one?



Hi,

Could you share your configuration please ?

And if possible, it could be good to check if you have same errors with HTTP/1 
requests.


--
Christopher Faulet



Re: [PATCH] BUG/MINOR: ssl: (no) empty handshake detection for BoringSSL

2019-07-18 Thread Emmanuel Hocdet

Hi,

This patch is an update to follow the Lukas's one.

Only BoringSSL case is addressed, because i test it for BoringSSL.
It could be used by LibreSSL for "dontlognull" to work.

++
Manu




0001-BUG-MINOR-ssl-no-empty-handshake-detection-for-Borin.patch
Description: Binary data


Re: Random 502's and instant 504's after upgrading

2019-07-18 Thread Lukas Tribus
Hello,


On Thu, 18 Jul 2019 at 16:51, Sander Klein  wrote:
>
> On 2019-07-18 09:15, Sander Klein wrote:
> > Hi,
> >
> > Last night I tried upgrading from haproxy 1.9.8 to 2.0.2. After
> > upgrading I get random 502's and random instant 504's when visiting
> > pages.
>
>
> Just tested with 'no option http-use-htx' in the defaults section and
> then my problems went away. Seems like a bug in HTX. Any info needed for
> this one?

Could be related to:
https://github.com/haproxy/haproxy/issues/176

Can you provide the "show errors" output from the admin cli for those
requests, and possible try one of the mentioned workarounds
(http-reuse never or http-server-close)?



Lukas



Re: Random 502's and instant 504's after upgrading

2019-07-18 Thread Sander Klein

On 2019-07-18 09:15, Sander Klein wrote:

Hi,

Last night I tried upgrading from haproxy 1.9.8 to 2.0.2. After
upgrading I get random 502's and random instant 504's when visiting
pages.



Just tested with 'no option http-use-htx' in the defaults section and 
then my problems went away. Seems like a bug in HTX. Any info needed for 
this one?


Sander



0x2E78FBE8.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature


Random 502's and instant 504's after upgrading

2019-07-18 Thread Sander Klein

Hi,

Last night I tried upgrading from haproxy 1.9.8 to 2.0.2. After 
upgrading I get random 502's and random instant 504's when visiting 
pages.


For the 502's I see the following in the log:

Jul 18 08:14:09 HOST haproxy[2003]: xxx:xxx:xxx:xxx:xxx::xxx 
[18/Jul/2019:08:14:09.133] cluster1-in~ cluster1/BACK1 0/0/0/-1/0 502 
1976 - - PH-- 382/129/8/5/0 0/0 {somesite.nl|Mozilla/5.0 
(Win|354|https://somesite.nl/stuff/goes/here/xxx} {} "POST 
/stuff/goes/here/xxx HTTP/2.0"
Jul 18 08:15:08 HOST haproxy[2003]: x.x.x.x:50004 
[18/Jul/2019:08:15:08.712] cluster1-in~ cluster1/BACK2 0/0/0/-1/0 502 
1976 - - PH-- 365/150/5/2/0 0/0 {somesite.nl|Mozilla/5.0 
(Win||https://somesite.nl/other/stuf/here/please/xxx} {} "GET 
/img/uploads/path/somejpeg.jpg HTTP/2.0"


The 504's are another thing, I do not see them logged at all. The only 
things I notice is that they are instant, so no timeout is reached.


Downgrading back to 1.9.8 fixes the problem again. I might try disabling 
htx later today to see what happens.


The backends are NGINX servers which talk plain http/1.1.

Sander

0x2E78FBE8.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature