[Resolved] error.log timestamp - fail2ban

Discussion in 'General' started by Clockwork, Mar 20, 2010.

  1. Clockwork

    Clockwork Member

    Hello,

    I'm currently trying to ban ip's that reach the hard-limit through fail2ban. But fail2ban tells me that the timestamp used by litespeed in the error.log isn't supported.

    Is there any way to change the timestamp format in the error.log?
    Last edited by a moderator: Mar 21, 2010
  2. NiteWave

    NiteWave Administrator

    what's the current time stamp format in error.log?
  3. Clockwork

    Clockwork Member

    it's 2010-03-20 18:18:39.041
  4. NiteWave

    NiteWave Administrator

    it should be OK. The root cause may be somewhere else. I installed fail2ban on 2 of our servers some time back. exactly same time stamp as yours.
  5. Clockwork

    Clockwork Member

    okay, it seems they've added that timestamp in 0.8.1, after the update it works now, thanks.
  6. J.T.

    J.T. New Member

    Could either of you please share your Fail2Ban jail config?

    F2B was imperative in protecting our old Apache based web server and I'd really like to have it work well with Litespeed too. Especially vulnerability probes which were dealt with easily with the NoScript jail. I'm hoping LSWS logs those attempts to access known bad scripts that don't exist on our server too so Fail2Ban can block them.

Share This Page