Hi Marcel,
I looked around but the function is in general by upstream not defined to be
synchronous.
Since rndc is only a network ping to the server to dump, and even the regular
dumps are defined to take place at up to 15 minutes delay (for efficiency) this
might happen here as well.
Seeing old issus as:
1594.»··[bug]»··»···'rndc dumpdb' could prevent named from answering
»···»···»···queries while the dump was in progress. [RT #10565]
I assume they would not like it to be sync.
There are log entries you could watch:
I found in ns_server_dumpdb -> dumpdone:
fprintf(dctx->fp, "; Dump complete\n");
isc_log_write(ns_g_lctx, NS_LOGCATEGORY_GENERAL,
NS_LOGMODULE_SERVER, ISC_LOG_ERROR,
"dumpdb failed: %s", dns_result_totext(result));
Not sure were they show up without checking.
I didn't find any Debian or Ubuntu Delta that would cause this.
IMHO the rndc utility could grow a feature to detect that the dump is
done. Guarded behind a new opt-in flag that would cause no regression to
other users, but never the less it would be a an upstream bug IMHO.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692514
Title:
dumpdb incomplete when used in scripts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1692514/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
