Date: Mon, 4 May 2020 23:32:10 +0200 From: Christoph Moench-Tegeder <cmt@burggraben.net> To: freebsd-ports@freebsd.org Subject: Re: Bind 9.16 port error still lingers Message-ID: <20200504213210.GA23232@elch.exwg.net> In-Reply-To: <20200504031008.GA93877@doctor.nl2k.ab.ca> References: <20200502140501.GA16385@doctor.nl2k.ab.ca> <20200502143210.GA4453@elch.exwg.net> <20200502151636.GA22397@doctor.nl2k.ab.ca> <20200502165318.GB4453@elch.exwg.net> <20200502172907.GA59662@doctor.nl2k.ab.ca> <20200503133239.GA14877@elch.exwg.net> <20200504031008.GA93877@doctor.nl2k.ab.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
## The Doctor via freebsd-ports (freebsd-ports@freebsd.org): > Well I did find a dead zone and still no dice. That's unfortunate. Completely nothing in config, zones, journals (if any)? Then it's either something totally obvious (obvious like an elephant in the room) which we're missing; or something is completely borked on your system. (BTW, where are you getting your packages from?) That would be a good point to rebuild bind with debug symbols, so we can get a meaningful stack trace; and if that narrows things down perhaps some tactical log statements. Or you could try cutting your config down to the bare minimum and if bind starts, work backwawrds from there. Whatever you're more comfortable with. Regards, Christoph -- Spare Space
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200504213210.GA23232>