Re: RPM [was: Re: bind dies with assertion failure]

2012-07-03 Thread Warren Kumari
On Jul 3, 2012, at 10:58 AM, wbr...@e1b.org wrote: > Jan-Piet wrote on 07/03/2012 10:41:20 AM: > >> Building BIND is easy; turning it into an installable RPM not so. >> I highly recommend fpm [1] which makes building an RPM trivial. :) > > Any advice or tricks for making a DEB for Ubuntu? > >

Re: RPM [was: Re: bind dies with assertion failure]

2012-07-03 Thread Jan-Piet Mens
> > Building BIND is easy; turning it into an installable RPM not so. > > I highly recommend fpm [1] which makes building an RPM trivial. :) > > Any advice or tricks for making a DEB for Ubuntu? Yes: use fpm. :) > So far my plan was to copy the source directory to each server and just > run "ma

Re: RPM [was: Re: bind dies with assertion failure]

2012-07-03 Thread WBrown
Jan-Piet wrote on 07/03/2012 10:41:20 AM: > Building BIND is easy; turning it into an installable RPM not so. > I highly recommend fpm [1] which makes building an RPM trivial. :) Any advice or tricks for making a DEB for Ubuntu? So far my plan was to copy the source directory to each server and

RPM [was: Re: bind dies with assertion failure]

2012-07-03 Thread Jan-Piet Mens
> While it's always better to compile and install from the latest > stable version, it's also nice to use their package management > system especially when you have to deal with multiple systems. Building BIND is easy; turning it into an installable RPM not so. I highly recommend fpm [1] which mak

RE: bind dies with assertion failure

2012-07-03 Thread Lightner, Jeff
g] On Behalf Of Oscar Ricardo Silva Sent: Tuesday, July 03, 2012 10:33 AM To: bind-users@lists.isc.org Subject: Re: bind dies with assertion failure (Sorry, forgot to include the right Subject line so re-sending) > Message: 1 > Date: Mon, 02 Jul 2012 17:40:51 -0500 > From: Oscar

Re: bind dies with assertion failure

2012-07-03 Thread Oscar Ricardo Silva
(Sorry, forgot to include the right Subject line so re-sending) > Message: 1 > Date: Mon, 02 Jul 2012 17:40:51 -0500 > From: Oscar Ricardo Silva > To: bind-users@lists.isc.org > Subject: Re: bind dies with assertion failure > Message-ID: <4ff22373.2000...@mail.utexas.edu&

Re: bind dies with assertion failure

2012-07-03 Thread Oscar Ricardo Silva
07/03/2012 01:16 AM, Oscar Ricardo Silva wrote: >> I *THINK* I found the reason for why we're exposed to this bug ... >> It would appear that Redhat based their BIND package on 9.8.2rc1. >> Guess where the patch for this bug was applied? 9.8.2rc2. > Are you sure about this? > From what I can se

Re: bind dies with assertion failure

2012-07-03 Thread WBrown
Oscar Ricardo Silva wrote on 07/02/2012 06:40:51 PM: > The reason I'm running is that we're currently running the stock version > of BIND available with RHEL6. It's their policy to backport patches and > if there's a patch available then they may apply it faster rather than > deploying a new

RE: bind dies with assertion failure

2012-07-03 Thread Lightner, Jeff
dies with assertion failure On 07/03/2012 01:16 AM, Oscar Ricardo Silva wrote: > I *THINK* I found the reason for why we're exposed to this bug ... It > would appear that Redhat based their BIND package on 9.8.2rc1. Guess > where the patch for this bug was applied? 9.8.2rc2. Are

Re: bind dies with assertion failure

2012-07-03 Thread Phil Mayers
On 07/03/2012 01:16 AM, Oscar Ricardo Silva wrote: I *THINK* I found the reason for why we're exposed to this bug ... It would appear that Redhat based their BIND package on 9.8.2rc1. Guess where the patch for this bug was applied? 9.8.2rc2. Are you sure about this? From what I can see in ou

Re: bind dies with assertion failure

2012-07-02 Thread Evan Hunt
On Mon, Jul 02, 2012 at 07:16:40PM -0500, Oscar Ricardo Silva wrote: > I *THINK* I found the reason for why we're exposed to this bug ... It > would appear that Redhat based their BIND package on 9.8.2rc1. Guess > where the patch for this bug was applied? 9.8.2rc2. Sigh. It wouldn't be the fi

Re: bind dies with assertion failure

2012-07-02 Thread Oscar Ricardo Silva
I *THINK* I found the reason for why we're exposed to this bug ... It would appear that Redhat based their BIND package on 9.8.2rc1. Guess where the patch for this bug was applied? 9.8.2rc2. Oscar On 07/02/2012 05:47 PM, Evan Hunt wrote: I can't answer for RedHat, but this bug fix was in

Re: bind dies with assertion failure

2012-07-02 Thread Evan Hunt
I can't answer for RedHat, but this bug fix was included in BIND 9.8.2. 3284. [bug] Address race conditions with the handling of rbtnode.deadlink. [RT #27738] On Mon, Jul 02, 2012 at 05:40:51PM -0500, Oscar Ricardo Silva wrote: > I may have missed something but

Re: bind dies with assertion failure

2012-07-02 Thread Oscar Ricardo Silva
Message: 6 Date: Tue, 14 Feb 2012 14:16:05 -0600 From: Michael Graff To: Alex Cc:bind-users@lists.isc.org Subject: Re: bind dies with assertion failure Message-ID:<9a4c0b81-4221-465a-a952-3523bd576...@isc.org> Content-Type: text/plain; charset=us-ascii It is a known issue, and is indeed a

Re: bind dies with assertion failure

2012-02-14 Thread Michael Graff
It is a known issue, and is indeed a bug. We're working on it already, so stay tuned. --Michael On Feb 14, 2012, at 12:44 PM, Alex wrote: > Hi, > > I have a fedora16 x86_64 box and named keeps dying with an assertion failure: > > 14-Feb-2012 13:24:41.137 general: critical: rbtdb.c:1619: > IN

bind dies with assertion failure

2012-02-14 Thread Alex
Hi, I have a fedora16 x86_64 box and named keeps dying with an assertion failure: 14-Feb-2012 13:24:41.137 general: critical: rbtdb.c:1619: INSIST(!((void *)((node)->deadlink.prev) != (void *)(-1))) failed 14-Feb-2012 13:24:41.137 general: critical: exiting (due to assertion failure) This is bin