Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
BIND
BIND
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 580
    • Issues 580
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 110
    • Merge Requests 110
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ISC Open Source Projects
  • BINDBIND
  • Issues
  • #1067

Closed
Open
Opened Jun 04, 2019 by Michael McNally@McNallyDeveloper

Underflow in Stats Channel RecursClients value?

Summary

It looks like we may have an underflow condition in the Stats Channel RecursClients value

BIND version used

Reported by a customer using 9.11.7-S1

What is the current bug behavior?

A customer who is using the statistics channel to monitor BIND behavior tells us:

Hello,

We have our DNS servers configured to collect stats. We have metrics servers collect the data so it can be displayed.

The data for the RecursClients stat randomly is a very high number. See below.

This is happening on a number of my servers.

name="RecursClients">18446744073709551440

name="RecursClients">18446744073709551426

From another server.

name="RecursClients">18446744073709551518

When I do an "rndc reconfig" the counter will clear out. But in a few seconds it will jump back up.

What is the expected correct behavior?

Obviously the customer does not actually have on the order of 2 ^ 64 recursive clients.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: isc-projects/bind9#1067