[syslog-ng] fedora/rhel & logrotate

[Peter Czanik (pczanik)]

Hi,

Did some experimenting:

Well. Starting logrotate by hand revealed, that it errors out:

[root at localhost ~]# /usr/sbin/logrotate /etc/logrotate.conf
error: syslog-ng:1 duplicate log entry for /var/log/cron
error: syslog-ng:1 duplicate log entry for /var/log/maillog
error: syslog-ng:1 duplicate log entry for /var/log/messages
error: syslog-ng:1 duplicate log entry for /var/log/secure
error: syslog-ng:1 duplicate log entry for /var/log/spooler
error: found error in file syslog-ng, skipping

So, one problem is resolved, as there is no more file conflict with rsyslog. But we have another one.

- if we keep the file level conflict, then everything works properly, but rsyslog and syslog-ng can't be installed in parallel
- if there is no file level conflict then they can be installed in parallel, but reloading syslog-ng from logrotate does not work

What do you think?

Bye,

Peter Czanik (CzP) <peter.czanik at oneidentity.com>
Balabit (a OneIdentity company) / syslog-ng upstream
https://syslog-ng.com/community/
https://twitter.com/PCzanik

________________________________
From: syslog-ng <syslog-ng-bounces at lists.balabit.hu> on behalf of Peter Czanik (pczanik) <Peter.Czanik at oneidentity.com>
Sent: Tuesday, February 18, 2020 14:15
To: syslog-ng at lists.balabit.hu <syslog-ng at lists.balabit.hu>
Subject: [syslog-ng] fedora/rhel & logrotate

CAUTION: This email originated from outside of the organization. Do not follow guidance, click links, or open attachments unless you recognize the sender and know the content is safe.

Hi,

Recently I received a bug report about logrotate and RHEL 8: https://bugzilla.redhat.com/show_bug.cgi?id=1802165<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.redhat.com%2Fshow_bug.cgi%3Fid%3D1802165&data=02%7C01%7CPeter.Czanik%40oneidentity.com%7C3ea468d976204da2730208d7b474aa32%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637176285482793330&sdata=nzbhb0Eke8Vn9j7zOP0aMAtbgX3B1CobMFY1L3mQPsY%3D&reserved=0> In RHEL 8 /etc/logroate.d/syslog is now rsyslog specific and thus conflicts with the same file coming from syslog-ng. I changed my test repo https://copr.fedorainfracloud.org/coprs/czanik/syslog-ng-githead/<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcopr.fedorainfracloud.org%2Fcoprs%2Fczanik%2Fsyslog-ng-githead%2F&data=02%7C01%7CPeter.Czanik%40oneidentity.com%7C3ea468d976204da2730208d7b474aa32%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637176285482803331&sdata=DQEEadIsOzsGAGGLCWmdQtUft3qsfqBSJvkf%2Bwic%2FwU%3D&reserved=0> in a way that RHEL 7 keeps using /etc/logroate/syslog, but all the Fedora and RHEL 8 packages change the logroate file name to /etc/logroate/syslog-ng.

Of course this means, that there is no conflict with rsyslog and there are two logrotate scripts for the same set of logs.

I am trying to test it on my own as well on RHEL 8, but any additional testing and feedback are very welcome!

Thanks,

Peter Czanik (CzP) <peter.czanik at oneidentity.com>
Balabit (a OneIdentity company) / syslog-ng upstream
https://syslog-ng.com/community/<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsyslog-ng.com%2Fcommunity%2F&data=02%7C01%7CPeter.Czanik%40oneidentity.com%7C3ea468d976204da2730208d7b474aa32%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637176285482803331&sdata=vshkcpFWTYDlfJacYRiCroVIgDeGiynw5E6F5I%2BlXd4%3D&reserved=0>
https://twitter.com/PCzanik<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2FPCzanik&data=02%7C01%7CPeter.Czanik%40oneidentity.com%7C3ea468d976204da2730208d7b474aa32%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637176285482813325&sdata=4UJPj1gdzKyT%2FwulMxYgYVS6TtFncSFQb9oNHEanLv0%3D&reserved=0>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.balabit.hu/pipermail/syslog-ng/attachments/20200218/a01a301f/attachment.html>