On 2/12/2016 11:09 μμ, Pieter Lexis wrote:
This is because the systemd-journal is forwarded to syslog. You will need to
remove the --disable-syslog flag from the PowerDNS Exec command in the service
file to make PowerDNS*itself* log to syslog.
Thank you Pieter,
Your suggestion did the tric
Hi Nick,
On Thu, 1 Dec 2016 23:11:04 +0200
Nikolaos Milas wrote:
> In my system, rsyslog is in fact enabled and working. For example,
> openldap which writes to local4 (per the default configuration) works
> fine (via local4).
>
> In any case, the log entries *do* reach /var/log/messages, as I
On 1/12/2016 7:47 μμ, Pieter Lexis wrote:
On CentOS 7, logging to syslog is disabled in the systemd unit file. You could
ship the message via the systemd-journal_or_ create an override unit file to
enable syslog.
Thank you Pieter for your reply,
In my system, rsyslog is in fact enabled and
Hi Nikolaos,
On Thu, 1 Dec 2016 17:35:19 +0200
Nikolaos Milas wrote:
> I have just started working with PDNS 4.0.1 (with LDAP backend),
> installed on CentOS 7 from the suggested repo.
>
> Installation went fine, but I am facing this problem:
>
> No matter how I try, pdns (and pdns-recursor)
Hello,
I have just started working with PDNS 4.0.1 (with LDAP backend),
installed on CentOS 7 from the suggested repo.
Installation went fine, but I am facing this problem:
No matter how I try, pdns (and pdns-recursor) insists on logging to
/var/log/messages and not to the configured facilit
