fail2ban, jail stopped, apache log not found

Discussion in 'Server Operation' started by TheRudy, Dec 24, 2014.

  1. TheRudy

    TheRudy Member

    Hey guys,

    I have fail2ban running, all is good and I've set apache WordPress login spam filter. It is running great! The problem is that the filter basically checks all the access.log files for each domain/subdomain and some of the domains/subdomains don't get hit daily, some probably not getting any hits per week.

    The result is that once the log rotate runs the access.log is no where to be found until the next domain/subdomain hit (visit).

    Of course fail2ban checks a few times for the log if found missing and after a while it stops the jail which is annoying.

    Any of you guys know how I could make the access.log for each domain/subdomain to be created daily, if it doesn't exist?

    I though of doing a daily cronjob that runs "touch /var/log/ispconfig/..../access.log" for each site.

    Is there any better way of doing it?

    Edit: Just realized that ISPConfig3 is rotating logs and not logrotate for web logs. Hmm..
    Edit 2: Am I drunk? vlogger is doing that.. Oh crap..

    Edit 3: Solution, use /var/log/apache2/other_vhosts_access.log path in the jail for the WP login spam filter.
    Last edited: Dec 24, 2014

Share This Page