Yes, I believe you are correct.  I've added my comment to that bug report.  I don't necessarily think it's a logrotate bug, it's just that the fail2ban logrotate config that comes packaged with fail2ban has the same logtarget settings as the fail2ban.conf and the real issue is as you pointed out the problem with the utf8 characters which you already fixed upstream.  I guess it has to be pushed up to the EPEL packagers to update to package.  Does that sound right?

On Wed, Oct 3, 2012 at 11:17 AM, Yaroslav Halchenko <> wrote:

On Wed, 03 Oct 2012, Yaroslav Halchenko wrote:
> ok:

> and I do not see one on the logrotate -- imho it is worth filing a
> bug report on this particular issue with logrotate.  There is already
> somewhat seeking an updated version ;)

ah -- wouldn't it be this one?

although I still think that it is an issue 32 which was fixed ;) even
with a default redirect to SYSLOG (I guess it is also the default
logtarget, isn't it?) -- it should be silent... and those spurious UTF8
characters confuse the log daemon causing them being broadcasted.

Yaroslav O. Halchenko
Postdoctoral Fellow,   Department of Psychological and Brain Sciences
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834                       Fax: +1 (603) 646-1419

Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
Fail2ban-users mailing list

Tomas Hajek
Systems Administrator
Information Technology

Phone: (810) 762-7887
Fax: (810) 762-9819
1700 University Avenue ~ Flint, MI  48504

Kettering University