• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx

  • We are developing a new feature in Plesk that will help you promote your websites or business on social media. We want to conduct a one-hour online UX test to present the prototype and collect feedback. If you are interested in the feature, please book a meeting via this link.
    Thank you in advance!
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Question upgrade to onyx - fail2ban conflicts

moswak

Regular Pleskian
CentOS 7.2.1511
Plesk 17.0.17 Update #7

Hi,

Fail2ban was manually installed, not via plesk and is not used in plesk either.
before upgrade to Onyx yum update shows "no updates"

After the upgrade to onyx "yum update" shows

--> Running transaction check
---> Package fail2ban.noarch 0:0.9.3-1.el7 will be updated
---> Package fail2ban.noarch 1:0.9.2-centos7.16102516 will be an update
--> Processing Dependency: gamin-python for package: 1:fail2ban-0.9.2-centos7.16102516.noarch
--> Running transaction check
---> Package gamin-python.x86_64 0:0.1.10-16.el7 will be installed
--> Processing Dependency: gamin = 0.1.10-16.el7 for package: gamin-python-0.1.10-16.el7.x86_64
--> Processing Dependency: libgamin-1.so.0()(64bit) for package: gamin-python-0.1.10-16.el7.x86_64
--> Running transaction check
---> Package gamin.x86_64 0:0.1.10-16.el7 will be installed
--> Processing Conflict: 1:fail2ban-0.9.2-centos7.16102516.noarch conflicts fail2ban-server
--> Processing Conflict: 1:fail2ban-0.9.2-centos7.16102516.noarch conflicts fail2ban-sendmail
--> Processing Conflict: 1:fail2ban-0.9.2-centos7.16102516.noarch conflicts fail2ban-firewalld
--> Finished Dependency Resolution
Error: fail2ban conflicts with fail2ban-firewalld-0.9.3-1.el7.noarch
Error: fail2ban conflicts with fail2ban-server-0.9.3-1.el7.noarch
Error: fail2ban conflicts with fail2ban-sendmail-0.9.3-1.el7.noarch

The repro files are unchanged, except for the plesk own reprofiles.

Why is after the upgrade at once the update for fail2ban suggested ?
 
Hi,

ok i know now from which source Onyx wants to update fail2ban
plesk.repo -> name=PLESK_17_0_17 extras

It is ok Plesk detects that the package fail2ban is installed "but" it does not check on fail2ban is installed / aktivated in Plesk as a component.
when fail2ban is not installed / activated via Plesk, Plesk should not update fail2ban from his own repo.

when i exclude fail2ban in plesk.repo -> name=PLESK_17_0_17 extras, this may be overwritten with updates ?
 
Would it be a good solution to switch from the individual fail2ban to the one that Plesk provides? What are your arguments to keep an individual version alive on that system?
 
The reason why fail2ban was installed manually is that this was necessary before Plesk 12. This has been maintained even when new servers are installed.

When upgrading from 12.0 to 12.5 gave no problem but now if fail2ban is detected it must be used either via plesk or as described excluded from the repo.
This is a pity
 
Now, with the new Plesk versions, I cannot see a reason for maintaining a stand-alone installation of fail2ban. Why not remove that installation and then install the Plesk module instead?
 
On a few servern is already converted. There are a lot of servers to convert. This requires a lot of time and until then it is simply excluded.
 
Back
Top