Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 633
    • Issues 633
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 90
    • Merge requests 90
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • 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 ProjectsISC Open Source Projects
  • BINDBIND
  • Issues
  • #3924
Closed
Open
Issue created Mar 06, 2023 by Tom Krizek@tkrizekMaintainer

missing messages in `dnstap` system test after query failure

In job #3215476, the tests expects two UDP messages in the dnstap output - CLIENT_QUERY and CLIENT_RESPONSE after querying for a.example. The dnstap.out doesn't contain any messages.

I:dnstap:checking reopened unix socket message counts
I:dnstap:checking UDP message counts
I:dnstap:ns4 0 expected 2
I:dnstap:failed
I:dnstap:checking TCP message counts
I:dnstap:checking AUTH_QUERY message counts
I:dnstap:checking AUTH_RESPONSE message counts
I:dnstap:checking CLIENT_QUERY message counts
I:dnstap:ns4 0 expected 1
I:dnstap:failed
I:dnstap:checking CLIENT_RESPONSE message counts
I:dnstap:ns4 0 expected 1
I:dnstap:failed

Inspecting the ns4/named.run, it looks like reopening the dnstap socket happened as expected. Afterwards, a query for a.example was received. For some reason, the query failed to resolve. It looks like before the server had a chance to respond to the query, it was shut down. The dig.out is also empty.

06-Mar-2023 14:48:09.490 received control channel command 'dnstap -reopen'
06-Mar-2023 14:48:09.490 reopening dnstap destination 'dnstap.out'
06-Mar-2023 14:48:09.550 client @0x7f1bed89ff68 10.53.0.1#59720: UDP request
06-Mar-2023 14:48:09.550 query client=0x7f1bed89ff68 thread=0x7f1c197ff700(a.example/A): client attr:0x2302, query attr:0x703, restarts:0, origqname:a.example, timer:0, authdb:0, referral:0
06-Mar-2023 14:48:09.550 query client=0x7f1bed89ff68 thread=0x7f1c197ff700(a.example/A): query_gotanswer: unexpected error: failure
06-Mar-2023 14:48:09.554 client @0x7f1bed89ff68 10.53.0.1#59720 (a.example): query failed (failure) for a.example/IN/A at query.c:7779
06-Mar-2023 14:48:16.306 shutting down
06-Mar-2023 14:48:16.310 client @0x7f1bed89ff68 10.53.0.1#59720: freeing client
06-Mar-2023 14:48:16.310 query client=0x7f1bed89ff68 thread=0x7f1c20fff700(<unknown-query>): query_reset
06-Mar-2023 14:48:16.322 closing dnstap
Assignee
Assign to
Time tracking