Bug#696087: Wheezy's fail2ban is affected by logrotation

2013-11-16 Thread Yaroslav Halchenko
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

Bug#696087: Wheezy's fail2ban is affected by logrotation

2013-05-29 Thread Yaroslav Halchenko
On Wed, 29 May 2013, Mariusz Sawicki wrote: > > 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 cou

Bug#696087: Wheezy's fail2ban is affected by logrotation

2013-05-29 Thread Mariusz Sawicki
sob, 25 maj 2013, 12:08:16 -0400, Yaroslav Halchenko napisał(a): > On Thu, 23 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 opti

Bug#696087: Wheezy's fail2ban is affected by logrotation

2013-05-25 Thread Yaroslav Halchenko
On Thu, 23 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 fail2

Bug#696087: Wheezy's fail2ban is affected by logrotation

2013-05-22 Thread Mariusz Sawicki
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-