Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 532
    • Issues 532
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 100
    • Merge requests 100
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • BINDBIND
  • Issues
  • #1074

Closed
Open
Created Jun 06, 2019 by Brian Conry@bconryContributor

underflow in stats channel stale cached RRSIG gauge [ISC-support #14769]

A customer running a Supported Preview build has started seeing:

<rrset><name>#NS</name>
<counter>18446744073709551615</counter></rrset>

<rrset><name>#RRSIG</name>
<counter>18446744073709551615</counter></rrset>
</cache>

The <rrsig> elements are part of the block that measures the current number of records in the cache by RRTYPE, and the # prefix on the RRTYPE name indicates that these are "stale" records. By the version reported these are supposed to track the number of records that could be used by the serve-stale feature (if enabled).

An underflow on the stat seems the most likely explanation.

Assignee
Assign to
Time tracking