Project

General

Profile

Bug #9037

Unbound not logging to syslog after reboot

Added by Patrick Clara 5 months ago. Updated 5 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
DNS Resolver
Target version:
-
Start date:
10/12/2018
Due date:
% Done:

0%

Estimated time:
Affected Version:
Affected Architecture:

Description

On my current installation (2.4.4-RELEASE (amd64)) unbound does not log to syslog after a reboot until unbound is restarted manually.
Might be related to https://redmine.pfsense.org/issues/6915

I have unbound logging queries on this machine which has a good amount of traffic. All the pfsense logging is also sent to syslog-ng.
From the syslog-ng logs, which start at the point where the syslog-ng package is started after a reboot, i see unbound actually logging queries for a few seconds.
The last query is logged immediately before syslogd seems to be restarted (for whatever reason).
After the point where "Bootup complete" is logged no other unbound logs show up.

The log after reboot from the syslog-ng startup until "Bootup complete" is attached.

syslog-ng.txt (4.36 KB) syslog-ng.txt Patrick Clara, 10/12/2018 02:57 AM

History

#1 Updated by Patrick Clara 5 months ago

Restarting syslogd from Status -> Services in the web UI also causes unbound to stop logging.

Also available in: Atom PDF