fatal error is syslog-ng 4.8 from copr when reading pipe sources.
I upgraded syslog-ng today from 4.6 to 4.8 and my disk drive almost immediately filled due to the local error from syslog-ng 2024-09-20T11:59:38.760-07:00 hostname syslog.err syslog-ng[600690]: Error invoking seek on file; filename='/var/log/syslog.pipes/mailstats2', error='Illegal seek (29)' This logged repeatedly until the disk filled up. My source definition for that pipe is source mailstats2 { pipe("/var/log/syslog.pipes/mailstats2" log_iw_size(900000) log_fetch_limit(500) flags(no-parse) ); }; Any insight would be useful. -- Evan
I should have looked at reported issues. This issue was reported previously at https://github.com/syslog-ng/syslog-ng/issues/5057 And the PR has already been created. I will wait for an updated package from copr. -- Evan ________________________________ From: syslog-ng <syslog-ng-bounces@lists.balabit.hu> on behalf of Evan Rempel <erempel@uvic.ca> Sent: September 20, 2024 12:08 PM To: syslog-ng@lists.balabit.hu <syslog-ng@lists.balabit.hu> Subject: [syslog-ng] fatal error is syslog-ng 4.8 from copr when reading pipe sources. I upgraded syslog-ng today from 4.6 to 4.8 and my disk drive almost immediately filled due to the local error from syslog-ng 2024-09-20T11:59:38.760-07:00 hostname syslog.err syslog-ng[600690]: Error invoking seek on file; filename='/var/log/syslog.pipes/mailstats2', error='Illegal seek (29)' This logged repeatedly until the disk filled up. My source definition for that pipe is source mailstats2 { pipe("/var/log/syslog.pipes/mailstats2" log_iw_size(900000) log_fetch_limit(500) flags(no-parse) ); }; Any insight would be useful. -- Evan
Hi Evan, Version 4.8.1 of syslog-ng was released yesterday. It should also fix your problem. https://copr.fedorainfracloud.org/coprs/czanik/syslog-ng48/is already updated to 4.8.1, the syslog-ng-stable repo will be updated with a few days of delay, as usual. Have a nice weekend, Peter Peter Czanik (CzP) <peter.czanik@oneidentity.com> Balabit (a OneIdentity company) / syslog-ng upstream https://syslog-ng.com/community/ https://twitter.com/PCzanik ________________________________ From: syslog-ng <syslog-ng-bounces@lists.balabit.hu> on behalf of Evan Rempel <erempel@uvic.ca> Sent: Monday, September 23, 2024 15:58 To: Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu> Subject: [syslog-ng] new copr package required: fatal error is syslog-ng 4.8 from copr when reading pipe sources. 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. I should have looked at reported issues. This issue was reported previously at https://github.com/syslog-ng/syslog-ng/issues/5057 And the PR has already been created. I will wait for an updated package from copr. -- Evan ________________________________ From: syslog-ng <syslog-ng-bounces@lists.balabit.hu> on behalf of Evan Rempel <erempel@uvic.ca> Sent: September 20, 2024 12:08 PM To: syslog-ng@lists.balabit.hu <syslog-ng@lists.balabit.hu> Subject: [syslog-ng] fatal error is syslog-ng 4.8 from copr when reading pipe sources. I upgraded syslog-ng today from 4.6 to 4.8 and my disk drive almost immediately filled due to the local error from syslog-ng 2024-09-20T11:59:38.760-07:00 hostname syslog.err syslog-ng[600690]: Error invoking seek on file; filename='/var/log/syslog.pipes/mailstats2', error='Illegal seek (29)' This logged repeatedly until the disk filled up. My source definition for that pipe is source mailstats2 { pipe("/var/log/syslog.pipes/mailstats2" log_iw_size(900000) log_fetch_limit(500) flags(no-parse) ); }; Any insight would be useful. -- Evan
participants (2)
-
Evan Rempel
-
Peter Czanik (pczanik)