Package: logrotate
Version: 3.14.0-4
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:
Contents of /etc/logrotate.d
total 48
-rw-r--r-- 1 root root 120 Oct 21  2017 alternatives
-rw-r--r-- 1 root root 443 Aug 30 14:29 apache2
-rw-r--r-- 1 root root 173 Dec 11  2016 apt
-rw-r--r-- 1 root root  79 Nov  8  2014 aptitude
-rw-r--r-- 1 root root 130 Aug 29 00:21 btmp
-rw-r--r-- 1 root root  82 Jan 10  2018 certbot
-rw-r--r-- 1 root root 112 Oct 21  2017 dpkg
-rw-r--r-- 1 root root 356 Jan  5  2018 fail2ban
-rw-r--r-- 1 root root 845 Feb  3  2017 mysql-server
-rw-r--r-- 1 root root 162 Jul  4  2016 rkhunter
-rw-r--r-- 1 root root 501 Jun 26 19:29 rsyslog
-rw-r--r-- 1 root root 145 Feb 19  2018 wtmp


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-1-amd64 (SMP w/1 CPU core)
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/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages logrotate depends on:
ii  cron [cron-daemon]  3.0pl1-130
ii  libacl1             2.2.52-3+b1
ii  libc6               2.27-8
ii  libpopt0            1.16-11
ii  libselinux1         2.8-1+b1

Versions of packages logrotate recommends:
ii  bsd-mailx [mailx]  8.1.2-0.20180807cvs-1

logrotate suggests no packages.

# ufw file of logrotate removed to prevent open ports to internet!!!
# systemd removed and switched back to sys-v-init ! like devuan !

# My workaround, ufw removed from logrotate and set ufw logging "off"!

# Problem appears after dist-upgrade/update !

-- no debconf information

Reply via email to