yep, I bound everything but I still get warnings. There's a bug that might be related where binding stats doesn't work with stats bind-process, perhaps that's my problem?
> On 11 Mar 2016, at 22:33, Chad Lavoie <[email protected]> wrote: > > Greetings, > > Ah, is the stats socket also bound to one process? For example "stats socket > /var/run/haproxy.sock mode 0600 level admin process 4" to bind it to process > 4. > > Otherwise the process your querying for the stats will bounce around, even if > the process with the table doesn't. > > - Chad > > On 03/11/2016 05:29 PM, Robert Samuel Newson wrote: >> ah, yes, nbproc of 2 here, but I should be clear. The stick tables are in a >> proxy pinned to one single process, the other is used to handle TLS decoding. >> >>> On 11 Mar 2016, at 18:27, Chad Lavoie <[email protected]> wrote: >>> >>> Greetings, >>> >>> That should have been "Do you have nbproc set and more then 1?", sorry. >>> >>> - Chad >>> >>> On 03/11/2016 01:17 PM, Chad Lavoie wrote: >>>> Greetings, >>>> >>>> Do you have nbproc set or more then 1? >>>> >>>> If so, then each thread has its own stick table set; and depending on what >>>> thread handles it the values will differ. >>>> >>>> Individual frontends can be set to a specific thread with bind-process (or >>>> for SSL a frontend specifically for SSL termination can be made). If that >>>> is the issue your seeing and you want more examples in that direction let >>>> me know what your use-case looks like and I'll go into more details there. >>>> >>>> - Chad >>>> >>>> On 03/11/2016 12:28 PM, Robert Samuel Newson wrote: >>>>> Hi, >>>>> >>>>> I'm using haproxy 1.6.3 and think I've uncovered an issue. >>>>> >>>>> I use the stick table feature and as you can see from below, items appear >>>>> and disappear randomly, these samples were taken less than a second >>>>> apart. Obviously the items in the middle have at least 56 seconds >>>>> remaining before expiration, so should have been in all three samples. >>>>> They reappear if I keep sampling, in seemingly random subsets. >>>>> >>>>> I can't easily tell if this just a display issue (i.e 'show table' has >>>>> the bug) or whether the table behaves as if it's empty when show table >>>>> shows it empty. >>>>> >>>>> Any advice? >>>>> >>>>>> echo "show table lookup" | socat /var/haproxy.sock - >>>>> # table: lookup, type: string, size:51200, used:0 >>>>> >>>>>> echo "show table lookup" | socat /var/haproxy.sock - >>>>> # table: lookup, type: string, size:51200, used:3 >>>>> 0x3c1d9ec: key=user1 use=0 exp=56035 gpc0_rate(1000)=0 >>>>> 0x3c0ff0c: key=user2 use=0 exp=58786 gpc0_rate(1000)=0 >>>>> 0x3c41b2c: key=user3 use=0 exp=59737 gpc0_rate(1000)=0 >>>>> >>>>>> echo "show table lookup" | socat /var/haproxy.sock - >>>>> # table: lookup, type: string, size:51200, used:0 >>>>> >>>>> >>>> >> >
