[Bug 247950] databases/lmdb: lmdb-0.9.24_2,1 causes problems with bind dynamic zones after reload
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Mon Jul 13 14:10:31 UTC 2020
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247950
Bug ID: 247950
Summary: databases/lmdb: lmdb-0.9.24_2,1 causes problems with
bind dynamic zones after reload
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: Individual Port(s)
Assignee: delphij at FreeBSD.org
Reporter: david at isnic.is
Assignee: delphij at FreeBSD.org
Flags: maintainer-feedback?(delphij at FreeBSD.org)
Since lmdb-0.9.24_2,1 bind with dynamic zones has problems after HUP. This
happens in our setup every night when newsyslog runs. It seems the fix in
#244493 may have issues.
Steps to reproduce:
* Install bind (bind911 and bind916 both tested)
* Add "allow-new-zones yes;" under options section of
/usr/local/etc/namedb/named.conf
* service named restart
* kill -HUP `cat /var/run/named/pid`
* rndc -k /usr/local/etc/namedb/rndc.key addzone 'example.org {type slave;
masters { 127.0.0.1;}; file "/usr/local/etc/namedb/slave/example.org";};'
* Check /var/log/messages, find errors like:
Jul 13 14:05:57 davidtest named[74867]: mdb_txn_begin: Invalid argument
Jul 13 14:05:57 davidtest named[74867]: mdb_txn_begin: Invalid argument
We've downgraded to lmdb-0.9.24_1,1 which does not have this problem.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list