Weird error. Ispconfig 3.0.2.2 Debian lenny Fail2ban installed but I get this message on control pannel: fail2ban is not installed at this server. See more (for debian) here... # ps -A | grep fail 4337 ? 00:02:03 fail2ban-server # ls -la /var/log | grep "fail" -rw-r----- 1 root adm 0 11 jul 06:25 fail2ban.log -rw-r----- 1 root adm 0 4 jul 06:25 fail2ban.log.1 -rw-r----- 1 root adm 290 4 jul 06:25 fail2ban.log.2.gz -rw-r----- 1 root adm 333 27 jun 06:25 fail2ban.log.3.gz -rw-r--r-- 1 root root 160320 10 jul 17:28 faillog Where's the problem???
# which fail2ban-client /usr/bin/fail2ban-client I reload fail2ban and now I get this: # /etc/init.d/fail2ban restart Restarting authentication failure monitor: fail2ban failed! where can I check??
hmm nothing works (monitor), but the sites work well (website, ftp, db) http://www.pict.com/view/3826363/800/ispconfig http://www.pict.com/view/3826366/800/ispconfig http://www.pict.com/view/3826368/800/ispconfig http://www.pict.com/view/3826371/800/ispconfig http://www.pict.com/view/3826374/800/ispconfig http://www.pict.com/view/3826378/800/ispconfig any idea ???
What exactly have you done before the monitor stopped working and how is this related to cubecells thread that you added your question to?
before it worked well but yesterday I added some info on the DNS(soa), and hop nothing works !! This morning I deleted the entry in DNS, but it still does not work .... http://www.pict.com/view/3826425/800/ispconfig
@cubecells: these answers are not related to your problem. @007007: Most likely the databse dont get filled as the server is not able to find the mysql serveranymore to insert the data which caused by the wrong dns record. As this affects most likely also the process that writes the data to disk, then your dns changes have not been removed yet as the access to the mysql databse is blocked. What you can try is to stop the local dns server for a few minutes and wait. Hopefully the system is able to connect then to mysql gaian and so update the records and rewrite the dns.
ok, the solution is the stop dns with this command : /etc/init.d/mydns stop and wait, after : /etc/init.d/mydns start yes ?