Search results

Hi, Thanks for your comments. I need the EPEL repo on my servers for other packages that I run. I see now that the best thing to do would have been to exclude Fail2Ban from EPEL intially, which would have ensured that a Plesk compatible version of Fai2Ban was installed. Having said that, I've...

I decided to try getting back to Fail2Ban 0.9.2 as this has numerous improvements compared to 0.8.13 and has worked fine with Plesk 12.0.18. So, what I did was: removing fail2ban completely excluded fail2ban from the EPEL repo installing fail2ban 0.9.2 manually...

Reporting back ... The suggested procedure worked perfectly -- thanks. What I actually ended up doing was: removing fail2ban completely excluding fail2ban from the EPEL repo installing fail2ban 0.9.2 manually (https://github.com/fail2ban/fail2ban/archive/0.9.2.tar.gz) So far all working...

I've done this on one of my servers and Fail2Ban 0.8.13 was installed from repo: PSA_12_0_18-dist. I haven't reinstalled my custom jails and filters etc, but so far so good. Shame to have to downgrade back to 0.8.x but I guess it's not really such a big deal. I presume I could manually install...

I will try the uninstall and reinstall f2b 0.9.2 from Plesk repo today. Though, as mentioned on the other thread (http://talk.plesk.com/threads/fail2ban-problems-in-plesk-12-0-18-update-68.335009/#post-788590) f2b 0.9.3 itself is working fine on CentOS 6.7 / iptables 1.4.7 (the f2b changelog...

Thanks so much for your help, I will try that out and report back. Weird thing is... Fail2Ban 0.9.3 itself (with CentOS 6.7, iptables 1.4.7) seems to be working fine (with the -w option disabled). F2B server runs fine, Jails load and successfully ban ips -- all seems to be working perfectly...

Hi, Thanks for your comments @roadrash. Interesting to hear I'm not alone, I'm having serious issues with Fail2ban 0.9.3, CentOS 6.7 and Plesk 12.0.18 (thread here: http://talk.plesk.com/threads/plesk-12-0-18-update-68-and-fail2ban-0-9-3-problem.335183/). When you say that "F2B 0.9.3 will no...

OK, thanks very much for your help so far. Odin Support: can you help? I have 2 Plesk 12.0.18 CentOS 6.7 servers with this same issue?

On further investigation it appears that the Starting: filwrpr ... lines start writing to panel.log as soon as I log into the panel, if I log out they stop. Fail2Ban server isn't even running now.

Hi, Well, I'm not having much luck. Here's what I've done: removed fail2ban with plesk installer, via command line removed /etc/fail2ban/ remove /var/log/fail2ban.log restarted server installed fail2ban with plesk installer, via command line I now have a completely fresh Fail2ban 0.9.3 All...

Hi again, Thanks, yes -- I'll try a reinstall. I know how to flush iptables, what I can't figure out is how to reset fail2ban's database, there doesn't seem to be anyway to do this. Thanks again.

Hello, I have enabled Plesk panel debug as suggested. I have also followed instructions as per: http://kb.odin.com/120312 My /usr/local/psa/admin/conf/php.ini file had no entry for 'pdo_mysql.default_socket' at all, so I added it: pdo_mysql.default_socket = /var/run/mysqld/mysqld.sock I...

Hi, Thanks so much for your suggestion. I tried a full server reboot, and now have these logs to share... These were generated after a server restart, when I get back to this, I'll switch on Plesk debug logging as you suggest and see if there is more information. Thanks again for your help...

Hi, I have 2 servers running Plesk 12.0.18 update #68, CentOS 6.7. Since the Plesk autoupdater installed fail2ban 0.9.3 I can no longer access the main Fail2Ban "Banned IP addresses" page in Plesk. The page never loads, and eventually times-out. I can get to the Plesk Fail2Ban settings page...

Hi, I have had a similar situation too, this is to do with Fail2Ban being updated, and your Fail2Ban configuration requires updating, and the Fail2Ban server needs restarting. I believe the difference is because CentOS 6.7 has fail2ban 0.9.2, whereas the older CentOS versions still have 0.8.x...

Thank you for the response.

I have a NAS mount which I use for my Plesk backups - this works fine for user and admin scheduled Plesk backups, but whenever the Plesk Auto-installer runs it attempts to CHOWN the MySQL preupgrade backup and fails with a permissions error: chown: changing ownership of...

Shameless bump ... No one? Still trying to resolve this issue, can anyone help? Thanks.

P.S. I just tried adding "users," to the fstab config: //SERVER/SHARE /media/nas/ cifs users,username=USERNAME,password=PASSWORD,uid=0,gid=0 0 0 ... but it didn't help, although the error in the log is slightly different now: Stopping psa... Stopping sw-engine-fpm: [ OK ] done chown...

Hi, My server is a VMWARE Cloud Server, CentOS 6.7, Plesk 12.0.18. My main disk was getting full, but rather than add more space to the main drive, I decided to get a NAS drive and move my Plesk Backups onto there (it's much cheaper, and I'll only use it for backups) I mounted the NAS share...