[MacPorts] #28619: bind9 @9.8.0_0 fails at startup with openssl error

MacPorts noreply at macports.org
Thu Mar 3 11:10:58 PST 2011


#28619: bind9 @9.8.0_0 fails at startup with openssl error
-------------------------------------+--------------------------------------
 Reporter:  dlb@…                    |       Owner:  dluke@…           
     Type:  defect                   |      Status:  new               
 Priority:  Normal                   |   Milestone:                    
Component:  ports                    |     Version:  1.9.2             
 Keywords:                           |        Port:  bind9             
-------------------------------------+--------------------------------------
Changes (by jmr@…):

  * owner:  macports-tickets@… => dluke@…
 * cc: dlb@… (removed)
  * port:  => bind9


Old description:

> I upgraded the bind9 port  to 9.8.0_0.  Now bind is failing at start up
> with the following error:
>

> Mar  3 10:41:33 gw3 named[8220]: starting BIND 9.8.0 -f -t /etc/namedb -u
> named -c /etc/named.conf
> Mar  3 10:41:33 gw3 named[8220]: built with '--prefix=/opt/local' '--
> mandir=/opt/local/share/man' '--with-openssl=/opt/local' '--with-
> libxml2=/opt/local' '--enable-threads' '--enable-ipv6'
> 'CC=/usr/bin/gcc-4.2' 'CFLAGS=-O2 -arch x86_64' 'LDFLAGS=-L/opt/local/lib
> -arch x86_64' 'CPPFLAGS=-I/opt/local/include' 'CXX=/usr/bin/g++-4.2'
> 'CXXFLAGS=-O2 -arch x86_64' 'FFLAGS=-O2 -m64'
> Mar  3 10:41:33 gw3 named[8220]: initializing DST: openssl failure
> Mar  3 10:41:33 gw3 named[8220]: exiting (due to fatal error)
>
> I am and have been running bind in a chroot environment, but this might
> be the trigger for the problem in this release.  Google turned up a
> Gentoo bug report  of the same failure that says it is supposed a due to
> running in a chroot environment.  Although supposedly it was fixed in
> 9.8.0_0 final. Here's the link:
>
> http://bugs.gentoo.org/show_bug.cgi?id=356519
>
> Let me know if you need more info.
>
> Thanks - David

New description:

 I upgraded the bind9 port  to 9.8.0_0.  Now bind is failing at start up
 with the following error:

 {{{
 Mar  3 10:41:33 gw3 named[8220]: starting BIND 9.8.0 -f -t /etc/namedb -u
 named -c /etc/named.conf
 Mar  3 10:41:33 gw3 named[8220]: built with '--prefix=/opt/local' '--
 mandir=/opt/local/share/man' '--with-openssl=/opt/local' '--with-
 libxml2=/opt/local' '--enable-threads' '--enable-ipv6'
 'CC=/usr/bin/gcc-4.2' 'CFLAGS=-O2 -arch x86_64' 'LDFLAGS=-L/opt/local/lib
 -arch x86_64' 'CPPFLAGS=-I/opt/local/include' 'CXX=/usr/bin/g++-4.2'
 'CXXFLAGS=-O2 -arch x86_64' 'FFLAGS=-O2 -m64'
 Mar  3 10:41:33 gw3 named[8220]: initializing DST: openssl failure
 Mar  3 10:41:33 gw3 named[8220]: exiting (due to fatal error)
 }}}
 I am and have been running bind in a chroot environment, but this might be
 the trigger for the problem in this release.  Google turned up a Gentoo
 bug report  of the same failure that says it is supposed a due to running
 in a chroot environment.  Although supposedly it was fixed in 9.8.0_0
 final. Here's the link:

 http://bugs.gentoo.org/show_bug.cgi?id=356519

 Let me know if you need more info.

 Thanks - David

--

Comment:

 Please also remember to preview and use WikiFormatting, and cc the
 maintainer. You do not need to be in cc when you are the reporter.

-- 
Ticket URL: <https://trac.macports.org/ticket/28619#comment:2>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list