Your message dated Thu, 18 Dec 2025 09:05:24 +0000
with message-id <[email protected]>
and subject line Bug#944969: fixed in iptraf-ng 1:1.2.2-1
has caused the Debian Bug report #944969,
regarding logrotate processing broken
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.)
--
944969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944969
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: iptraf-ng
Version: 1:1.1.4-6+b1
Severity: normal
I saw that logrotate.service state went red so I checked the log:
systemctl status logrotate.service
● logrotate.service - Rotate log files
Loaded: loaded (/lib/systemd/system/logrotate.service; static; vendor
preset: enabled)
Active: failed (Result: exit-code) since Sun 2019-11-17 00:00:00 CET; 22h ago
Docs: man:logrotate(8)
man:logrotate.conf(5)
Main PID: 9160 (code=exited, status=1/FAILURE)
Nov 17 00:00:00 zombie systemd[1]: Starting Rotate log files...
Nov 17 00:00:00 zombie logrotate[9160]: error: iptraf-ng:2 duplicate log entry
for /var/log/iptraf/rvnamed.log
Nov 17 00:00:00 zombie logrotate[9160]: error: found error in file iptraf-ng,
skipping
Nov 17 00:00:00 zombie systemd[1]: logrotate.service: Main process exited,
code=exited, status=1/FAILURE
Nov 17 00:00:00 zombie systemd[1]: logrotate.service: Failed with result
'exit-code'.
Nov 17 00:00:00 zombie systemd[1]: Failed to start Rotate log files.
However, this is the state of the said file, this can hardly contain a
duplicated log entry:
-rw-r--r-- 1 root root 0 Mai 24 2017 rvnamed.log
So I guess it's complaining about wrong logrotate config itself?
$ grep iptraf /etc/logrotate.d/ -r
/etc/logrotate.d/iptraf-ng:# Logrotate file for iptraf
/etc/logrotate.d/iptraf-ng:/var/log/iptraf/*.log {
/etc/logrotate.d/iptraf:/var/log/iptraf/*.log {
/etc/logrotate.d/iptraf: /usr/bin/killall -USR1 iptraf 2>
/dev/null || :
Checking, purging iptraf -> result: the problem is solved.
Please find a clean solution here, at least mentioning the side effects
of iptraf's remains in README.Debian (but better, check for the other's
config state via checksum and killing it, although not sure whether
policy has some kind of exception for this case).
Best regards,
Eduard.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.3.8+ (SMP w/12 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages iptraf-ng depends on:
ii libc6 2.29-3
ii libncursesw6 6.1+20191019-1
ii libtinfo6 6.1+20191019-1
iptraf-ng recommends no packages.
iptraf-ng suggests no packages.
-- no debconf information
--
<Angel`Eye> installations anleitung für intelx86 richtig ?
<Salz> Angel`Eye: Kommt auf deinen Rechner an. Wenn du die Antwort nicht weißt,
ist sie ja.
--- End Message ---
--- Begin Message ---
Source: iptraf-ng
Source-Version: 1:1.2.2-1
Done: Aron Xu <[email protected]>
We believe that the bug you reported is fixed in the latest version of
iptraf-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.
Aron Xu <[email protected]> (supplier of updated iptraf-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: Thu, 18 Dec 2025 16:33:35 +0800
Source: iptraf-ng
Architecture: source
Version: 1:1.2.2-1
Distribution: unstable
Urgency: medium
Maintainer: Aron Xu <[email protected]>
Changed-By: Aron Xu <[email protected]>
Closes: 859759 860568 900370 944969 1090381
Changes:
iptraf-ng (1:1.2.2-1) unstable; urgency=medium
.
* New upstream release (Closes: #1090381, CVE-2024-52949)
* Update std-ver to 4.7.2, no change required.
* Add appropriate maint scripts (Closes: #859759, #900370)
* Fix upstream logrotate configuration (Closes: #860568, #944969)
Checksums-Sha1:
c5d395fa38ff2565d6b92d378220fb1b7f9fa8c8 1411 iptraf-ng_1.2.2-1.dsc
9039cf611de741cc8c2c2cfb2494eec06f249d0a 325800 iptraf-ng_1.2.2.orig.tar.gz
f3069201cc327551cc4cf60c5f51b5d7a99240ad 3412 iptraf-ng_1.2.2-1.debian.tar.xz
aead83d01bffebec449dc1ca6ed58f4668c91448 5263
iptraf-ng_1.2.2-1_source.buildinfo
Checksums-Sha256:
0eef6aeacfc8d22f6af6e548c36a44c7401a8b5863c00c8cbf4c934f4b67feb6 1411
iptraf-ng_1.2.2-1.dsc
75fd653745ea0705995c25e6c07b34252ecc2563c6a91b007a3a8c26f29cc252 325800
iptraf-ng_1.2.2.orig.tar.gz
c601611ad1dc877f7b2048f2e2ea3d4ed6acd6fc50105f70ba03187b8dcc9696 3412
iptraf-ng_1.2.2-1.debian.tar.xz
7fefaab8045d938eff32dbe0bd842d108b300bbaaacbc81f117a46de2cec520d 5263
iptraf-ng_1.2.2-1_source.buildinfo
Files:
ab7b29465fcc230a80f53c9e0843a011 1411 net optional iptraf-ng_1.2.2-1.dsc
5bb20562a785b446b17dc79e2bc1ed41 325800 net optional
iptraf-ng_1.2.2.orig.tar.gz
07bc08d47d80491f54d102102d8be9a5 3412 net optional
iptraf-ng_1.2.2-1.debian.tar.xz
18648d5ad6428bab9b84cf8637032c91 5263 net optional
iptraf-ng_1.2.2-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCgAdFiEEBLHAyuu1xqoC2aJ5NP8o68vMTMgFAmlDvesACgkQNP8o68vM
TMjN8ggAiza4mCuGjWi3h7M8J78LYywp7AI2tj3mpvoqsKhhchSWYEIAdekG7Qmh
YQK/F6PmLhNgDg2Vh4asu7tCtJZPGsoYdHf64C9d9IwLceB8s8Y4yytqnxWMFOk1
rhZeVdIFW9yQa8tNz1+cGJLS9MqvtbDi+gybo0uYjVw2XrDfIoBPqv1kkhJ5dfET
OuYmDKSM0ILibvO8fnmaYK+JW6xQipD9k0AASDHJf3v6cnR6ZSRDK9iFkC5FrMgN
W2zadiOA9PjhSU1zbYsZuWxRaS+Wb+xexVDI2AsZpwgjE39gCMSu6II1VfilLRrm
D23AaECk4NbicTxYX6MX+/LrJY4tvw==
=Tjcy
-----END PGP SIGNATURE-----
pgp5dzX4Zckvi.pgp
Description: PGP signature
--- End Message ---
