Bug #6915
closed
unbound logging not working after reboot or "Reset log files"
Added by idris budak over 7 years ago.
Updated about 7 years ago.
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)
- Assignee set to Renato Botelho
- 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
- 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).
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
- Status changed from Assigned to Feedback
PR merged, works fine. Will wait for it to be in snaps before one last test.
- Status changed from Feedback to Resolved
- Target version changed from 2.4.0 to 2.3.3
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.
- Project changed from pfSense Packages to pfSense
- Category changed from Unbound to DNS Resolver
Yep, that's better, thanks!
Also available in: Atom
PDF
Updated by 
Updated by Kill Bill 
Updated by 
Updated by 
Updated by