Few weeks ago, I did a migration from Wheezy to Jessie. Having a look to the fail2ban log files, I found that they were empty. Indeed:
$ sudo service fail2ban status fail2ban.service - LSB: Start/stop fail2ban Loaded: loaded (/etc/init.d/fail2ban) Active: active (exited) since Thu 2016-01-21 18:38:07 CET; 15h ago
Jan 21 18:38:06 myServerName fail2ban[1782]: Starting authentication failure monitor: fail2banERROR Found no accessible config files for 'filter.d/sasl' under /etc/fail2ban Jan 21 18:38:06 myServerName fail2ban[1782]: ERROR Unable to read the filter Jan 21 18:38:06 myServerName fail2ban[1782]: ERROR Errors in jail 'sasl'. Skipping... Jan 21 18:38:07 myServerName fail2ban[1782]: failed!
Could it be that, after the upgrade to Jessie, I need to reconfigure (dpkg-reconfigure) one of the following yunohost services? yunohost-config / yunohost-config-others / yunohost-config-slapd
Let’s say it another way: is that safe to reconfigure the following yunohost services on a running server? yunohost-config / yunohost-config-others / yunohost-config-slapd
Sorry to insist, but nobody can tell if it could be an issue to reconfigure the yunohost services on a quite-well-running server, to try fixing that problem?
Or if it is safe to try it?