Yaroslav Halchenko schrieb:
> Hi Willi
> 
> Thank you for your rapid response
> 
>> Can you provide me a version of 0.7.x for sarge? I'd like to test before
>> I upload.
> 
> I will package 0.7 for sarge hopefully later on today: I am partying now
> ;-)
> 
> As for locale issue, I hope this would help
> 
> ,---------------------------------------------------------
> | add
> | export LANG=C
> | to the initial statements in /etc/init.d/fail2ban.
> `---

Yes it does. (at least on my sarge box with 0.6)

I've found an issue on sid with

# logwatch --print --service fail2ban

 ################### Logwatch 7.3.1 (09/15/06) ####################
        Processing Initiated: Mon Dec  4 15:15:05 2006
        Date Range Processed: yesterday
                              ( 2006-Dec-03 )
                              Period is day.
      Detail Level of Output: 5
              Type of Output: unformatted
           Logfiles for Host: wmiwilli
  ##################################################################

 --------------------- fail2ban-messages Begin ------------------------

 **Unmatched Entries**
 iptables -F fail2ban-<name>
 iptables -X fail2ban-<name>
 iptables -A fail2ban-<name> -j RETURN
 iptables -I INPUT -p <protocol> --dport <port> -j fail2ban-<name>

 ---------------------- fail2ban-messages End -------------------------


 ###################### Logwatch End #########################

which is now surprise because (see attachment, snippet of fail2ban.log).
I recommend that fail2ban replaces the newlines with ";" before logging.
This happened with 0.7.4-3 on sid.

Willi




>> 2006-12-03 11:54:19,684 ERROR: Please check the format and your locale
>> settings.
>> 2006-12-03 11:54:19,685 ERROR: time data did not match format:  data=Dec
>>  3 06:58:00  fmt=%b %d %H:%M:%S
>> 2006-12-03 11:54:19,686 ERROR: Please check the format and your locale
>> settings.
>>> ...<
> 
> 
>> occur, and the logwatch email had 6MB on a really small server, where
>> the normal size is 40 KB....
> yeah... fail2ban should have better just died if felt something weird...
> But I hope this issue would not come up in 0.7. or latest 0.6 due to fix
> with that export line
> 
> 
> 

2006-12-04 15:10:20,531 fail2ban.actions.action: INFO   Set actionBan = 
iptables -I fail2ban-<name> 1 -s <ip> -j DROP
2006-12-04 15:10:20,533 fail2ban.actions.action: INFO   Set actionStop = 
iptables -D INPUT -p <protocol> --dport <port> -j fail2ban-<name>
iptables -F fail2ban-<name>
iptables -X fail2ban-<name>
2006-12-04 15:10:20,535 fail2ban.actions.action: INFO   Set actionStart = 
iptables -N fail2ban-<name>
iptables -A fail2ban-<name> -j RETURN
iptables -I INPUT -p <protocol> --dport <port> -j fail2ban-<name>

Reply via email to