Opened 8 years ago

Closed 8 years ago

#1786 closed defect (fixed)

ZONEMGR_NO_MASTER_ADDRESS -- please submit a bug report

Reported by: jreed Owned by:
Priority: medium Milestone:
Component: Unclassified Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: Medium
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 5 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

Logs have:

2012-03-17 00:26:51.q INFO  [b10-xfrout.xfrout] XFROUT_NOTIFY_COMMAND received command to send notifies for bind10.isc.org./IN
2012-03-17 00:26:51.q INFO  [b10-xfrout.xfrout] XFROUT_NOTIFY_COMMAND received command to send notifies for bind10.isc.org./IN
2012-03-17 00:26:51.q ERROR [b10-zonemgr.zonemgr] ZONEMGR_NO_MASTER_ADDRESS internal BIND 10 command did not contain address of master
2012-03-17 00:26:51.q ERROR [b10-zonemgr.zonemgr] ZONEMGR_NO_MASTER_ADDRESS internal BIND 10 command did not contain address of master
% ZONEMGR_NO_MASTER_ADDRESS internal BIND 10 command did not contain address of master
A command received by the zone manager from the Auth module did not
contain the address of the master server from which a NOTIFY message
was received.  This may be due to an internal programming error; please
submit a bug report.

So opening bug report as requested.

Subtickets

Change History (8)

comment:1 Changed 8 years ago by jreed

This happens automatically (not manually using retransfer command).

The zone transfer in is still working.

I was told in jabber: "the message text should still be fixed, because if you ask to retransfer an unknown zone it produces this message as well."

comment:2 Changed 8 years ago by jinmei

So, what's the goal of this ticket? Just update the log message?

comment:3 Changed 8 years ago by shane

  • Defect Severity changed from N/A to Medium
  • Milestone changed from New Tasks to Next-Sprint-Proposed

Well, we should probably completely remove the log message in the case where we ask to retransfer an unknown zone.

comment:4 Changed 8 years ago by shane

At the very least, we should output some extra information like where the invalid notify came from and perhaps any other information about the message that we have lying around (we should have the zone name and class, according to the code).

comment:5 Changed 8 years ago by shane

See also #1834.

comment:6 Changed 8 years ago by muks

This bug would very well have happened due to wrong handling of the ZONE_NEW_DATA_READY_CMD as a "notify" command (see bug #2023). This would have caused the ZONEMGR_NO_MASTER_ADDRESS log to be generated.

#2023 fix is now in master, so please test if this issue occurs still.

comment:7 Changed 8 years ago by jreed

This log message went away once I installed and restarted new version today. Yesterday it happened 2860 times (every 30 seconds).

comment:8 Changed 8 years ago by jreed

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.