#996246 syslog-ng: Spams /var/log/syslog with 100 MB of "Destination timeout has elapsed, closing connection" per day after upgrade from Buster to Bullseye

Package:
syslog-ng
Source:
syslog-ng
Submitter:
Axel Beckert
Date:
2026-10-18 20:45:08 UTC
Severity:
important
Tags:
#996246#5
Date:
2021-10-12 13:55:33 UTC
From:
To:
Dear Syslog-NG Maintainers,

I've run in an annoying bug with syslog-ng in Debian 11 Bullseye which
is already fixed upstream in version 3.30:

   * What led up to the situation?

Upgrading a high-traffic syslog-ng server from Debian Buster to Bullseye.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

We did not change any of the configuration except what the package
changes (and which was untouched by us).

   * What was the outcome of this action?

About 100 MB of /var/log/syslog within 24h (the upgrade was
on 13:30 UTC yesterday):

#996246#12
Date:
2021-10-12 16:41:44 UTC
From:
To:
Hi,

Axel Beckert wrote:

I've prepared a potential stable update at
https://github.com/xtaran/syslog-ng-debian/tree/debian/bullseye in
commit
https://github.com/xtaran/syslog-ng-debian/commit/4b508ba601f16b11378886f2626016816dcf0e2a

The patch is attached as well.

I'm now running this in production. It still has the "~abe1" suffix in
the version number (i.e. debian/changelog) in git so that any
potential security update overrides my local bugfix.

If you want to use this as real stable update, you need to remove that
safety guard suffix at least. Feel free to also bump the changelog
entry signature and replace "* Non-maintainer upload" with "[ Axel
Beckert ]".

Wanted to do a pull request for this, but Github doesn't seem to allow
pull requests which create new branches. And this shouldn't go into
any existing branch. So you need to pull or cherry-pick this on your
own into a debian/bullseye (or similar) branch.

The Stable Release Managers likely want to see that patch in Debian
Testing first, so you should probably start with updating Debian
Unstable to the latest upstream stable release and wait for that to
migrate to testing, before uploading any stable update package.

Thanks in advance for your consideration.

		Regards, Axel

#996246#29
Date:
2026-10-18 20:42:03 UTC
From:
To:
We believe that the bug you reported is fixed in the latest version of
syslog-ng, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 996246@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
SZALAY Attila <sasa@debian.org> (supplier of updated syslog-ng package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sun, 18 Oct 2026 20:33:27 +0100
Source: syslog-ng
Architecture: source
Version: 4.12.0-1
Distribution: unstable
Urgency: medium
Maintainer: syslog-ng maintainers <syslog-ng-maintainers@alioth-lists.debian.net>
Changed-By: SZALAY Attila <sasa@debian.org>
Closes: 831908 833283 844372 970355 992428 996246 1050692 1111518 1138428 1143061
Changes:
 syslog-ng (4.12.0-1) unstable; urgency=medium
 .
   * New upstream version 4.12.0 (Closes: #1143061, #1138428)
   * Clean up old and obsolated bugs (Closes: #831908, #844372, #970355, #992428, #996246)
   * Prepare new temporary release
   * Update debian patches
   * Dropping removed SCL modules
   * Re-enable secure logging module
   * Add new SCL config files to the syslog-ng-scl module
   * debian: Migrate legacy syslog-ng configs on upgrade (Closes: #833283)
   * debian: Update default configs to 4.12 (Closes: #1050692)
   * debian: Fix init script LSB header.
     Thanks to Andrew Bower <andrew@bower.uk> (Closes: #1111518)
   * Commenting about the GRPC module into the debian/README.source
Checksums-Sha1:
 301a2b61b3759e8d7297a24249736a5f8100ea84 4299 syslog-ng_4.12.0-1.dsc
 b5b0514b17f66a835a07713ea4307b91b2b199b2 2491465 syslog-ng_4.12.0.orig.tar.gz
 50cdfcccc94a08e6a082ffe114b8d03637a0a463 47660 syslog-ng_4.12.0-1.debian.tar.xz
 0672b083121e98c2b1283c699c7a417241c367a6 18385 syslog-ng_4.12.0-1_amd64.buildinfo
Checksums-Sha256:
 ae813e775eb8508b26b22ed764e8fdd9d3e89555f9f70d852eb9b6739914e20e 4299 syslog-ng_4.12.0-1.dsc
 94c88cb6d23d95c82a25366ae5455e6b0854716f27ab8f9288bdc7983188a381 2491465 syslog-ng_4.12.0.orig.tar.gz
 549d8c74f837497531d3a0ebab7ad33939ad2e0c361c94d53a6e74fc93f59d9b 47660 syslog-ng_4.12.0-1.debian.tar.xz
 cd30df305354247739c8b4c1ee30801f1f520bc2ddf8bc2bb94160c863f93cfd 18385 syslog-ng_4.12.0-1_amd64.buildinfo
Files:
 4dcf4cbc3937264e40a5873abf0a6337 4299 admin optional syslog-ng_4.12.0-1.dsc
 bc6bf2abe2705ac7e8daa36118c61785 2491465 admin optional syslog-ng_4.12.0.orig.tar.gz
 406376180601ff6f9dd34d72393a9e59 47660 admin optional syslog-ng_4.12.0-1.debian.tar.xz
 d2a6677d824c8d83d7e03603b8e60815 18385 admin optional syslog-ng_4.12.0-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQJEBAEBCgAuFiEEDLxdlTMbVcF2xVjk+A0hGpn97vgFAmrVIYYQHHNhc2FAZGVi
aWFuLm9yZwAKCRD4DSEamf3u+FRtD/oDTped4HVDnt+MZ8LfHlh4fyzx8BTOD/Sk
Gvc9uFp73zoS+RMSm49LRAK9nZojJd7L3WLC48WQk7wCDFLQ6nwhttinJqO+fWEK
SGS6PEqDH5+m8nqW09C/r3zbAy3ydSoiNXncy6qKcn5LD/UVaqH8ekFKn/4H2Bfx
hD4SsQaB27mZULNCVSm0qex1P0qwo0i/wrjMJj0Nq9lveNkidE4pUYh6xCGI2ff/
eQ9I5zAZCY2PJXxIXetN8W32d/J1bS7Yutx46h9xbr6ZZ8yJDiSeU5ik0iiTFtcA
/A2LgxBkwI5NY92yeOSJ+3KCqM0DcFwy/RdU7abzTSJBoc5q6WT6KdxxlYUgOvs2
p3FLbtQwP9QjXzb1SUakVYFPGjbjOfGyxd2Pf9Miq6NaduaE/gBqXPoY+kx8dX4U
rUWpBDBEob5Z2J/LR1WP/YrgFIEi2Ds2MYEsNxQWdZUkdL11pRIb772jbTTe49Uk
RWhCJfCinBsTKO+4SWvLLEwLY9Q3w/qufT0d721ff0ll/fWjHREDJEoaoKbtvq0E
r1pox2QQF494gPwiOJXLPJCjzjFi8vY411uSv9LmsOrUGB0jozUQcYxq1xzO/FLo
3yO9jbiXZoYoHWoafsxpe0IvvU5VIBG5glC0MdgiTArNk4oCA2zJ14qQ70l5eSHh
ARASRpJamg==
=OkXZ
-----END PGP SIGNATURE-----