-archive.com/haproxy@formilux.org/msg31345.html
), but i don't think we have defined the perfect way to do it yet..
So that part of the question still stands ;) .. Whats the best way to
skip tests that are not applicable?
Regards,
PiBa-NL (Pieter)
Hi Frederic,
Op 1-10-2018 om 16:19 schreef Frederic Lecaille:
On 09/11/2018 04:51 PM, PiBa-NL wrote:
Hi List,
I was wondering how to best run the reg-tests that are 'valid' for
FreeBSD.
There are a 2 tests that use abns@ sockets, which seem not available
on FreeBSD.
Also 1 test is failing
Hi Willy,
Op 30-9-2018 om 20:38 schreef Willy Tarreau:
On Sun, Sep 30, 2018 at 08:22:23PM +0200, Willy Tarreau wrote:
On Sun, Sep 30, 2018 at 07:59:34PM +0200, PiBa-NL wrote:
Indeed it works with 1.8, so in that regard i 'think' the test itself is
correct.. Also when disabling threads
Hi Willy,
Op 30-9-2018 om 7:46 schreef Willy Tarreau:
Hi Pieter,
On Sun, Sep 30, 2018 at 12:05:14AM +0200, PiBa-NL wrote:
Hi Willy,
I thought lets give those reg-test another try :) as its easy to run and
dev3 just came out.
All tests pass on my FreeBSD system, except this one, new reg-test
for
the wrong reason.?.
Hope that makes some sense in my thought process :).
Regards,
PiBa-NL (Pieter)
|CumReq: 65
h1 0.0 CLI expect failed ~ "CumConns: 41"
If my 'expect' is correct, would the patch be suitable for inclusion
with the other reg-tests this way?
If you want to rename loadtest, to heavytest, or any other tweaks please
feel free to do so.
Regards,
PiBa-NL (Pieter
of the email, thanks for your elaborate response :).
Regards,
PiBa-NL (Pieter)
/
with more or less the same likelihood of catching yet unknown issues..?
Looking forward to reactions :) .
Thanks and regards,
PiBa-NL (Pieter)
top 0.0 extmacro def pwd=/usr/ports/net/haproxy-devel
top 0.0 extmacro def localhost=127.0.0.1
top 0.0 extmacro def bad_bac
on
FreeBSD, adding a 'nokqueue' on 1.8.13 makes it succeed though..).
I think it might be a good and reproducible test to run.?
Or does it need more tweaking? Thoughts appreciated :).
Regards,
PiBa-NL (Pieter)
From 4b1af997e796e1bb2098c5f66ac24690841c72e8 Mon Sep 17 00:00:00 2001
From: PiBa-NL
failed ~ " - 33 -" << The port change not
being picked up is a 'known bug' afaik.
Am i writing the test in a wrong way? Should i wait/lock/check something
after some steps and if so how?
Also its taking like a second or more to complete. is there a way to
make it faster, witho
tion reset by peer)
MEDIUM: connections/mux: Add a recv and a send+recv... 4cf7fb OK
Did something go astray?
p.s. should reg-tests maybe get run before the -dev releases get tagged?
(or is that already done, and this could be a FreeBSD specific issue and
as such not have been spotted?)
Regards
build to take into my production system. If
some tests fail by design (on this platform), it takes more
administration to figure out if that was okay or not.
Please advice :)
Regards,
PiBa-NL (Pieter)
From 89a5fd48c11dba6a30f468e86e5a7d4bdab6b986 Mon Sep 17 00:00:00 2001
From: PiBa-NL
Date
made the patch. Only
thing i provided was a 'reg-test' and some gdb traces..
Anyhow its fixed now, that's the important part ;)
Regards,
PiBa-NL (Pieter)
Subject: [PATCH] BUG/MAJOR: thread: lua: Wrong SSL context initialization.
When calling ->prepare_srv() callback for SSL server which
depends on global "nbthread" value, this latter was not already parsed,
so equal to 1 default value. This lead to bad memory accesses.
Thank you to Pi
Hi Frederic,
Op 28-8-2018 om 11:27 schreef Frederic Lecaille:
On 08/27/2018 10:46 PM, PiBa-NL wrote:
Hi Frederic, Oliver,
Thanks for your investigations :).
I've made a little reg-test (files attached). Its probably not
'correct' to commit as-is, but should be enough to get a
reproduction
testing..). There is of
course the option that i did something wrong in the lua as well...
Does the test itself work for you guys? (with nbthread 1)
Did i do something crazy in the lua code? , i do have several loops..
but i don't think thats where it 'hangs' ?..
Regards,
PiBa-NL (Pieter)
Luacurl
Hi List, Thierry, Olivier,
Using a lua-socket with connect_ssl and haproxy running with nbthread
3.. results in haproxy hanging with 3 threads for me.
This while using both 1.9-7/30 version (with the 2 extra patches from
Olivier avoiding 100% on a single thread.) and also a build of today's
would have likely returned in this time
period..
Ill keep it running for a few more days, and switch back to nbthread 3
then.. Till next time ;)
Thanks again!
Best regards,
PiBa-NL (Pieter)
,{ 0.0 }) = 0 (0x0)
kevent(3,0x0,0,{ },200,{ 0.0 }) = 0 (0x0)
Regards,
PiBa-NL (Pieter)
Op 8-8-2018 om 22:49 schreef PiBa-NL:
Hi List,
Ive got a weird issue.. and im not sure where/how to continue digging
at the moment...
Using nbthread=1 nbproc=1, a few lua
es with that before..)
Hoping someone has an idea how to debug it further/differently or
perhaps create a patch that might provide extra information when it
occurs again.?.
Regards,
PiBa-NL (Pieter)
1.9-dev0-842ed9b 2018/07/20
(Well at least my reproduction doesn't work anymore.. while it did quite
easily before.) So thats good ;)
Regards,
PiBa-NL (Pieter)
622 +
'0461-BUG-MEDIUM-threads-Use-the-sync-point-to-che-1.9-dev0.patch' works
okay.
Though i guess just reverting that line is not the right fix ;).
Regards,
PiBa-NL (Pieter)
that can be spotted with the info from the
stack-traces of both 1.8 and 1.9 below ill try and dig further tomorrow
:).Thanks in advance for anyone's time :).
Regards,
PiBa-NL (Pieter)
p.s.
I CC'ed Christopher as he seems to have made the last 2 patches going
into 20180623. Im hoping he has a clue
analysis, though i'm not sure what to do with the info
at the moment, i do hope you guys together can find a likely culprit
from the information given ;).
Regards,
PiBa-NL (Pieter)
Hi List,
I've got no clue how i got into this state ;) and maybe there is nothing
wrong..(well i did resume a VM that was suspended for half a day..)
Still thought it might be worth reporting, or perhaps its solved already
as there are a few fixes for threads after the 6-6 snapshot that i
As can be seen from below output the second socket:receive() takes the
complete 6 seconds that tcploop takes to produce its second response.
Can you take a look? Thanks in advance :).
Regards,
PiBa-NL (Pieter)
---
response1response2
Timing:
[19:42:14.8185]: wait 1 sec
[19:42:15.
Hi Thierry,
Op 25-5-2018 om 15:40 schreef Thierry FOURNIER:
On Fri, 18 May 2018 22:17:00 +0200
PiBa-NL <piba.nl@gmail.com> wrote:
Hi Thierry,
Op 18-5-2018 om 20:00 schreef Thierry FOURNIER:
Hi Pieter,
Could you test the attached patch ? It seems to fix the problem, but I
hav
the same testbox for an hour now without issue.
Thanks !
Regards,
PiBa-NL (Pieter)
to "-" when not
covered by a socket family.
This should be backported to 1.8
Thanks,
-- Daniel
Works for me to get rid of the unix-socket message.
So 1 issue fixed, and 1 to go on this subject ;)
Regards,
PiBa-NL (Pieter)
c/dns.c:1646
More gdb 'bt full' output of all 3 threads is at the bottom of the
attached logfile.
Hope someone can try and fix this :) Config and haproxy -vv also added
below.
Thanks
PiBa-NL (Pieter)
global
maxconn 3002
log /var/run/log local0 info
stats socket
differently? Or should i ignore those.?. Or
is there a way to suppress those messages.?.
Regards,
PiBa-NL (Pieter)
of 150ms.
Regards,
PiBa-NL (Pieter)
con = core.tcp()
con:connect_ssl("216.58.212.132",443) --google: 216.58.212.132
request = [[GET / HTTP/1.0
]]
con:send(request)
res = con:receive("*a")
con:close()
o] 130/195937 (76770) : Wait response 2..
xref_get_peer_and_lock xref->peer == 1
Hope this helps to come up with a solution..
Thanks in advance,
PiBa-NL (Pieter)
Op 9-5-2018 om 19:47 schreef PiBa-NL:
Hi Thierry,
Op 9-5-2018 om 18:30 schreef Thierry Fournier:
It seems a dead lock,
(VERSIONS
DIFFER!)
p.s. Running with different versions between build/running is a bad thing..
Regards,
PiBa-NL
://git.haproxy.org/?p=haproxy.git;a=commit;h=6b96f7289c2f401deef4bdc6e20792360807dde4
Thanks,
PiBa-NL (Pieter)
From 3c60fdace2f23a8c6d070c8fafab660becb8c514 Mon Sep 17 00:00:00 2001
From: PiBa-NL <piba.nl@gmail.com>
Date: Thu, 10 May 2018 01:01:28 +0200
Subject: [PATCH] BUG/MEDIUM: pollers/kqueu
sleep() as you suggest.
Regards,
PiBa-NL
http://git.haproxy.org/?p=haproxy.git;a=blob;f=include/common/xref.h;h=6dfa7b62758dfaebe12d25f66aaa858dc873a060;hb=29d698040d6bb56b29c036aeba05f0d52d8ce94b
31
<http://git.haproxy.org/?p=haproxy.git;a=blob;f=include/common
doesnt know what socket / peer it should release at that point.. its in
the local peer variable of the hlua_socket_receive_yield funtion..
Should it be 'unlocked' before calling stream_int_notify??
Does anyone dare to take a stab at a creating a patch ? If so thanks in
advance ;)
Regards,
Hi List, Thierry, Willy,
Created another little patch. Hope this one fits all submission criteria.
Regards,
PiBa-NL (Pieter)
From cc4adb62c55f268e9e74853f4a4893e2a3734aec Mon Sep 17 00:00:00 2001
From: PiBa-NL <piba.nl@gmail.com>
Date: Sat, 5 May 2018 23:51:42 +0200
Subject: [PATC
guess i just didn't expect it.
Regards,
PiBa-NL
if now its leaking memory instead for some cases.. Is there a easy
way to check?
Regards,
PiBa-NL (Pieter)
diff --git a/src/hlua.c b/src/hlua.c
index 4c56409..6515f52 100644
--- a/src/hlua.c
+++ b/src/hlua.c
@@ -6635,8 +6635,7 @@ error:
static void hlua_applet_http_release(struct appct
Hi Tim, Willy,
Apparently even a simple copy/paste is to difficult for me to do right
sometimes really sorry about that.. :/
Thanks for merging and explaining, ill try and do better next time :)
Regards,
PiBa-NL
Hi List,
Sometimes after a few 'restarts' of haproxy 1.8.8 (using -sf
parameter) one of the processes seems to get into a 'hanging' state
consuming 100% cpu..
In this configuration i'm using 'nbthread 1' not sure if this is related
to the corrupted task-tree from my other lua issue.?.
Hi Tim,
Op 3-5-2018 om 0:26 schreef Tim Düsterhus:
Pieter,
Am 02.05.2018 um 23:54 schrieb PiBa-NL:
If commit message needs tweaking please feel free to do so :).
obviously not authoritative for this, but I noticed directly that the
first line of your message is very long. It should
be merged.?
If commit message needs tweaking please feel free to do so :).
Regards,
PiBa-NL (Pieter)
From a0b01cdc8ccc4ae95c5c03bc98bf859b6115d2f9 Mon Sep 17 00:00:00 2001
From: PiBa-NL <piba.nl@gmail.com>
Date: Wed, 2 May 2018 22:27:14 +0200
Subject: [PATCH] BUG/MINOR, lua/sockets, ma
Hi Thierry,
Op 27-4-2018 om 1:54 schreef PiBa-NL:
Hi Thierry,
Op 26-4-2018 om 12:25 schreef thierry.fourn...@arpalert.org:
Your trace shows a corrupted tree. Maybe it is due to the freebsd
architecture and the corruption is no reproductible on Linux ? I do
not have
freebsd for testing
that at least for the first task to be put into the tree
there is some special handling.. On the other side, if it aint in the
tree, is there technically still a 'next' item??
Below the last part of that logging, and also attached the complete log
from the start.. Perhaps it gives a cl
Regards,
PiBa-NL (Pieter)
mytask = function()
core.sleep(10)
core.Info("TASK start")
local mailconnection = core.tcp()
mailconnection:settimeout(60)
mailconnection = mailconnection
ret = mailconnection:connect("127.0.0.1","80")
repeat
fast. And the
coredump backtrace belonging with that output.
Anything i can try to narrow it down further.? Or perhaps leave it for
now.?. as long as i dont output tons of info on console after the last
tcp.send it seams to work okay for now..
Regards,
PiBa-NL (Pieter)
root@freebsd11:~/.netbeans
Christopher, and that seems to do
the trick nicely for my situation.
If you guys come up with a different approach i'm happy to try that as
well instead.
Regards,
PiBa-NL (Pieter)
Hi Tim,
Op 24-4-2018 om 14:36 schreef Tim Düsterhus:
Hi
Am 23.04.2018 um 22:36 schrieb PiBa-NL:
Is there a bug in my script, or is it more likely that 'something' needs
fixing in the lua api / interaction?
I poked around a bit: The cause in this case is the Content-Length
header. It causes
.
Regards,
PiBa-NL (Pieter)
haproxy.conf & lua scripts
Basically the serverhealth_smtpmail_haproxy.conf
<https://github.com/PiBa-NL/MyPublicProjects/blob/master/haproxy/lua-scripts/serverhealth_smtpmail_haproxy.conf>
and the files it links to are here:
https:
,
PiBa-NL (Pieter)
haproxy.conf
global
nbthread 1
lua-load /root/haproxytest/print_r.lua
lua-load /root/haproxytest/test.lua
defaults
mode http
timeout connect 5s
timeout client 30s
timeout server 60s
frontend TestSite
bind *:80
Lua script
mytask
effects i'm seeing..
Regards,
PiBa-NL (Pieter)
Content of haproxy.conf
global
nbthread 1
lua-load /root/haproxytest/print_r.lua
lua-load /root/haproxytest/test.lua
defaults
mode http
timeout connect 5s
timeout client 30s
timeout server 60s
frontend TestSite
!
Willy
Thanks!
Works as expected with current master.
Do i dare ask a estimate when 1.8.8 might be released? (oh just did. ;) )
O well, i guess ill run production with nokqueue for a little while,
that works alright for me sofar.
Regards,
PiBa-NL (Pieter)
and 'error report' some of the changes.?. I've not tried to
measure this, but technically i think there will be a few more cpu
operations needed overall this way.?.
Regards,
PiBa-NL (Pieter)
ter this the KernelEvent for FD 7 that should read the second browser
request never happens.
I think we can conclude deleting events that don't exist is a bad thing.?
Ill leave further discussion about why and how to you and Oliver :).
Regards,
PiBa-NL (Pieter)
..
Lemme know if its okay like this, you would like the new variable to be
renamed, the if/then/else restructured or just don't like it at all ;).
In the last case please do give a hint about what you would like instead :).
Regards,
PiBa-NL (Pieter)
From 21c191c036f740eb75a4fa59c23232b910cd695c Mon Sep
in the browser. The 'fix'
on the old version after the commit introducing the issue was to call
the EV_SET write delete *less* often. Or maybe my understanding of what
is does is just wrong :).
Op 13-4-2018 om 0:57 schreef PiBa-NL:
Hi Willy,
Op 13-4-2018 om 0:22 schreef Willy Tarreau:
I'm suspecting
h -dk) the request works properly.
Many thanks for your tests.
Willy
Regards,
PiBa-NL (Pieter)
the latest 1.9-dev just by chance ?
Yes when i started compiling from source, thats where i started, the
current master branch. Though (sadly) it has the same broken effect.
Ill try and investigate a bit more.. Though if you think of a possible
patch, i'm happy to try anything out ;)
Regards,
PiBa-NL
:).
Regards,
PiBa-NL (Pieter)
src/ev_kqueue.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/ev_kqueue.c b/src/ev_kqueue.c
index a103ece..49e7302 100644
--- a/src/ev_kqueue.c
+++ b/src/ev_kqueue.c
@@ -78,7 +78,7 @@ REGPRM2 static void _do_poll(struct poller *p, int exp
after the first request and as such should
have no issue sending the credentials the the server.?.
Below are: config / haproxy -vv / tcpdump / sess all
Is it a known issue? Is there anything else i can provide?
Regards,
PiBa-NL (Pieter)
-
# Automaticaly generated
0a:]/
/0001:main.closed[000a:]/
*发件人:*PiBa-NL [mailto:piba.nl@gmail.com]
*发送时间:*2018年3月31日1:20
*收件人:*Xu Ricky <xu.binf...@live.com>; haproxy@formilux.org
*主题:*Re: proxy error 502
Hi Ricky,
Works for me with your configuration, mostly.
Adding a bind to the frontend
app.srvhdr[0009:000c]: Accept-Ranges: bytes
:app.srvcls[0009:adfd]
0001:main.clicls[000a:]
0001:main.closed[000a:]
0002:main.clicls[000b:]
0002:main.closed[000b:]
0003:main.clicls[0009:]
0003:main.closed[0009:]
Regard
..
Regards,
PiBa-NL (Pieter)
is not relevant.
However you should iirc get a warning that the http-request will be
processed before the use_backend directive.
Regards,
PiBa-NL
se_backend and backend
sections.There are no log statements in these sections.)
I did add the following to /etc/rsyslog.conf and messages are being
logged to those files.
local0.*/var/log/haproxy.log
local1.*/var/log/haproxy-status.log
Thanks for any clues,
Glen
Regards,
PiBa-NL (Pieter)
ed!
Not that i have a strong preference, but imho it would be nice to keep
the way to call similar commands the the same.
Regards,
PiBa-NL (Pieter)
Hi Christopher,
Patch seems to work for me.
Maybe Paul can confirm as well.
Regards,
PiBa-NL / Pieter
Op 24-1-2018 om 22:02 schreef Christopher Faulet:
Le 24/01/2018 à 17:21, Paul Lockaby a écrit :
Sorry, I know this list is super busy and that there are a number of
other more important
http-check disable-on-404
server myhost vhost1.pfs.local:303 track example-http/myhost
Regards,
PiBa-NL / Pieter
; "closing/newfd/first if necessary" https://linux.die.net/man/2/dup2 Regards,
PiBa-NL / Pieter
tmas day(s) and a happy new year.
Regards,
PiBa-NL / Pieter
From 49272b2c0bafb413f0fb89717f17c784c2947a4f Mon Sep 17 00:00:00 2001
From: PiBa-NL <pba_...@yahoo.com>
Date: Mon, 25 Dec 2017 21:03:31 +0100
Subject: [PATCH] BUG/MEDIUM: mworker: avoid closing stdin/stdout/stderr file
descriptor
ays appreciated.
Regards,
PiBa-NL
create it under his own name? Either way is
fine for me. :)
Regards,
PiBa-NL / Pieter
From 3129e1ae21e41a026f6d067b3658f6643835974c Mon Sep 17 00:00:00 2001
From: PiBa-NL <pba_...@yahoo.com>
Date: Wed, 6 Dec 2017 01:35:43 +0100
Subject: [PATCH] BUG/MEDIUM: email-alert: don't set server
/msg28158.html
Please let me know if it is OK, or should be done differently.
Thanks in advance,
PiBa-NL / Pieter
From bf80b0398c08f94bebec30feaaddda422cb87ba1 Mon Sep 17 00:00:00 2001
From: PiBa-NL <pba_...@yahoo.com>
Date: Wed, 6 Dec 2017 01:35:43 +0100
Subject: [PATCH] BUG/MEDIUM: email
bind's then..)
If a mailserver is listening, then 800+ mails are received..
Regards,
PiBa-NL / Pieter
defaults
option log-health-checks
listen HAProxyLocalStats
bind 127.0.0.1:42200 name localstats
mode http
stats enable
mailers globalmailers
mailer ex01 127.0.0.1:3325
backend
at all..
Anyhow when you have time to look into it, i look forward to your
feedback :) . Thanks in advance.
Regards,
PiBa-NL / Pieter
From c103dbd7837d49721ccadfb1aee9520e821a020f Mon Sep 17 00:00:00 2001
From: PiBa-NL <pba_...@yahoo.com>
Date: Tue, 28 Nov 2017 23:26:08 +0100
Subject:
.
This is intended to solve my previously reported 'issue' :
https://www.mail-archive.com/haproxy@formilux.org/msg27963.html
Let me know if something about it needs fixing..
Thanks
PiBa-NL / Pieter
From 06224a3fcf7b39bf1bf0128a5bac3d0209bc2aab Mon Sep 17 00:00:00 2001
From: PiBa-NL <pba_...@yahoo.
to use it?
- wont the rd wr char* values leak memory?
Anyhow the biggest part that should be noticed of the bug is the
sometimes wrongful alert when the fd is actually '0'...
If anything needs to be changed let me know.
Regards,
PiBa-NL / Pieter
From 486d7c759af03f9193ae3e38005d8325ab069b37 Mon
Hi Christopher / Willy,
On Tue, Nov 28, 2017 at 10:28:20AM +0100, Christopher Faulet wrote:
Here is a patch that should fix the deadlock. Could you confirm it fixes
your bug ?
Fix confirmed.
Thanks,
PiBa-NL / Pieter
though.. no mail is received.
I tried using nokqueu and nopoll, but that did not result in any
improvement..
Anything else i can provide?
Regards,
PiBa-NL / Pieter
haproxy -f /root/hap.conf -V
[WARNING] 330/204605 (14771) : config : missing timeouts for frontend
'TestMailFront'.
| While
Hi Willy,
Op 25-11-2017 om 8:33 schreef Willy Tarreau:
Hi Pieter,
On Tue, Nov 21, 2017 at 04:34:16PM +0100, PiBa-NL wrote:
Hi William,
I was intending to use the new feature to pass open sockets to the next
haproxy process.
And thought that master-worker is a 'requirement' to make that work
of that package
if haproxy 1.8 gets released as it currently is.
I'm not sure if other folks are using some service management tool like
systemd on FreeBSD... But i guess time will tell, i'm sure 1.8 wont be
the last release ever so fixes when required will come :).
Regards,
PiBa-NL / Pieter
everything
stops running..
Anyhow looking forward to your replies.
Regards,
PiBa-NL
Op 22-11-2017 om 17:48 schreef PiBa-NL:
Hi William,
I'm not 100% sure but i think the stdout and errout files should be
closed before process exit?
It seems to me they are not.
At least with the following php
check?
Regards,
PiBa-NL
#!/usr/local/bin/php-cgi -f
0 => array("pipe", "r"), // stdin is a pipe that the child will
read from
1 => array("pipe", "w"), // stdout is a pipe that the child will
write to
2 => array("pipe", &q
nda expected this to indeed be 'as intended' -sf will fully replace
the old processes.
Thanks for your reply.
Regards,
PiBa-NL / Pieter
so far :)
Daniel
Regards,
PiBa-NL / Pieter
the (original?) master was successful in reloading the config /
starting new workers or how should this be done?
Currently a whole new set of master-worker processes seems to be take over..
Or am i taking the wrong approach here?
Regards,
PiBa-NL / Pieter
#1# Startup script (simplified..) haprox
not testedit and it may even break epoll, but one thing at a
time :-)
Thanks,
Willy
You patch fixes the issue.
If you've got a definitive patch lemme know.
Thanks,
PiBa-NL
Hi Willy,
Op 20-11-2017 om 21:46 schreef Willy Tarreau:
Hi Pieter,
On Mon, Nov 20, 2017 at 01:47:48AM +0100, PiBa-NL wrote:
Hmmm thinking about it there might be something. Could you start with
"-dk" to disable kqueue and fall back to poll ? kqueue registers a post-
fork functio
-mD7vv/vQe/Pj33VRqdju
https://0bin.net/paste/sJ955XNt2hE1a9mF#xsMP2tzydlK3BVpxo2nNRl878SRbxZNAUpRw5-YhwdM
Op 20-11-2017 om 1:47 schreef PiBa-NL:
Hi List,
After compiling haproxy 1.8-rc4 (without modifications) on FreeBSD11.1
i'm trying to run it with master-worker option.
I can run
ed i get the result below from haproxy -vv, looks
good :) but i didn't actually start it yet with a proper config.
Regards,
PiBa-NL / Pieter
root@:/usr/ports/net/haproxy-devel # haproxy -vv
HA-Proxy version 1.8-rc4-cfe1466 2017/11/19
Copyright 2000-2017 Willy Tarreau <wi...@haproxy.org>
Bui
for a day now. Sofar it
sticks to <1% cpu usage.
Will report if anything changes, cant tell for sure as don't have a
clear reproduction of the issue, but my issue 'seems' fixed.
Regards,
PiBa-NL / Pieter
haproxy-ss
PORTVERSION= 20171017
CATEGORIES= net www
MASTER_SITES= http://www.haproxy.org/download/1.7/src/snapshot/
And then ran:
make clean build install NO_CHECKSUM=yes
Which did 'seem' to download the 'intended?' file..
Thanks,
PiBa-NL / Pieter
Hi Willy,
Op 9-11-2017 om 5:45 schreef Willy Tarreau:
Hi Pieter,
On Thu, Nov 09, 2017 at 02:28:46AM +0100, PiBa-NL wrote:
Actually haproxy has been running for a few weeks with 100% and i didnt
notice.. it does keep working it seems..
Anyhow thought i would try and capture the next event
backend that is part of the configuration never got a
single request according to stats..
Is it a known issue?
Are tcpdump/truss output desired ..? (where should i send em?)
Is there any other output that can try to gather next time?
Regards,
PiBa-NL
HA-Proxy version 1.7.9 2017/08/18
TARGET
lt;http://192.168.0.5:9876> maxconn 2000
With this configuration can i undergo my setup with 8000 connection
load distribution or do i have to undergo some changes here
Thanks,
Kushal
Add a 'maxconn 8000' in 'global' section?
Regards,
PiBa-NL
proxy-dconv/1.7/configuration.html#4.2-optio
n%20log-health-checks
in your config.
It would be nice to know which haproxy version you use.
haproxy -vv
--
Best Regards
Aleks
https://www.me2digital.com/
--
Best Regards
Aleks
Regards,
PiBa-NL
-SSL
There is no acl for the backend above? so probably the default_backend
below will never be reached.
Could it be the above backend returns the 404 your seeing?
default_backend CitrixSF-SSL
Regards,
PiBa-NL
Hi Willy, Christopher,
Do you perhaps have a small update about the "[PATCH] MAJOR: ssl: add
'tcp-fallback' bind option for SSL listeners" ?
I've not seen any new information about it for a while, will it come
with 1.7devX ? Or should there first be a solid http/2 implementation
before
101 - 200 of 342 matches
Mail list logo
