From: Michael F. <ne...@me...> - 2017-08-07 23:45:11
|
Dominic, Jonathan, Thanks much for the quick response. Still getting used to the systemd stuff. M From: Jonathan Kamens [mailto:ji...@ka...] Sent: Monday, August 7, 2017 1:36 PM To: Fail2Ban-Users Distribution List <fai...@li...> Subject: Re: [Fail2ban-users] Ubuntu 16.04 package problems Dominic has correctly identified the issue. In Ubuntu 16.04, if you stop fail2ban using fail2ban-client rather than systemctl, then systemd will think that fail2ban died abnormally, complain in the logs about that, and attempt to restart it. Use systemctl to stop it cleanly. jik On 8/7/17 4:01 PM, Dominic Raferd wrote: On 7 August 2017 at 20:33, Michael Fox <ne...@me... <mailto:ne...@me...> > wrote: I've been a user of fail2ban for several years. I'm not an expert. But I'm not a newbie either. Everything has been running fine on Ubuntu 14.04. I'm building a new Ubuntu 16.04 machine. I installed the fail2ban package (v0.9.3) and encountered this problem immediately after install and before performing any customization at all. "fail2ban-client stop" claims success, but syslog shows problems. Question 1: Why is the client reporting success even though there is evidently a problem? Question 2: Why is it starting again, when the command given was "stop"? $ sudo fail2ban-client stop Shutdown successful Not sure if it will help, but in Ubuntu 16.04 the way to start and stop fail2ban is with systemctl (under systemd control): sudo systemctl start|stop|reload-or-restart fail2ban BTW, fail2ban 0.9.3 can be very (very) slow starting, stopping and reloading. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Fail2ban-users mailing list Fai...@li... <mailto:Fai...@li...> https://lists.sourceforge.net/lists/listinfo/fail2ban-users |