On Fri, Jun 8, 2018 at 10:15 PM, Mike Torra wrote:
> Hi -
>
> I am relatively new to using haproxy, and I am trying to figure out if it
> is possible to use a consistent hashing algorithm to hash a cookie value in
> to a separate header. This seems very similar to how you would use a
> consistent
Hi -
I am relatively new to using haproxy, and I am trying to figure out if it
is possible to use a consistent hashing algorithm to hash a cookie value in
to a separate header. This seems very similar to how you would use a
consistent `hash-type` (
http://cbonte.github.io/haproxy-dconv/1.8/configu
> On 8 Jun 2018, at 18:21, Willy Tarreau wrote:
>
> On Fri, Jun 08, 2018 at 01:09:04PM +0200, Thierry Fournier wrote:
>> Hi,
>>
>> runtime errors doesn't provides the error line, in particular the memory
>> error (out of memory)
>>
>> Please find a Lua patch in attachment.
>> It provides ba
On Fri, Jun 08, 2018 at 06:22:39PM +0200, William Dauchy wrote:
> On Fri, Jun 08, 2018 at 04:31:30PM +0200, William Lallemand wrote:
> > That's great news!
> >
> > Here's the new patches. It shouldn't change anything to the fix, it only
> > changes the sigprocmask to pthread_sigmask.
>
> thanks, I
On Fri, Jun 08, 2018 at 04:31:30PM +0200, William Lallemand wrote:
> That's great news!
>
> Here's the new patches. It shouldn't change anything to the fix, it only
> changes the sigprocmask to pthread_sigmask.
thanks, I attached the backport for 1.8 and started a new test with
them.
Feel free to
On Fri, Jun 08, 2018 at 01:09:04PM +0200, Thierry Fournier wrote:
> Hi,
>
> runtime errors doesn't provides the error line, in particular the memory
> error (out of memory)
>
> Please find a Lua patch in attachment.
> It provides backtrace condensed in one line.
Indeed it's much better. Given t
On Fri, Jun 08, 2018 at 06:20:21PM +0200, Willy Tarreau wrote:
> On Fri, Jun 08, 2018 at 04:31:30PM +0200, William Lallemand wrote:
> > That's great news!
> >
> > Here's the new patches. It shouldn't change anything to the fix, it only
> > changes the sigprocmask to pthread_sigmask.
>
> OK, I ca
On Fri, Jun 08, 2018 at 04:31:30PM +0200, William Lallemand wrote:
> That's great news!
>
> Here's the new patches. It shouldn't change anything to the fix, it only
> changes the sigprocmask to pthread_sigmask.
OK, I can merge them right now if you want. At the very least it will
kill a whole cl
On Fri, Jun 08, 2018 at 02:10:44PM +0200, William Dauchy wrote:
> On Thu, Jun 07, 2018 at 11:50:45AM +0200, William Lallemand wrote:
> > Sorry for the late reply, I manage to reproduce and fix what seams to be
> > the bug.
> > The signal management was not handled correctly with threads.
> > Could
Hello William L.,
On Thu, Jun 07, 2018 at 11:50:45AM +0200, William Lallemand wrote:
> Sorry for the late reply, I manage to reproduce and fix what seams to be the
> bug.
> The signal management was not handled correctly with threads.
> Could you try those patches and see if it fixes the problem?
On Wed, 6 Jun 2018 at 11:20, Willy Tarreau wrote:
> Hi Milan,
>
> On Wed, Jun 06, 2018 at 11:09:19AM +0200, Milan Petruzelka wrote:
> > Hi Willy,
> >
> > I've tracked one of connections hanging in CLOSE_WAIT state with tcpdump
> > over last night. It started at 17:19 like this:
> >
> > "Packe
Hi,
runtime errors doesn’t provides the error line, in particular the memory error
(out of memory)
Please find a Lua patch in attachment.
It provides backtrace condensed in one line.
Thierry
0001-MINOR-lua-Increase-debug-information.patch
Description: Binary data
On Thu, Jun 07, 2018 at 12:02:46PM +0200, Willy Tarreau wrote:
> On Thu, Jun 07, 2018 at 11:50:45AM +0200, William Lallemand wrote:
> > /* block signal delivery during processing */
> > +#ifdef USE_THREAD
> > + pthread_sigmask(SIG_SETMASK, &blocked_sig, &old_sig);
> > +#else
> > sigprocma
13 matches
Mail list logo