Hi,
thanks for the help, but it seems that didnt fix it.
I changed the Makefile.bsd as advised and with the new build
i at least dont get the error message anymore when i try
maxconn anything higher then 1024.
I also applied the sysctl and ulimit changes.
The problem is when i run apachebench against the haproxy it still
starts to choke when its hitting maxconn 1024 levels.
While that is happening cpu load is at 5%.
I have three backend servers from which i know they each can sustain
about 5000 concurrent connections with ease so its not the backend either.
This is the output of haproxy -vv
root@proxytest [haproxy-1.5-dev19] # haproxy -vv
HA-Proxy version 1.5-dev19 2013/06/17
Copyright 2000-2013 Willy Tarreau <[email protected]>
Build options :
TARGET = openbsd
CPU = native
CC = gcc
Default settings :
maxconn = 65530, bufsize = 8030, maxrewrite = 10300, maxpollevents = 200
Encrypted password support via crypt(3): no
Built without zlib support (USE_ZLIB not set)
Compression algorithms supported : identity
Built without OpenSSL support (USE_OPENSSL not set)
Built with PCRE version : 8.31 2012-07-06
PCRE library supports JIT : no (USE_PCRE_JIT not set)
Built with transparent proxy support using: SO_BINDANY
Available polling systems :
kqueue : pref=300, test result OK
poll : pref=200, test result OK
select : pref=150, test result OK
Total: 3 (3 usable), will use kqueue.
On 10/7/2013 6:17 PM, Thomas Heil wrote:
Hi,
On 08.10.2013 01:49, Sven Liedtke wrote:
Hi,
i seem to have issues getting haproxy to run with more then maxconn
1024 on openbsd 5.3
You have to change Makefile.bsd
--
SMALL_OPTS = -DBUFSIZE=8030 -DMAXREWRITE=1030 -DSYSTEM_MAXCONN=1024
--
e.g to
--
SMALL_OPTS = -DBUFSIZE=16060 -DMAXREWRITE=10300 -DSYSTEM_MAXCONN=65530
--
Dont forget to make clean.
Even though i have:
root@proxytest [haproxy] # sysctl | grep maxfiles
kern.maxfiles=20000
root@proxytest [haproxy] # ulimit -n
20000
and in haproxy.cfg:
global
log /dev/log local0 debug
log /dev/log local1 info
maxconn 4096
#chroot /usr/share/haproxy
user root
group wheel
daemon
This is happening with 1.4.24 and 1.5-dev19
Anyone an idea?
and maybe some ulimits
--
ulimit -d 3048576
ulimit -f 138192
ulimit -n 165500
ulimit -u 165500
--
and some sysctl values
--
kern.maxfiles=90001
kern.maxproc=90001
kern.maxlocksperuid=100001
kern.maxclusters=100001
kern.somaxconn=32001
--
Be careful with pcre. Maybe you have to REGEX=... to whatever is working.
If you use pf the dont use "scrub". Its nearly the same like using conntrack
with Linux.
Regards,
Sven
hope that helps you a bit.
cheers
thomas