On 12.02.2012 14:24, Cyril Bonté wrote:
Take into account that virtualization can be a bottleneck for a
network component like haproxy.
I know that, that's the reason I used one physical nic especially for
the haproxy instances.
Sure there could still be some problem, but that would be a metter of
testing it out.
Right now the traffic doesn't seem to be a problem, cause it's being
relayed as it should be.
You said that you couldn't find anything useful in the logs.
From the configuration you just posted, you're using the default log
format.
You should use an enhanced one, at least with "option tcplog" or
better for http : "option httplog". This is a prerequisite to find
useful information : it will help you find where time is spent (See
chapter 8.2.3 in the documentation).
Btw, talking about the configuration, your line "stat refresh s" is
wrong and ineffective (missing numbers for the refresh, which
currently disables the action, but could implies a bug in future
versions).
Thank you for that hint, I will correct that right away.
To the log option, I've already found that entry too, the only thing
with the pfsense implementation is to change that setting.
Regards
Sebastian
--
Sebastian Fohler
Far-Galaxy Networks
Web: http://www.far-galaxy.de
Tel.: +49 (0)173 8796211
E-Mail: [email protected]
