So after removing fail2ban (the VM host takes care of this in my setup), I have been greeted with

	/etc/cron.daily/logrotate:
	logrotate_script: 2: logrotate_script: fail2ban-client: not found
error: error running non-shared postrotate script for /var/log/fail2ban.log of /var/log/fail2ban.log run-parts: /etc/cron.daily/logrotate exited with return code 1
Manual removal of fail2ban from /etc/logrotate.d required.
Forum: 
Jeremy Davis's picture

Thanks again for reporting this. Although I'm not really sure what to do with this. Whilst it could reasonably be considered a bug in your circumstance, I'm not 100% sure.

Perhaps for starters it's worth getting an understanding of how you removed fail2ban? I'm assuming that you used apt right? E.g. something like this:

apt remove fail2ban
# or
apt-get remove fail2ban

Under normal circumstance I would expect the package management to remove that file too, and so perhaps it's a bug within the package management scripts. Another thing is that when you use "remove" that intentionally leaves some config files behind (so it doesn't require reconfiguration if you reinstall it), so perhaps it's better to use purge (which will remove all config)?:

apt purge fail2ban
# or
apt-get purge fail2ban
# or
apt-get remove --purge fail2ban

Add new comment