[SOLVED] Fail2ban-1.0.2 don't start anymore on current, please help
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Fail2ban-1.0.2 don't start anymore on current, please help
I use the Ponce Slackbuild to build version 1.0.2 from fail2ban but i realized it doesn't start anymore since ~ Apr 3
Code:
# /etc/rc.d/rc.fail2ban start
Starting fail2ban
Traceback (most recent call last):
File "/usr/bin/fail2ban-client", line 34, in <module>
from fail2ban.client.fail2banclient import exec_command_line, sys
File "/usr/lib/python3.11/site-packages/fail2ban/client/fail2banclient.py", line 39, in <module>
from ..server.utils import Utils
File "/usr/lib/python3.11/site-packages/fail2ban/server/utils.py", line 56, in <module>
for name, num in signal.__dict__.iteritems() if name.startswith("SIG"))
^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'dict' object has no attribute 'iteritems'
I tried to replace iteritems() by items() but i have zero knowledge in python and it did not solve the issue.
Does anyone have experienced this error and have a fix ?
EDIT:
by the way there is a small typo in paths-slackware.conf from the Slackbuild:
There is a build deprecation notice but it start fine
The version on SBo hasn't been updated since 2018 and is meant to be built for python2 so it's not surprising. You should takeover the slackbuild and update it to 1.0.2 on SBo and make sure to change the setup.py line above to python3. (note that on current /usr/bin/python -> python3.11 which adds to the issue you are having)
The version on SBo hasn't been updated since 2018 and is meant to be built for python2 so it's not surprising. You should takeover the slackbuild and update it to 1.0.2 on SBo and make sure to change the setup.py line above to python3. (note that on current /usr/bin/python -> python3.11 which adds to the issue you are having)
Didn't mention i was talking about the Ponce repo version for current.
Starts fine now, i will post here if i encounter error on use.
Didn't mention i was talking about the Ponce repo version for current.
Starts fine now, i will post here if i encounter error on use.
Thank you for the update.
I understood, but it doesn't matter in this case. The basic rule is that if a fix can be made in the SBo 15.0 repo, it should be made there first, if not then ponce will fix it in his current repo.
I understood, but it doesn't matter in this case. The basic rule is that if a fix can be made in the SBo 15.0 repo, it should be made there first, if not then ponce will fix it in his current repo.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.