On 4/11/2015 2:49 AM, Willy Tarreau wrote:
> As you have posted yourself, this has nothing to do with haproxy, it's a
> kernel crash (in the scheduler here). Your system is running a totally
> outdated and unmaintained kernel (2.6.35.14) which suffers from many bugs
> Now regarding your version
Hi David,
On Thu, Apr 09, 2015 at 04:01:44PM -0700, David Birdsong wrote:
> Ok, false alarm.
>
> We have corruption in our log parsing stream so that's what the rest of my
> week will be centered around.
OK, "cool" (for the rest of us). I was suspecting that the captures were
initialized too lat
Hi Andrew,
On Thu, Apr 09, 2015 at 08:55:20AM -0500, Andrew Hayworth wrote:
> Hi Willy -
>
> Apologies if this comes through multiple times; I'm having some mail
> difficulties.
I received it only once FYI.
> When I attempt to use %[path] in a log-format directive, I get the
> following errors:
On Fri, Apr 10, 2015 at 07:07:25AM -0600, Shawn Heisey wrote:
> I am having repeated crashes of haproxy 1.4.18, using a package in
> Fedora Core 14.
>
> Kernel log of crash:
> http://apaste.info/q5u
>
> slightly redacted haproxy config:
> http://apaste.info/ijJ
>
> Is this a known problem? When
On Wed, Apr 08, 2015 at 02:13:44AM +0200, Willy Tarreau wrote:
> Hi,
>
> On Tue, Apr 07, 2015 at 12:03:37PM -0400, CJ Ess wrote:
> > This is my first time submitting a modification to haproxy, so I would
> > appreciate feedback.
> >
> > We've been experimenting with using the stick tables feature
5 matches
Mail list logo
