Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation or implementation of "verbosity" option #495

Closed
he32 opened this issue May 27, 2021 · 1 comment
Closed

Documentation or implementation of "verbosity" option #495

he32 opened this issue May 27, 2021 · 1 comment
Assignees

Comments

@he32
Copy link
Contributor

he32 commented May 27, 2021

Describe the bug
The documentation for the verbosity option says:

       verbosity: <number>
              The verbosity number, level 0 means no verbosity, only errors.
              Level 1 gives operational information. Level 2 gives detailed
              operational information. Level 3 gives query level information,
              output per query.  Level 4 gives algorithm level information.
              Level 5 logs client identification for cache misses.  Default is
              level 1.  The verbosity can also be increased from the
              commandline, see unbound(8).

While looking at an operational problem, I wanted to get "more detailed operational information",
so I set verbosity: 2 in unbound.conf, but to my surprise, I got "query level information" in the
log, like this:

May 26 20:01:53 dr2 unbound: [13154:0] info: start of service (unbound 1.13.1).
May 26 20:02:12 dr2 unbound: [13154:0] info: control cmd:  stats
May 26 20:02:19 dr2 unbound: [13154:0] info: resolving r3---sn-ovgq0oxu-5goe.googlevideo.com. A IN
May 26 20:02:19 dr2 unbound: [13154:0] info: priming . IN NS
May 26 20:02:19 dr2 unbound: [13154:0] info: resolving E.ROOT-SERVERS.NET. AAAA IN
May 26 20:02:19 dr2 unbound: [13154:0] info: priming . IN NS
May 26 20:02:19 dr2 unbound: [13154:0] info: resolving G.ROOT-SERVERS.NET. AAAA IN
May 26 20:02:19 dr2 unbound: [13154:0] info: priming . IN NS
May 26 20:02:19 dr2 unbound: [13154:0] info: response for . NS IN
May 26 20:02:19 dr2 unbound: [13154:0] info: reply from <.> 2001:500:2f::f#53
May 26 20:02:19 dr2 unbound: [13154:0] info: query response was ANSWER
May 26 20:02:19 dr2 unbound: [13154:0] info: priming successful for . NS IN
May 26 20:02:19 dr2 unbound: [13154:2] info: resolving init.ess.apple.com. TYPE65 IN
May 26 20:02:19 dr2 unbound: [13154:2] info: resolving init.ess.apple.com. A IN
May 26 20:02:19 dr2 unbound: [13154:2] info: resolving a239.gi3.akamai.net. TYPE65 IN
May 26 20:02:19 dr2 unbound: [13154:2] info: resolving a239.gi3.akamai.net. A IN
May 26 20:02:19 dr2 unbound: [13154:2] info: response for init.ess.apple.com. TYPE65 IN

etc.

So the question here is whether it's the code or the documentation which is wrong;
my bet is on the code.

To reproduce
Steps to reproduce the behavior:

  1. Configure unbound 1.13.1 with verbosity: 2
  2. See query-level information in the log, which is unexpected.

Expected behavior
I would have expected "query level information" only when verbosity >= 3.

System:

  • Unbound version: 1.13.1
  • OS: NetBSD
  • unbound -V output:
Version 1.13.1

Configure line: --enable-allsymbols --with-libexpat=/usr --with-libevent=/usr --enable-event-api --with-ssl=/usr --with-pidfile=/var/run/unbound/unbound.pid --sysconfdir=/usr/pkg/etc --with-libnghttp2 --enable-gost --enable-sha2 --prefix=/usr/pkg --build=x86_64--netbsd --host=x86_64--netbsd --mandir=/usr/pkg/man --enable-option-checking=yes
Linked libs: pluggable-libevent 2.1.8-stable (it uses kqueue), OpenSSL 1.1.1k  25 Mar 2021
Linked modules: dns64 respip validator iterator

BSD licensed, see LICENSE in source package for details.
Report bugs to unbound-bugs@nlnetlabs.nl or https://github.com/NLnetLabs/unbound/issues

Additional information
Should be clear from the above.

@gthess
Copy link
Member

gthess commented Jun 21, 2021

Hi,
I don't think this is an issue.
Well, it could be an issue for the man page to include that really short information per query is also included in the "detailed operational information".

These were originally on the next level which "gives query level information", but after operator demand the current level with detailed operational information was created (f3525b2).

@gthess gthess closed this as completed in 896357a Jun 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants