L’actualité hebdomadaire par RFI - 28/08/2015
Visualisez cet email dans votre navigateur
http://rfi.nlfrancemm.com/HM?b=7sGYhZdtBxp5FWGdcWhRWyP1r8qcT9OiP7ZIlFIA0q8wy2FsYUqx4IIT5avfs3Lv&c=DMDfSy30mUljARvcFrFULQ
La grève de la faim, le corps comme arme de protestation
Partout sur la planète,
Le 28 août 2015 15:45, a écrit :
>
> Hello,
>
> We have tcp-check configured on some backends, which works fine, except
when service is flapping.
>
> If the backend server is in transitional state, for example
transitionally DOWN (going up), the counter is not reset to 0 if tcp-check
give a KO sta
Hi,
On 28.08.2015 12:23, Lukas Erlacher wrote:
> Hello,
>
> firstly, I am aware that SMTPS is deprecated and should not be used. But
> I have to support legacy infrastructure and the person who can tell me
> that it is fine to turn off SMTPS isn't around atm, so I'm trying to
> make this work.
s
Hello,
We have tcp-check configured on some backends, which works fine, except
when service is flapping.
If the backend server is in transitional state, for example
transitionally DOWN (going up), the counter is not reset to 0 if
tcp-check give a KO state between some OK state. The result is
On 8/27/2015 10:22 PM, Nathan Williams wrote:
> We have 2 OpenStack VMs with IPs on the internal network, a keepalived
> -managed VIP on the internal network that's added to each VMs allowed
> -address-pairs in neutron, and a floating IP from the external network
> mapped to the internal VIP (OpenS
After doing some more debugging using nc and openssl s_client it appears
that postfix first expects the PROXY line and then the ssl CLIENT_HELLO.
So passing through the client TCP connection would be the correct
configuration I believe.
So if I configure it like this:
frontend ft_smtps
Hello,
firstly, I am aware that SMTPS is deprecated and should not be used. But
I have to support legacy infrastructure and the person who can tell me
that it is fine to turn off SMTPS isn't around atm, so I'm trying to
make this work.
I have a postfix server with SMTPS, this is the master.c
>> Ok, you may be hitting a bug. Can you provide haproxy -vv output?
>>
>
>
> What do you mean? I get the following warning when trying to use this
> option in tcp backend/frontend:
Yes I know (I didn't realize you are using tcp mode). I don't mean the
warning is the bug, I mean the tcp mode is su
> On 28 авг. 2015 г., at 12:18, Lukas Tribus wrote:
>
>>> Use "option http-no-delay" [1] to disable Nagle unconditionally.
>>
>>
>> This option requires HTTP mode, but I must use TCP mode because our
>> protocol is not HTTP (some custom protocol over TCP)
>
> Ok, you may be hitting a bug. Can
>> Use "option http-no-delay" [1] to disable Nagle unconditionally.
>
>
> This option requires HTTP mode, but I must use TCP mode because our
> protocol is not HTTP (some custom protocol over TCP)
Ok, you may be hitting a bug. Can you provide haproxy -vv output?
Thanks,
Lukas
> On 28 авг. 2015 г., at 12:12, Lukas Tribus wrote:
>
>> Hello,
>>
>> The flag TCP_NODELAY is unconditionally set on each TCP (ipv4/ipv6)
>> connections between haproxy and the server, and beetwen the client and
>> haproxy.
>
> That may be true, however HAProxy uses MSG_MORE to disable and
> e
> Hello,
>
> The flag TCP_NODELAY is unconditionally set on each TCP (ipv4/ipv6)
> connections between haproxy and the server, and beetwen the client and
> haproxy.
That may be true, however HAProxy uses MSG_MORE to disable and
enable Nagle based on the individual situation.
Use "option http-no-d
Hi Baptiste,
In our production setup. The flow will be like this:
incoming clients request --> *HAProxy* (as a load balancer) --> Nginx (as a
router) --> App servers (java and ruby)
In our java app servers, sometime there is an exception log complained by
'Netty' (our java web server) with a mes
13 matches
Mail list logo
