Changes between Initial Version and Version 2 of Ticket #28619
- Timestamp:
- Mar 3, 2011, 7:10:57 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #28619
- Property Cc dlb@… removed
- Property Owner changed from macports-tickets@… to dluke@…
- Property Port bind9 added
-
Ticket #28619 – Description
initial v2 1 1 I upgraded the bind9 port to 9.8.0_0. Now bind is failing at start up with the following error: 2 2 3 3 {{{ 4 4 Mar 3 10:41:33 gw3 named[8220]: starting BIND 9.8.0 -f -t /etc/namedb -u named -c /etc/named.conf 5 5 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' 6 6 Mar 3 10:41:33 gw3 named[8220]: initializing DST: openssl failure 7 7 Mar 3 10:41:33 gw3 named[8220]: exiting (due to fatal error) 8 8 }}} 9 9 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: 10 10 … … 14 14 15 15 Thanks - David 16 17