I recently noticed that I couldn't get my bind servers to start if they do remote logging because they try to resolve the remote logger before starting. Since I was bringing up the network after a power outage there were no running bind servers anywhere. The remote sysloging is done like this in syslog-ng.conf: destination syslog { tcp("syslog" port(5000)); }; uk-ns1 src # /etc/init.d/named start Error resolving hostname; host='syslog' * Starting syslog-ng ... Error resolving hostname; host='syslog' No destination address set; * Failed to start syslog-ng [ !! ] uk-ns1 src # Workaround: uk-ns1 src # /etc/init.d/named --nodeps start * Starting chrooted named ... [ ok ] uk-ns1 src # emerge --version Portage 2.1.4.4 (default-linux/x86/2006.1/server, gcc-4.1.2, glibc-2.6.1-r0, 2.6.24-gentoo-r7 i686)
According to the changelog, this issue has been fixed in 2.1_beta1, released in April.
(In reply to comment #1) > According to the changelog, this issue has been fixed in 2.1_beta1, released in > April. > so we can close this one, right?
(In reply to comment #2) > (In reply to comment #1) > > According to the changelog, this issue has been fixed in 2.1_beta1, released in > > April. > > > > so we can close this one, right? > Yeah, I think so. I'm not the maintainer though... ;-)
(In reply to comment #3) > (In reply to comment #2) > > (In reply to comment #1) > > > According to the changelog, this issue has been fixed in 2.1_beta1, released in > > > April. > > > > > > > so we can close this one, right? > > > > Yeah, I think so. I'm not the maintainer though... ;-) > doing so then ;)
