? I suspect you've truncated this output too much. The interesting part is the > stderr output of the action command that is executed. That should tell us why > the action failed.
>Orion Poplawski Thanks for the reply, however I know the cause of the problem, which was that fail2ban started before iptables (which I am using instead of firewalld on RHEL7). F2b was upset because it could not find the needed table in iptables to undo the ban. That's fixable. The problem I can't solve is with the logging. That length of log message is being sent to rsyslogd, which then breaks logwatch. I am hoping there is a way to make the log message less verbose or truncated by f2b so that it doesn't break the output. The older rsyslog versions on RHEL7 can't handle that message length. --dcl Dave LeFevre ------------------------------------------------------------------------------ The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik _______________________________________________ Fail2ban-users mailing list Fail2ban-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fail2ban-users
