Opened 8 years ago
Closed 7 years ago
#1931 closed defect (duplicate)
what zone config or file had problem?
Reported by: | jreed | Owned by: | |
---|---|---|---|
Priority: | medium | Milestone: | |
Component: | b10-auth | Version: | |
Keywords: | Cc: | ||
CVSS Scoring: | Parent Tickets: | ||
Sensitive: | no | Defect Severity: | N/A |
Sub-Project: | DNS | Feature Depending on Ticket: | |
Estimated Difficulty: | 4 | Add Hours to Ticket: | 0 |
Total Hours: | 0 | Internal?: | no |
Description
2012-05-01 22:36:15.132 ERROR [b10-auth.auth] AUTH_CONFIG_UPDATE_FAIL update of configuration failed: Server configuration failed: Parse failure for a valid RR at line 12
The logging should say what file or zone configuration had failure. On many zones (like 19) it may be difficult to notice. (By the way, named-checkzone didn't notice. The problem was accidental addition of $TTL entry at that line 12.)
Subtickets
Change History (5)
comment:1 Changed 8 years ago by shane
- Milestone changed from New Tasks to Next-Sprint-Proposed
comment:2 Changed 8 years ago by jinmei
comment:3 Changed 8 years ago by muks
See bug #1932 for what the "like 19" means in the description.
comment:4 Changed 7 years ago by jinmei
recorded it in #2035 for tracking this issue (if not "automatically" resolved).
closing this one.
comment:5 Changed 7 years ago by jinmei
- Resolution set to duplicate
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
I don't think we should solve this particular problem in the one-by-one manner
now that we include generic zone loading in our middle term goals.