Date: Sun, 02 May 2021 10:39:33 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 255543] security/py-fail2ban: Not working with Python 3.8 Message-ID: <bug-255543-7788-qEtbNsAEqR@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-255543-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-255543-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255543 --- Comment #1 from theis@gmx.at --- I updated python a couple of days before. I noticed that the pid in sock fi= les in /var/run/fail2ban are left over which in my case caused the messages "not running but socket exists" and another error "'str' object does not have property 'args'" (or something like that). Deleting those files solved my problems. I filed it as my error because I didn't followed the update proce= dure to its full extend and so didn't investigate further. A fresh install of fail2ban on a test machine was successful. So you may try if this resolves your problem: - stop fail2ban - remove the /var/run/fail2ban/fail2ban.pid and .../fail2ban.sock - start fail2ban --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-255543-7788-qEtbNsAEqR>