[From nobody Sun Oct 18 21:45:10 2026 Received: (at submit) by bugs.debian.org; 20 Jul 2016 18:28:34 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.0-bugs.debian.org_2005_01_02 (2014-02-07) on buxtehude.debian.org X-Spam-Level: X-Spam-Status: No, score=-11.9 required=4.0 tests=BAYES_00, FOURLA, HAS_PACKAGE, XMAILER_REPORTBUG autolearn=ham autolearn_force=no version=3.4.0-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 18; hammy, 150; neutral, 161; spammy, 0. spammytokens: hammytokens:0.000-+--systemd, 0.000-+--H*M:reportbug, 0.000-+--H*MI:reportbug, 0.000-+--H*x:reportbug, 0.000-+--H*UA:reportbug Return-path: <gombasg@digikabel.hu> Received: from smarthost06.digicable.hu ([94.21.128.16]) by buxtehude.debian.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from <gombasg@digikabel.hu>) id 1bPwEU-0003OY-Aq for submit@bugs.debian.org; Wed, 20 Jul 2016 18:28:34 +0000 Received: from [92.249.128.189] (helo=relay01.digicable.hu) by smarthost06.digicable.hu with esmtp id 1bPwEM-0007SO-NW ; Wed, 20 Jul 2016 20:28:26 +0200 Received: from [84.236.18.46] (helo=raspi.lan) by relay01.digicable.hu with esmtpa id 1bPwEM-0002DE-6e ; Wed, 20 Jul 2016 20:28:26 +0200 Received: from zephyr.lan (zephyr.lan [10.72.1.19]) by raspi.lan (Postfix) with ESMTPS id 3rvllt0KlHzdbc; Wed, 20 Jul 2016 20:28:26 +0200 (CEST) Received: by zephyr.lan (Postfix, from userid 1000) id BD50717AFDE; Wed, 20 Jul 2016 20:28:25 +0200 (CEST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Gabor Gombas <gombasg@digikabel.hu> To: Debian Bug Tracking System <submit@bugs.debian.org> Subject: syslog-ng-mod-journal: Upgrading to 3.7.3-1 caused all of the existing systemd journal to be dumped into syslog Message-ID: <146903930574.8658.12624667423963550327.reportbug@zephyr.lan> X-Mailer: reportbug 6.6.6 Date: Wed, 20 Jul 2016 20:28:25 +0200 X-Original: 84.236.18.46 X-Original: 92.249.128.189 Delivered-To: submit@bugs.debian.org Package: syslog-ng-mod-journal Version: 3.7.3-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Upgrading syslog-ng-core. * What exactly did you do (or not do) that was effective (or ineffective)? apt upgrade -t unstable * What was the outcome of this action? The _entire_ systemd journal (several months) were dumped into syslog. * What outcome did you expect instead? No such stupidity... More seriously, from dpkg log it can be seen when syslog-ng was upgraded: 2016-07-20 07:57:02 install syslog-ng-mod-journal:amd64 <none> 3.7.3-1 2016-07-20 07:57:02 status half-installed syslog-ng-mod-journal:amd64 3.7.3-1 2016-07-20 07:57:02 status triggers-pending syslog-ng-core:amd64 3.5.6-2.1+b3 2016-07-20 07:57:02 status half-installed syslog-ng-mod-journal:amd64 3.7.3-1 2016-07-20 07:57:02 status unpacked syslog-ng-mod-journal:amd64 3.7.3-1 2016-07-20 07:57:02 status unpacked syslog-ng-mod-journal:amd64 3.7.3-1 2016-07-20 07:57:02 upgrade syslog-ng-core:amd64 3.5.6-2.1+b3 3.7.3-1 2016-07-20 07:57:02 status half-configured syslog-ng-core:amd64 3.5.6-2.1+b3 2016-07-20 07:57:02 status unpacked syslog-ng-core:amd64 3.5.6-2.1+b3 2016-07-20 07:57:02 status half-installed syslog-ng-core:amd64 3.5.6-2.1+b3 2016-07-20 07:57:03 status half-installed syslog-ng-core:amd64 3.5.6-2.1+b3 2016-07-20 07:57:03 status unpacked syslog-ng-core:amd64 3.7.3-1 2016-07-20 07:57:03 status unpacked syslog-ng-core:amd64 3.7.3-1 /var/log/syslog: Jul 20 07:57:36 host syslog-ng[2221]: syslog-ng shutting down; version='3.5.6' Jul 20 07:57:36 host systemd[1]: Stopping System Logger Daemon... Jul 20 07:57:37 host syslog-ng[25569]: syslog-ng starting up; version='3.7.3' Jul 20 07:57:37 host syslog-ng[25569]: Syslog connection established; fd='13', server='AF_INET(192.168.0.10:601)', local='AF_INET(0.0.0.0:0)' --- fine so far... but: --- Oct 15 19:44:20 host systemd-journal[271]: Runtime journal (/run/log/journal/) is currently using 8.0M. Maximum allowed usage is set to 157.4M. Leaving at least 236.1M free (of currently available 1.5G of space). Enforced usage limit is thus 157.4M. Oct 15 19:44:20 host systemd-journal[271]: Runtime journal (/run/log/journal/) is currently using 8.0M. Maximum allowed usage is set to 157.4M. Leaving at least 236.1M free (of currently available 1.5G of space). Enforced usage limit is thus 157.4M. Yup, that's the beginning of the systemd journal: # journalctl | head -- Logs begin at Thu 2015-10-15 19:44:20 CEST, end at Wed 2016-07-20 20:09:22 CEST. -- Oct 15 19:44:20 host systemd-journal[271]: Runtime journal (/run/log/journal/) is currently using 8.0M. Maximum allowed usage is set to 157.4M. Leaving at least 236.1M free (of currently available 1.5G of space). Enforced usage limit is thus 157.4M. Oct 15 19:44:20 host systemd-journal[271]: Runtime journal (/run/log/journal/) is currently using 8.0M. Maximum allowed usage is set to 157.4M. Leaving at least 236.1M free (of currently available 1.5G of space). Enforced usage limit is thus 157.4M. *** End of the template - remove these template lines *** -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable'), (102, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.3 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages syslog-ng-mod-journal depends on: ii libc6 2.23-2 ii libsystemd0 230-7 ii syslog-ng-core [syslog-ng-abi-3.7-0] 3.7.3-1 Versions of packages syslog-ng-mod-journal recommends: ii systemd 230-7 syslog-ng-mod-journal suggests no packages. -- no debconf information ]