Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    unbound sending info and debug to syslog....

    Scheduled Pinned Locked Moved DHCP and DNS
    4 Posts 2 Posters 681 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      nrf
      last edited by nrf

      I'm sending unbound logs to a remote syslog destination (QRadar). I have set verbosity to 3 yet it is emitting info: and debug: logs. this is driving my QRadar system crazy as it has to parse and store all that junk. any suggestions?
      thanks in advance!
      nrf

      (FWIW turning off logging to remote in log settings didn't propagate to unbound, I had to add use-syslog: no to the custom properties to null it.)

      N GertjanG 2 Replies Last reply Reply Quote 0
      • N
        nrf @nrf
        last edited by

        @nrf barring any fixes to unbound I found a way to filter these in QRadar using 'routing' rule to drop.
        thanks for your help

        1 Reply Last reply Reply Quote 0
        • GertjanG
          Gertjan @nrf
          last edited by

          @nrf said in unbound sending info and debug to syslog....:

          driving my QRadar system crazy as it has to parse and store all that junk. any suggestions?

          Is related to :

          @nrf said in unbound sending info and debug to syslog....:

          I have set verbosity to 3

          Lower that settings to have less verbosity.

          No "help me" PM's please. Use the forum, the community will thank you.
          Edit : and where are the logs ??

          N 1 Reply Last reply Reply Quote 0
          • N
            nrf @Gertjan
            last edited by

            @Gertjan sorry but setting it to zero does not fix the problem. it should be debugging only at HIGH levels of verbosity.
            I have it set at 3 for a reason in any case. a documented feature is that different verbosity levels provide certain information.

            maybe pfsense has included a developer build of unbound or the developer forgot to turn off some test ifdef's that force debug.
            problem solved for now but "sloppy"....

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.