Project

General

Profile

Actions

Bug #6915

closed

unbound logging not working after reboot or "Reset log files"

Added by idris budak about 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Normal
Category:
DNS Resolver
Target version:
Start date:
11/11/2016
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.3.2
Affected Architecture:

Description

After "reboot the machine" or "Status => System Logs => Settings" => "Reset log files" then unbound logs are not sending to "resolver.log" or rsyslog.

After restarting the unbound service then logs are okey.

In version: 2.3.2-RELEASE-p1 (amd64)

Actions #1

Updated by Jim Thompson almost 5 years ago

  • Assignee set to Renato Botelho
Actions #2

Updated by Kill Bill almost 5 years ago

The "reset log files" issue should be fixed by https://github.com/pfsense/pfsense/pull/3284

As for unbound logging not working after reboot, that's definitely not something I could reproduce anywhere.

Actions #3

Updated by Renato Botelho almost 5 years ago

  • Status changed from New to Feedback
  • Priority changed from High to Normal
  • Target version set to 2.4.0
  • % Done changed from 0 to 100

PR has been merged

Actions #4

Updated by Jim Pingle almost 5 years ago

  • Status changed from Feedback to Assigned

It works from the Settings tab if you reset all log files, but it doesn't work if you clear the log specifically while looking at the resolver tab (Click the wrench, then click Clear Log).

Actions #5

Updated by Kill Bill almost 5 years ago

Jim Pingle wrote:

It works from the Settings tab if you reset all log files, but it doesn't work if you clear the log specifically while looking at the resolver tab (Click the wrench, then click Clear Log).

https://github.com/pfsense/pfsense/pull/3383

Actions #6

Updated by Jim Pingle almost 5 years ago

  • Status changed from Assigned to Feedback

PR merged, works fine. Will wait for it to be in snaps before one last test.

Actions #7

Updated by Jim Pingle almost 5 years ago

  • Status changed from Feedback to Resolved

Works

Actions #8

Updated by Jim Pingle almost 5 years ago

  • Target version changed from 2.4.0 to 2.3.3
Actions #9

Updated by Phillip Davis almost 5 years ago

This one shows up under "pfSense packages". Maybe because the category is set to "Unbound".
Other "modern" unbound issues have category "DNS Resolver"
Might e useful to correct for auto-generating reports.

Actions #10

Updated by Jim Pingle almost 5 years ago

  • Project changed from pfSense Packages to pfSense
  • Category changed from Unbound to DNS Resolver

Yep, that's better, thanks!

Actions

Also available in: Atom PDF