bind9 incorrectly logs "starting maxtime timer" debug messages as errors

Bug #2012058 reported by Ondřej Hošek
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bind9 (Ubuntu)
Fix Released
Fix Released

Bug Description

bind9 version 1:9.18.1-1ubuntu1.3, when performing zone transfers, incorrectly logs a debug message ("starting maxtime timer") with an ERROR log level.

Example of such a message:

Fri Mar 17 08:21:02 CET 2023 : named error: client @0x7f001ddc4e18 ( transfer of '': starting maxtime timer 7200000 ms

This has been acknowledged upstream:

I kindly request that the fix be pulled into Ubuntu 22.04 LTS (jammy). Thanks in advance!

description: updated
Revision history for this message
Sergio Durigan Junior (sergiodj) wrote :

Thanks for taking the time to report this bug.

We're currently working on updating the bind9 version that's shipped in Ubuntu Jammy, and this bug will be fixed by this update. I am subscribing the person responsible for this effort so that she's aware of the bug and can close when the new bind9 reaches jammy-updates. Thanks.

Changed in bind9 (Ubuntu):
status: New → Fix Released
Changed in bind9 (Ubuntu Jammy):
status: New → Triaged
Revision history for this message
Lena Voytek (lvoytek) wrote :

9.18.12 has been released to Jammy now so this should be fixed. If you still experience this issue please let me know.


Changed in bind9 (Ubuntu Jammy):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.