Dear Willy,
Thank you for your prompt guidance. Result of your insights: SUCCESS in
loading stats and other pages in both the use cases listed below:
1). Removed mailers section in 1.8.0.
2). Compiled 1.8-commit 8f42b19 ("BUG/MEDIUM: tcp-check: Don't lock the
server in tcpcheck_main")
Hope the verification helps other users and companies that contribute to the
betterment of our economy and society.
Just to expand our understanding for the future, did you nail the issue from
multi-character process state "Rs", i.e., "runnable on queue""is a session
leader"?
Hats off to you for starting this project. HAProxy has empowered us to
contribute. Should you like to see the impact of HAProxy's indirect
contribution to common global denizens, please take a look at what HAProxy
enables in remote disadvantaged areas:
http://www.coscend.com/Anchor/SSF_Tour/RMCC_Tour/Overview/CoscendCC_Telemedi
cine_anchor.html
Dear Christopher,
Thank you for this timely commit 8f42b19 ("BUG/MEDIUM: tcp-check: Don't lock
the server in tcpcheck_main").
Sincerely,
Hemant K. Sabat
Coscend Communications Solutions
<http://www.coscend.com/> www.Coscend.com
------------------------------------------------------------------
Real-time, Interactive Video Collaboration, Tele-healthcare, Tele-education,
Telepresence Services, on the fly.
------------------------------------------------------------------
CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail
Messages from Coscend Communications Solutions' posted at:
<http://www.Coscend.com/Anchor/Common/Terms_and_Conditions.html>
http://www.Coscend.com/Anchor/Common/Terms_and_Conditions.html
-----Original Message-----
From: Willy Tarreau [mailto:w...@1wt.eu]
Sent: Tuesday, November 28, 2017 12:25 PM
To: Coscend@HAProxy <haproxy.insig...@coscend.com>
Cc: haproxy@formilux.org
Subject: Re: Does HAProxy 1.8.0 need new param vs 1.7.9
Hi Hemant,
On Tue, Nov 28, 2017 at 12:15:32PM -0600, Coscend@HAProxy wrote:
> Thank you for giving time after a large 1.8.0 release to provide us
> vectors on testing HAProxy work mode. This community's intensity and
> laser focus are a standout. Below is all the information you asked us
> to look at. By any chance, was there any critical change between
> 1.8-dev3 and 1.8-rc series/1.8.0?
Sure, a lot! Too many to enumerate in fact.
> New checks: Loads stats page and accesses all backends
>
> SUCCESS: 1.8-dev0/dev1/dev2/dev3
> FAILS: 1.8-rc1/rc2rc3/rc4 and 1.8.0
>
> Browser message:
>
> This site can't be reached
>
> coscend.com took too long to respond.
Ah OK so it's not a "connection refused" as I thought it was, but the fact
that it apparently hangs. That's a different case. I suspect the process
quickly goes up in a loop at 100% CPU due to a bug. There has been a locking
bug on the mailers section causing this, would you happen to have one such
setting in your config ?
> (1) check if the process is still present (ps aux)
>
> root 2801 0.0 0.1 74928 11560 ? S 11:28 0:00
> /usr/local/sbin/haproxy -Ws -V -C /usr/local/haproxy-1.8.0/conf -f
> /usr/local/haproxy-1.8.0/conf -f <path to configuration files> -D -p
> /var/run/haproxy.pid
>
> haproxy 2802 99.5 0.1 75620 12408 ? Rs 11:28 10:50
^^^^^
Bingo, spinning process!
Thanks for all the elements. If you're having a "mailers" section, then the
next nighly snapshot will contain the fix, or you can pick it yourself, it's
commit 8f42b19 ("BUG/MEDIUM: tcp-check: Don't lock the server in
tcpcheck_main").
If you don't have such a section, that's embarrassing, it means there is
another locking bug. In this case I'll ask you for more info off-list.
Regards,
Willy
---
This email has been checked for viruses by AVG.
http://www.avg.com
