Skip to content

Unable to upgrade firewalld/plinth due to conflict with fail2ban

I saw this issue in vagrant, not sure if normal boxes are affected:

Setting up firewalld (0.4.4.6-1) ...
Failed to restart firewalld.service: Transaction contains conflicting jobs 'restart' and 'stop' for fail2ban.service. Probably contradicting requirement dependencies configured.
See system logs and 'systemctl status firewalld.service' for details.
invoke-rc.d: initscript firewalld, action "restart" failed.
● firewalld.service - firewalld - dynamic firewall daemon
   Loaded: loaded (/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2017-11-16 23:23:45 UTC; 50min ago
     Docs: man:firewalld(1)
 Main PID: 374 (firewalld)
    Tasks: 2 (limit: 4915)
   CGroup: /system.slice/firewalld.service
           └─374 /usr/bin/python3 -Es /usr/sbin/firewalld --nofork --nopid

Nov 16 23:23:43 freedombox systemd[1]: Starting firewalld - dynamic firewall daemon...
Nov 16 23:23:45 freedombox systemd[1]: Started firewalld - dynamic firewall daemon.
dpkg: error processing package firewalld (--configure):
 installed firewalld package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of plinth:
 plinth depends on firewalld; however:
  Package firewalld is not configured yet.

dpkg: error processing package plinth (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 firewalld
 plinth

i can get past the issue by running "systemctl stop fail2ban".