[389-users] Re: errors messages in /var/log/messges
On 4 Mar 2020, at 20:17, Mitja Mihelič <mitja.mihelic(a)arnes.si>
wrote:
H!
We have set up a new 389DS instance (389-ds-1.2.2-6.el7.noarch) on CentOS7. Messages from
the "errors" log file are also getting written into /var/log/messages.
The instances (389-ds-1.2.2-1.el6.noarch) on CentOS6 do not do that.
I have checked the rsyslog facilities local0-local7 and none of them are responsible.
What could be causing this?
Hi there,
Messages that go to the error log functions in directory server are also echoed to the
processes stderr - on RHEL7 since this uses system, stderr is sent to the journal, which
in turn then proxies to /var/log/messages.
Details about this can be seen in:
https://www.freedesktop.org/software/systemd/man/systemd.exec.html#
Section "logging and standard input/output".
Note the items "StandardOutput=" and "StandardError=" which default to
"journal". If you want to stop this behaviour you can do:
systemctl edit dirsrv(a)instance.service.
Then add the lines:
[Service]
StandardError=null
This is a per-server and per-service custom override, so should persist through upgrades.
Hope that helps!
Kind regards,
Mitja Mihelič
_______________________________________________
389-users mailing list -- 389-users(a)lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproje...
—
Sincerely,
William Brown
Senior Software Engineer, 389 Directory Server
SUSE Labs