Your message dated Sun, 18 Sep 2022 16:46:18 +0000 with message-id <[email protected]> and subject line Bug#982918: fixed in syslog-ng 3.38.1-2 has caused the Debian Bug report #982918, regarding syslog-ng: tty10 is not a device under LXC causing a normal file to be written for d_console_all to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 982918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982918 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: syslog-ng Version: 3.19.1-5 Severity: important Dear Maintainer, The Debian syslog-ng.conf contains the following: # Virtual console. # destination d_console_all { file(`tty10`); }; Normally this works fine. However, under LXC there are only a small number of tty devices available. Therefore, syslog-ng will write to a standard file /dev/tty10 instead of the block device. Further, LXC by default allocates a relatively small amount of partition space to /dev, approximately 500 KB, so /dev/tty10 will quickly grow to consume all available /dev space rendering syslog-ng from logging at all once that situation arises. This issue was detailed in a blog post here: <https://www.claudiokuenzler.com/blog/988/syslog-ng-lxc-container-no-space-left-on-device-dev> The blog post author suggested changing tty10 to tty2, but the syslog-ng upstream maintainer suggested just removing tty10 config altogether: <https://lists.balabit.hu/pipermail/syslog-ng/2021-February/026182.html> This configuration statement appears to have introduced as far back as 3.1.0-1: syslog-ng (3.1.0-1) unstable; urgency=low * New upstream release. * Fix path of syslog logfile (closes: #575722) and use tty10 instead of vc/10 to log on console. -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-13-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages syslog-ng depends on: ii syslog-ng-core 3.19.1-5 ii syslog-ng-mod-mongodb 3.19.1-5 ii syslog-ng-mod-sql 3.19.1-5 Versions of packages syslog-ng recommends: ii syslog-ng-mod-add-contextual-data 3.19.1-5 ii syslog-ng-mod-amqp 3.19.1-5 ii syslog-ng-mod-examples 3.19.1-5 ii syslog-ng-mod-extra 3.19.1-5 ii syslog-ng-mod-geoip 3.19.1-5 ii syslog-ng-mod-geoip2 3.19.1-5 ii syslog-ng-mod-getent 3.19.1-5 ii syslog-ng-mod-graphite 3.19.1-5 ii syslog-ng-mod-journal 3.19.1-5 ii syslog-ng-mod-map-value-pairs 3.19.1-5 ii syslog-ng-mod-pacctformat 3.19.1-5 ii syslog-ng-mod-python 3.19.1-5 ii syslog-ng-mod-redis 3.19.1-5 ii syslog-ng-mod-riemann 3.19.1-5 ii syslog-ng-mod-smtp 3.19.1-5 ii syslog-ng-mod-snmptrapd-parser 3.19.1-5 ii syslog-ng-mod-stardate 3.19.1-5 ii syslog-ng-mod-stomp 3.19.1-5 ii syslog-ng-mod-tag-parser 3.19.1-5 ii syslog-ng-mod-xml-parser 3.19.1-5 syslog-ng suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Source: syslog-ng Source-Version: 3.38.1-2 Done: SZALAY Attila <[email protected]> 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 [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. SZALAY Attila <[email protected]> (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 [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sun, 18 Sep 2022 16:13:46 +0100 Source: syslog-ng Architecture: source Version: 3.38.1-2 Distribution: unstable Urgency: medium Maintainer: syslog-ng maintainers <[email protected]> Changed-By: SZALAY Attila <[email protected]> Closes: 962839 982918 Changes: syslog-ng (3.38.1-2) unstable; urgency=medium . [ Attila Szalay ] * To smooth the upgrade process, re-introduce syslog-ng-mod-extra as a transitional package * Fix control socket path (Closes: #962839) * Select virt console destination dinamically (Closes: #982918) Checksums-Sha1: dc04d218a58cdb263327d18d501aba2ffb4bd775 4434 syslog-ng_3.38.1-2.dsc 551a822c0528cfa3544942e8300a3cc0152602e1 41564 syslog-ng_3.38.1-2.debian.tar.xz 905449bb15728aa761be953c229904d489bd3385 17870 syslog-ng_3.38.1-2_amd64.buildinfo Checksums-Sha256: 956e365330dd98ce7d079e0e3f4d64fa93ec39880193545de9152fe43dcac3e3 4434 syslog-ng_3.38.1-2.dsc d7517cc0410b7a4ff6e761e9513eb9d8297bd00bbd335d1659fd79aa1599cb7c 41564 syslog-ng_3.38.1-2.debian.tar.xz 4676b5b3dd1fa1971d350a872bd10bc6e0bf3e586759c50b32963ce8ec412052 17870 syslog-ng_3.38.1-2_amd64.buildinfo Files: abcec832eb14f0fd3d6d18c92422b9b1 4434 admin optional syslog-ng_3.38.1-2.dsc 4c341d4376a114d88fb4732d751627cd 41564 admin optional syslog-ng_3.38.1-2.debian.tar.xz db6b66581ae696691e0298165115fe22 17870 admin optional syslog-ng_3.38.1-2_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQJEBAEBCgAuFiEEDLxdlTMbVcF2xVjk+A0hGpn97vgFAmMnRbQQHHNhc2FAZGVi aWFuLm9yZwAKCRD4DSEamf3u+HuJEACFXGan1I7913JmgPYKKv55CSPcb3amDn0F nQKWc+f4wS7uome6Nidc73CeP174htzL9Gz2kTuuCAfTUhqw9sS4/lAEe/mhyR4q EaXmu8IF0EFv7Ut//+Ba+88eVGV2dE1KYoxs1H9ExMr4Bx6wfNdKq1F7vQ7TP8Hb 49aBlQ7ky7p2uOZ1UKQfnfV9UYPyNAk9VnqEyZ48NYCM9sdOkKXb1lojkwa3vqyp ODXufXGfqNCoHbMvyeiSKIq6X27zByFEv6CiRH9oPEsoJDUU0rtzn9UbzxkyGqeO BPTlhXq6JJRCJK7cw0asBtN/u3cKUDHuiHrZB2RfFqYeygVZ4FZ+Kd1yIxVYAr5z +VhheMq1U9mxrLe2oCaLG3N35JviWDj2KNAR0579hxT0EEsWdCabpMNtanNZiKQr Qj7SyGkK3bRdJL40RXNa6BDaUDzqGKpIBJA6WcTzMe7Slwn4qTsVOyfnU1hDIGKF seXbtcU2MXpujgYY2FI1dilx9MrzxSUhFHsu5SwlQsq+J5E5Se5GsjUYsP/NRoBw U85JlzMIU+MdTz6z4dnB4NbmbQrPtjhUAglwVmQkRKuckl6BRKNMlBZEVZKuQa3G A6Zy+uMm1r8FpjAd4f9yMa8awXnY06nr3JxD+j+PztNcLnZ7UjNS3jlnNyKKhdZ/ JvXZNlIwnw== =qji/ -----END PGP SIGNATURE-----
--- End Message ---
