Re: [PATCH] MEDIUM: mailer: try sending a mail up to 3 times

On Sat, Nov 21, 2015 at 01:21:16AM +0100, PiBa-NL wrote: > Hi Simon, > > Ok, ill try and see if i can add a config setting for it. And move the > whitespace changes to a separate patch. > Will take me some time.. And for what it's worth, I was about to make the same comments as Simon. Please how

unsubscribe

Re: [PATCH] MEDIUM: mailer: try sending a mail up to 3 times

Hi Simon, Ok, ill try and see if i can add a config setting for it. And move the whitespace changes to a separate patch. Will take me some time.. Thanks for your feedback, PiBa-NL Op 21-11-2015 om 0:30 schreef Simon Horman: On Fri, Nov 20, 2015 at 11:58:19PM +0100, PiBa-NL wrote: Hi Willy,

Re: [PATCH] MEDIUM: mailer: try sending a mail up to 3 times

On Fri, Nov 20, 2015 at 11:58:19PM +0100, PiBa-NL wrote: > Hi Willy, > > Op 16-11-2015 om 19:57 schreef Willy Tarreau: > >I agree with you since we don't know the timeout value nor what it applies > >to (connection or anything). Thus I think that we should first find and > >change that value, and

Re: [PATCH] MEDIUM: mailer: try sending a mail up to 3 times

Hi Willy, Op 16-11-2015 om 19:57 schreef Willy Tarreau: I agree with you since we don't know the timeout value nor what it applies to (connection or anything). Thus I think that we should first find and change that value, and maybe after that take your patch to permit real retries in case of con

RE: Owncloud through Haproxy makes upload not possible

Hi Piotr, > Unfortunately, using 1.5.15 didn't change anything. a few things I would suggest to try/troubleshoot: - try nokqueue mode [1] - try option http-no-delay [2] - check cpu usage (system and haproxy) while uploading - truss ([3]) haproxy while uploading - tcpdump the frontend connection

Re: Owncloud through Haproxy makes upload not possible

On 11/20/2015 21:05, Bryan Talbot wrote: > On Fri, Nov 20, 2015 at 1:39 AM, Piotr Kubaj > wrote: > > > > Unfortunately, using 1.5.15 didn't change anything. The logs are: > > > We can see from the logs below that the connection is aborting with CD > or sH codes. > >

Re: Owncloud through Haproxy makes upload not possible

On 11/20/2015 21:05, Bryan Talbot wrote: > On Fri, Nov 20, 2015 at 1:39 AM, Piotr Kubaj > wrote: > > > > Unfortunately, using 1.5.15 didn't change anything. The logs are: > > > We can see from the logs below that the connection is aborting with CD > or sH codes.

Re: Owncloud through Haproxy makes upload not possible

On Fri, Nov 20, 2015 at 1:39 AM, Piotr Kubaj wrote: > > > Unfortunately, using 1.5.15 didn't change anything. The logs are: > We can see from the logs below that the connection is aborting with CD or sH codes. The docs say: CD The client unexpectedly aborted during data transfer. This c

RE: Connect() failed using unix sockets

>> >> So anybody know what resource "free ports" relates to in the unix >> domain socket case? Are there any other debug options to find out >> more about what is happening. > > I suspect the connect() call returns EAGAIN Digging some more, it looks like the kernel returns EAGAIN when the backlog

RE: Connect() failed using unix sockets

Hi Greg, > Connect() failed for backend frontend: no free ports. > Connect() failed for backend frontend: no free ports. > Connect() failed for backend frontend: no free ports. > Connect() failed for backend frontend: no free ports. > Connect() failed for backend frontend: no free ports. >

Re: Re: CPU 100% when waiting for the client timeout

ok, thanks for your reply :-) -- Best Regards BaiYang baiy...@gmail.com http://baiy.cn < END OF EMAIL > From: Willy Tarreau Date: 2015-11-21 02:16 To: baiyang CC: Lukas Tribus; haproxy Subject: Re: Re: CPU 100% when waiting for the client timeout On Fri, Nov 20, 2015 at

Re: Re: CPU 100% when waiting for the client timeout

On Fri, Nov 20, 2015 at 09:26:53PM +0800, baiyang wrote: > Hi Willy, > > Another question: > As you said, HAProxy seems no using multi-thread model, so multi-process > (nbproc) is the only choice for HAProxy if we want using multiple processor > cores sufficiently? For now yes. You may want to

Re: Selecting back end from host header

> use_backend %[req.hdr(host),lower] Is there anyway to extract the host subdomain to use like this (rather than the full hostname)? I can't see any obvious way to do it from the manual, but perhaps I'm missing something.

Re: TCP connections rdp

Douglas, The stats page will only show the number of connections and which server they are going to... I think you mean you want to see the contents of the stick table i.e.: echo "show table VIP1" | socat unix-connect:/var/run/haproxy.stat stdio # table: VIP1, type: ip, size:10485760, used:1 0x11

Comparer les offres d'assurances pour votre animal de compagnie

http://news.topaffaireduweb.com/YSUzRDQ5NyUyNmMlM0QxNCUyNmUlM0QxMTc2ODglMjZsJTNEMTU4JTI2cyUzRDI3MzY1MSUyNnQlM0RjJTI2bHMlM0Q1JTI2dW5zdWJzY3JpYmVfbGluayUzRCUyNm1pcnJvcl9saW5rJTNE Assurance Chien Chat ILS NE SONT PAS TOUS DES SUPER HéROS. Protégez-les ! [1]

Re: TCP connections rdp

Hello.. thanks for the answer. I would like to monitor the User connected on port 3389, tried as it is below, but I could not make it work. listen stats bind: enable stats connect timeout 4000 client timeout 42000 server timeout 43000 stats uri / option httpclose stats auth loadbalancer: load

Re: Re: CPU 100% when waiting for the client timeout

Hi Willy, Another question: As you said, HAProxy seems no using multi-thread model, so multi-process (nbproc) is the only choice for HAProxy if we want using multiple processor cores sufficiently? Thanks :-) -- Best Regards BaiYang baiy...@gmail.com http://baiy.cn < END OF EMA

Re: Re: CPU 100% when waiting for the client timeout

On Fri, Nov 20, 2015 at 08:15:03PM +0800, baiyang wrote: > > But the kernel's build date dates 2012, that's what troubles me. Are you > > sure you're not running on a locally built kernel that is never updated > > anymore or any such thing ? > Yes I sure we are using the official kernel, and did

Re: ingress TCP connection state

HI, any thoughts? Thank you very much! Miloš > 18. 11. 2015 v 19:22, Miloš Kozák : > > Hello, > > I have got haproxy installed from CentOS 6 repository, and I use TCP mode for > a special messaging protocol. Occasionally, the ingress TCP connection dies, > but the TCP connection towards the a

Re: ingress TCP connection state

HI, any thoughts? Thank you very much! Miloš > 18. 11. 2015 v 19:22, Miloš Kozák : > > Hello, > > I have got haproxy installed from CentOS 6 repository, and I use TCP mode for > a special messaging protocol. Occasionally, the ingress TCP connection dies, > but the TCP connection towards the a

Re: Re: CPU 100% when waiting for the client timeout

Hi, Thanks for your advice Aleks, I'll give it a try if "3.2.0-95-generic #135-Ubuntu SMP Tue Nov 10 13:33:29 UTC 2015" still have this problem :-) -- Best Regards BaiYang baiy...@gmail.com http://baiy.cn < END OF EMAIL > From: Aleksandar Lazic Date: 2015-11-20 20:00 To

Re: Re: CPU 100% when waiting for the client timeout

Hi Willy, > But the kernel's build date dates 2012, that's what troubles me. Are you sure > you're not running on a locally built kernel that is never updated anymore or > any such thing ? Yes I sure we are using the official kernel, and did a reboot after upgrade. But just like I said, Ubuntu

Re: CPU 100% when waiting for the client timeout

Hi. Am 20-11-2015 11:59, schrieb baiyang: Hi Willy, This one seems to have missed 3 years of bugfixes I've just done a "apt-get update && apt-get upgrade" successfully and reboot the machine this week. I think the OS is fresh enough, but I'll try to upgrade the kernal to a newer one. :-) Ho

RE: [SPAM] Re: CPU 100% when waiting for the client timeout

> I think the right way to upgrade kernel with ubuntu, is: > > apt-get update && apt-get dist-upgrade Exactly, apt may hold back kernel upgrades otherwise. Lukas

Re: CPU 100% when waiting for the client timeout

Hi BaiYang, On Fri, Nov 20, 2015 at 06:59:12PM +0800, baiyang wrote: > Hi Willy, > > > This one seems to have missed 3 years of bugfixes > I've just done a "apt-get update && apt-get upgrade" successfully and reboot > the machine this week. I think the OS is fresh enough, but I'll try to > upgra

[SPAM] Re: CPU 100% when waiting for the client timeout

I think the right way to upgrade kernel with ubuntu, is: apt-get update && apt-get dist-upgrade Le 20/11/2015 12:13, baiyang a écrit : he kernel seems not upgrade to new version automatically within above commands, we need do it explicitly. I think it's a protection mechanism for the system c

Re: Re: CPU 100% when waiting for the client timeout

Ok, so I'll try to do an explicitly kernal upgrade now. :-) -- Best Regards BaiYang baiy...@gmail.com http://baiy.cn < END OF EMAIL > From: Willy Tarreau Date: 2015-11-20 18:55 To: Lukas Tribus CC: baiyang; haproxy Subject: Re: CPU 100% when waiting for the client timeout

Re: TCP connections rdp

Douglas, I'm a bit confused on the question but an example Session Broker Config would be: listen Test bind 192.168.64.28:3389 transparent mode tcp balance leastconn persist rdp-cookie server backup 192.168.64.15:3389 backup non-stick timeout client 12h timeout server

Re: RE: CPU 100% when waiting for the client timeout

Hi, Lukas No, I did a reboot after "apt-get update && apt-get upgrade". Even more, I have been reboot the server many times to troubleshooting the issue during these days. But in Ubuntu, the kernel seems not upgrade to new version automatically within above commands, we need do it explicitly.

RE: CPU 100% when waiting for the client timeout

> Hi Willy,  >  >> This one seems to have missed 3 years of bugfixes  > I've just done a "apt-get update && apt-get upgrade" successfully and  > reboot the machine this week. I think the OS is fresh enough, but I'll  > try to upgrade the kernal to a newer one. :-)  When you upgrade Ubuntu precise

Re: CPU 100% when waiting for the client timeout

Hi Willy, > This one seems to have missed 3 years of bugfixes I've just done a "apt-get update && apt-get upgrade" successfully and reboot the machine this week. I think the OS is fresh enough, but I'll try to upgrade the kernal to a newer one. :-) > I find this very strange here because the r

Re: CPU 100% when waiting for the client timeout

Hi Lukas, On Fri, Nov 20, 2015 at 11:34:50AM +0100, Lukas Tribus wrote: > >> # uname -a > >> Linux WD-G0-SRP1 3.2.0-29-generic #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC > >> 2012 x86_64 x86_64 x86_64 GNU/Linux > > > > This one seems to have missed 3 years of bugfixes but anyway I don't see > > how a

RE: CPU 100% when waiting for the client timeout

>> # uname -a >> Linux WD-G0-SRP1 3.2.0-29-generic #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC >> 2012 x86_64 x86_64 x86_64 GNU/Linux > > This one seems to have missed 3 years of bugfixes but anyway I don't see > how any kernel bug could make haproxy fail, and if it did we'd have to > find a workaround

Re: Owncloud through Haproxy makes upload not possible

On 11/19/15 22:43, Igor Cicimov wrote: > > It might be something specific to BSD os causing issues for you > since I haven't heard of anyone complaining about ssl till now. > You can also try latest stable 1.5.15 since I can't see any 1.6 > specific feature in your config. > Unfortunately, using

RE: RE: security system products, you still do not know these situations. (Refused to profiteering)

  RE: RE: security system products, you still do not know these situations. (Refused to profiteering)   Dear,   Please allow me to take the liberty to send you this letter, but I hope you can read. If it is useful to you, you can contact me, maybe we can be friends; if not useful, you may igno

Re: Owncloud through Haproxy makes upload not possible

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/19/15 22:43, Igor Cicimov wrote: > > It might be something specific to BSD os causing issues for you > since I haven't heard of anyone complaining about ssl till now. > You can also try latest stable 1.5.15 since I can't see any 1.6 > spec

Re: Owncloud through Haproxy makes upload not possible

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/19/15 22:43, Igor Cicimov wrote: > > On 20/11/2015 7:23 AM, "Piotr Kubaj" > wrote: >> >> On 11/19/2015 17:01, Janusz Dziemidowicz wrote: >>> 2015-11-19 15:45 GMT+01:00 Piotr Kubaj >: >>>

Re: Re: CPU 100% when waiting for the client timeout

Hi, On Fri, Nov 20, 2015 at 04:11:48PM +0800, baiyang wrote: > Sorry for send it again, mail.formilux.org told me my attachment is too > large: /var/spool/mail/archives-haproxy: error writing message: File too large > So I striped it. Thanks. I don't remember the file size limit but the list del

[SPAM] Re: ABS/Aluminum/Glass Panel lights for Indoor using

Dear Manager,Hope this Email find you well!As a professional LED Lights(Indoor&Outdoor) manufacturer more than 10 years, we cooperate with many customers in Turkey/Russian and so on.All of our products meet CE&ROHs standard and i believe the price is competitive in your area.After some research of