On Wed, 29 May 2013, Mariusz Sawicki wrote:
> > > Version: 0.8.6-3wheezy1
> > > Priority: important

> > > In new stable version of fail2ban there is also problem with log
> > > rotation (by logrotate) when you don't use copytruncate option. Old log
> > > is renamed, gziped and new one created, ex. auth.log and fail2ban still
> > > has opened this unexisting file:

> > > fail2ban-  2342 2554        root    4r      REG              254,1 418124 
> > >     260631 /var/log/auth.log.1 (deleted)

> > > Bug is also reported here:

> > > https://bugzilla.redhat.com/show_bug.cgi?id=833056
> > hm -- that one about pyinotify backend issue which was fixed post 0.8.8
> > and is not relevant to 0.8.6 which doesn't support pyinotify (introduced
> > in 0.8.7)

> > so we would need to troubleshoot here separately:  what backend is used
> > on your system (

> I was using polling backend. But after returning to previous (wheezy's)
> version rotation works fine, also on another (upgraded to wheezy)
> system I could not observe previous failures after rotation. Hmm... I
> don't know why fail2ban was trying to read deleted file auth.log.1. I
> think my problem isn't repeatable so you could ignore it.

going through the pile of fail2ban bug reports in Debian... most
probably it is due to what we have fixed while working toward 0.8.11
release:

     - Polling backend: detect changes in the files not only based on
       mtime, but also on the size and inode.  It should allow for
       better detection of changes and log rotations on busy servers,
       older python 2.4, and file systems with precision of mtime only
       up to a second (e.g. ext3).

sounds relevant? ;-)

-- 
Yaroslav O. Halchenko, Ph.D.
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Senior Research Associate,     Psychological and Brain Sciences Dept.
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834                       Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik        


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to