• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Fail2ban errors in log after domain change !

Status
Not open for further replies.

Pascal_DEVIF

New Pleskian
Hi,
After changing website domain name (from development one -dev-domain.com- to production one) we have this error in fail2ban.log :

2015-02-01 06:46:41,176 fail2ban.filter [2848]: ERROR Unable to open /var/www/vhosts/system/dev-domain.com/logs/proxy_access_log
2015-02-01 06:46:41,176 fail2ban.filter [2848]: ERROR [Errno 2] No such file or directory: '/var/www/vhosts/system/dev-domain.com/logs/proxy_access_log'
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/server/filter.py", line 520, in getFailures
has_content = container.open()
File "/usr/lib/python2.7/dist-packages/server/filter.py", line 601, in open
self.__handler = open(self.__filename)
IOError: [Errno 2] No such file or directory: '/var/www/vhosts/system/dev-domain.com/logs/proxy_access_log'

A way to fix that ?
 
Try to restart fail2ban with

# /etc/init.d/fail2ban stop
# /etc/init.d/fail2ban start
 
Fail2ban already restarted by Plesk Panel many times as i added lot of IP to whitelist.

Whatever i tried to restart by console with your commands.
For now (some minutes after) it seems ok.
I will tell you if error appear again.

Thanks.
 
Status
Not open for further replies.
Back
Top