bind10-devel-20110119 b10-resolver failure

Waitman Gobble uzimac at da3m0n8t3r.com
Mon Feb 13 07:31:00 UTC 2012


Waitman Gobble <uzimac at da3m0n8t3r.com> wrote ..
> Spain, Dr. Jeffry A. <spainj at countryday.net> wrote ..
> > I rebuilt with Boost 1.46.1, Botan 1.8.13, Sqlite 3.7.7, and Python 3.2.2, which
> > are the versions of this software in the Ubuntu Oneiric packages. The same error
> > 'b10-resolver ended with status 11' is occurring. Tomorrow I will work on replacing
> > these one at a time with the Oneiric packages themselves until I get it working
> > again. I think there's probably some dependency I'm not aware of yet. Jeff.
> > _______________________________________________
> > bind10-users mailing list
> > bind10-users at lists.isc.org
> > https://lists.isc.org/mailman/listinfo/bind10-users
> 
> I'm getting the same results on Ubuntu with 2012-01-19. IMHO It's probably better
> to try 2012-01-27, just an idea.
> 
> Linux waitman-VirtualBox 2.6.38-11-generic #50-Ubuntu SMP Mon Sep 12 21:18:14 UTC
> 2011 i686 i686 i386 GNU/Linux
> 
> 
> Here's the build log  (without most of the make output)
> 
> https://www.uzimac.com/ubuntu-b10log.txt
> 
> 
> Here's the server run / test.
> 
> https://www.uzimac.com/ubuntu-b10run.txt
> 
> 
> 
> You may wish to consider adding the checksum verification to the doc.. 
> 
> ie,
> 
> # gpg Botan-1.10.1.tbz.asc
> gpg: Signature made Mon 11 Jul 2011 10:32:33 AM PDT using RSA key ID EFBADFBC
> # gpg --keyserver pgpkeys.mit.edu --recv-key EFBADFBC
> # gpg Botan-1.10.1.tbz.asc
> gpg: Signature made Mon 11 Jul 2011 10:32:33 AM PDT using RSA key ID EFBADFBC
> gpg: Good signature from "Botan Distribution Key"
> # gpg --verify Botan-1.10.1.tbz.asc Botan-1.10.1.tbz
> gpg: Signature made Mon 11 Jul 2011 10:32:33 AM PDT using RSA key ID EFBADFBC
> gpg: Good signature from "Botan Distribution Key"
> 
> (you can trust key key if you wanna)
> 
> # sha1sum boost_1_48_0.tar.bz2
> # sha1sum log4cplus-1.0.4.tar.bz2
> # sha1sum sqlite-autoconf-3071000.tar.gz
> 
> etc
> 
> 
> Hopefully bootstrapping a gcc build isn't the solution :-) That's a major task
> for reals, I recently wrote up a three page process to upgrade gcc tp latest release
> on a CentOS 5.7 machine. But the 5.7 in CentOS really means everything is 5 to
> 7 years old. :) Shouldn't be necessary for bind10 though me thinks,
> 
> Have fun.
> 
> 
> -- 
> Waitman Gobble
> San Jose California USA

anyway, looking at the bind10 log this is suspect:
2012-02-12 22:40:14.594 WARN  [b10-resolver.resolver] RESOLVER_NO_ROOT_ADDRESS no root addresses available

if it's not getting hints to root that could cause failure.. 
i'll take a look tomorrow i'm beat.


-- 
Waitman Gobble
San Jose California USA



More information about the bind10-users mailing list