RE: 'clear table table' clearing only bottom entry? (1.5dev7)
Good morning Willy, I hope the new year is treating you well! I was wondering whether you were able to reproduce this issue? I had a quick look on git but couldn't immediately find any commits. If not, is there any further information or work I could do to assist? Unfortunately I'm not quite au fait with C! Thanks, Joe -Original Message- From: Willy Tarreau [mailto:w...@1wt.eu] Sent: 28 November 2011 20:25 To: Price Joe JPC Cc: haproxy@formilux.org Subject: Re: 'clear table table' clearing only bottom entry? (1.5dev7) *SNIP* Using 'clear table backend1' on the socket seems to only be clearing the bottom entry of 'show table backend1' wheras the docs say In the case where no options arguments are given all entries will be removed. I'm reasonably sure this worked fine in 1.4. You might have caught a bug. I'll check this ASAP, this behaviour is not expected at all. *SNIP* Thanks, Willy
Re: 'clear table table' clearing only bottom entry? (1.5dev7)
Hi Joe, On Mon, Jan 09, 2012 at 09:47:05AM -, joe.pr...@vaisala.com wrote: Good morning Willy, I hope the new year is treating you well! I was wondering whether you were able to reproduce this issue? I had a quick look on git but couldn't immediately find any commits. No, I completely forgot about it. I think I should setup some bugtracking tool somewhere, because it's not the first time I forget about a bug when I can't work on it for a full week. If not, is there any further information or work I could do to assist? Unfortunately I'm not quite au fait with C! I just have to recheck the whole thread to see how to reproduce the issue. Thanks, Willy
RE: 'clear table table' clearing only bottom entry? (1.5dev7)
Good Morning! Is there a better place to report/track bugs? -Original Message- From: joe.pr...@vaisala.com [mailto:joe.pr...@vaisala.com] Sent: 09 November 2011 09:32 To: haproxy@formilux.org Subject: 'clear table table' clearing only bottom entry? (1.5dev7) Using 'clear table backend1' on the socket seems to only be clearing the bottom entry of 'show table backend1' wheras the docs say In the case where no options arguments are given all entries will be removed. I'm reasonably sure this worked fine in 1.4. Also, in the docs, my socat (1.7.1.2) doesn't work as the example... I needed to `echo clear table backend1 | socat unix-connect:haproxy.sock stdio` Apologies if this isn't the correct place to report possible bugs, I didn't see anywhere better on the website. My configuration follows: global daemon maxconn 256 #chroot chroot stats socket /home/vaisala/haproxy/haproxy.sock mode 0600 level admin defaults log global option tcplog option logasap mode tcp timeout check 4s timeout connect 4s timeout client 2m timeout server 2m backend backend1 log 127.0.0.1 local0 balance leastconn stick-table type integer size 10k expire 70m stick on dst_port default-server weight 100 maxconn 1 inter 30s downinter 2m fastinter 5s slowstart 15m server server1 address1:port check server server2 address2:port check
'clear table table' clearing only bottom entry? (1.5dev7)
Using 'clear table backend1' on the socket seems to only be clearing the bottom entry of 'show table backend1' wheras the docs say In the case where no options arguments are given all entries will be removed. I'm reasonably sure this worked fine in 1.4. Also, in the docs, my socat (1.7.1.2) doesn't work as the example... I needed to `echo clear table backend1 | socat unix-connect:haproxy.sock stdio` Apologies if this isn't the correct place to report possible bugs, I didn't see anywhere better on the website. My configuration follows: global daemon maxconn 256 #chroot chroot stats socket /home/vaisala/haproxy/haproxy.sock mode 0600 level admin defaults log global option tcplog option logasap mode tcp timeout check 4s timeout connect 4s timeout client 2m timeout server 2m backend backend1 log 127.0.0.1 local0 balance leastconn stick-table type integer size 10k expire 70m stick on dst_port default-server weight 100 maxconn 1 inter 30s downinter 2m fastinter 5s slowstart 15m server server1 address1:port check server server2 address2:port check