-
Notifications
You must be signed in to change notification settings - Fork 1
/
bugs.json
3893 lines (3893 loc) · 245 KB
/
bugs.json
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
{"tickets": [{
"status": "closed",
"reported_by_id": "4e8a1d76b9363c20cf000dcf",
"related_artifacts": [],
"attachments": [],
"reported_by": "lostcontrol",
"description": "The fail2ban log file can be access with write\r\npermission by everyone. This could be a security issue.\r\n\r\nThanks to Yaroslav Halchenko who found this issue.",
"labels": [],
"assigned_to": "nobody",
"assigned_to_id": null,
"private": false,
"summary": "fail2ban.log is world-open for writing",
"discussion_thread": {
"_id": "4702890a",
"posts": [
{
"text": "Logged In: YES \nuser\\_id=933467\n\nFixed in the CVS branch FAIL2BAN-0\\_5",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2005-07-12 12:47:41",
"slug": "37a9",
"subject": "#1 fail2ban.log is world-open for writing"
},
{
"text": "- **status**: open --> closed",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2005-07-12 12:47:41",
"slug": "c1d5",
"subject": "#1 fail2ban.log is world-open for writing"
}
],
"discussion_id": "51acf2192718464f1a12f6bd",
"subject": ""
},
"mod_date": "2005-07-12 12:47:41",
"votes_down": 0,
"votes_up": 0,
"_id": "51acf21c2718464f1a12f6c7",
"discussion_thread_url": "http://sourceforge.net/rest/p/fail2ban/bugs/_discuss/thread/4702890a/",
"ticket_num": 1,
"custom_fields": {
"_priority": "9"
},
"created_date": "2005-07-08 09:57:22"
},{
"status": "closed",
"reported_by_id": "51769796e88f3d77c1994eb5",
"related_artifacts": [],
"attachments": [],
"reported_by": "neversleepy",
"description": "If the config file option \"ignoreip\" is blank, fail2ban\r\nexits with error: \"socket.error: illegal IP address\r\nstring passed to inet\\_aton\"",
"labels": [],
"assigned_to": "nobody",
"assigned_to_id": null,
"private": false,
"summary": "crash on program load if \"ignoreip\" is blank.",
"discussion_thread": {
"_id": "7029482f",
"posts": [
{
"text": "Logged In: NO \n\nI'm unable to reproduce this bug. Which version of Python do\r\nyou have?\r\n\r\nThank you",
"attachments": [],
"author": "nobody",
"timestamp": "2005-07-19 16:34:42",
"slug": "169f",
"subject": "#2 crash on program load if \"ignoreip\" is blank."
},
{
"text": "Fail2Ban config file (produces ignore IP error)",
"attachments": [
{
"url": "http://sourceforge.net/p/fail2ban/bugs/_discuss/thread/7029482f/4e89/attachment/fail2ban.conf",
"bytes": 7316
}
],
"author": "neversleepy",
"timestamp": "2005-07-20 17:58:19",
"slug": "4e89",
"subject": "#2 crash on program load if \"ignoreip\" is blank."
},
{
"text": "Logged In: YES \nuser\\_id=634475\n\nI have attached a copy of the config file which reproduced\r\nthis bug.\r\n\r\nI am on Debian\\(Sarge\\), using Python 2.3.5\\(2\\). \\(2\\) being\r\ndebian's revision number.\r\nUsing Yaroslav Halchenko's package version 0.5.0-1\r\n\r\nI just did a lot of checking between two systems and\r\nresolved this problem by ensuring the following Debian\r\npackages were at Debian-Sarge level \\(upgrading\\): hostname\r\niptables ncurses-base ncurses-bin sed strace whois\r\n\r\nIf one or more of these applications are needed in fail2ban;\r\nit would be good for Yaroslav to put a version requirement\r\non his package definition for Sarge versions and newer.\r\n\r\nSo it was an older version of one of these applications that\r\ncaused the issue.",
"attachments": [],
"author": "neversleepy",
"timestamp": "2005-07-20 17:58:19",
"slug": "bd43",
"subject": "#2 crash on program load if \"ignoreip\" is blank."
},
{
"text": "Logged In: YES \nuser\\_id=634475\n\nThis is random.\r\n\r\nNoticed fail2ban not running on the server, ran in debug\r\nmode, and now the illegal IP address errors for \"ignoreip\"\r\nare back \\(when the field is blank\\).\r\n\r\nNo changes made, after reporting sucessful a couple hours ago.",
"attachments": [],
"author": "neversleepy",
"timestamp": "2005-07-20 20:19:54",
"slug": "a0fc",
"subject": "#2 crash on program load if \"ignoreip\" is blank."
},
{
"text": "Logged In: NO \n\nThank you\r\n\r\nI can reproduce it now :-\\) I just copy your \"ignoreip\"\r\nsection to my config file and it crashes :-/\r\n\r\nI will try to fix this before 0.5.1.",
"attachments": [],
"author": "nobody",
"timestamp": "2005-07-22 20:11:59",
"slug": "993c",
"subject": "#2 crash on program load if \"ignoreip\" is blank."
},
{
"text": "Logged In: YES \nuser\\_id=933467\n\nFixed in CVS branch FAIL2BAN-0\\_5",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2005-07-22 21:15:28",
"slug": "b97c",
"subject": "#2 crash on program load if \"ignoreip\" is blank."
},
{
"text": "- **status**: open --> closed",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2005-07-22 21:15:28",
"slug": "cd16",
"subject": "#2 crash on program load if \"ignoreip\" is blank."
}
],
"discussion_id": "51acf2192718464f1a12f6bd",
"subject": ""
},
"mod_date": "2005-07-22 21:15:28",
"votes_down": 0,
"votes_up": 0,
"_id": "51acf21d2718464f1a12f6d8",
"discussion_thread_url": "http://sourceforge.net/rest/p/fail2ban/bugs/_discuss/thread/7029482f/",
"ticket_num": 2,
"custom_fields": {
"_priority": "5"
},
"created_date": "2005-07-16 20:57:42"
},{
"status": "closed",
"reported_by_id": "51769796e88f3d77c1994eb5",
"related_artifacts": [],
"attachments": [],
"reported_by": "neversleepy",
"description": "fail2ban does not properly check for an invalid .pid\r\nfile upon startup.\r\n\r\nWhen the .pid file of a crashed fail2ban session\r\nexists, no checks are made by a new daemon to verify\r\nthe process ID in the .pid is truly valid.\r\n\r\nError given by debug mode: \"Fail2Ban already running\r\nwith PID <pid\\# in fail2ban.pid file>\"\r\n\r\nA check of running processes verifies fail2ban is truly\r\nnot running on this PID.\r\n\r\nSimply deleting the fail2ban.pid file; is a\r\nwork-around. Although this is not desirealbe on\r\nsystems duing bootup.",
"labels": [],
"assigned_to": "nobody",
"assigned_to_id": null,
"private": false,
"summary": "improper checking of fail2ban.pid file upon program startup",
"discussion_thread": {
"_id": "7d264d04",
"posts": [
{
"text": "Logged In: NO \n\nI don't know how this handle by others daemons. Checking if\r\na fail2ban process is already running with the PID is the\r\nsame as checking for a running instance without a PID file.\r\n\r\nApcupsd doesn't check for a running instance if it finds a\r\nPID file.\r\n\r\nI don't know how Apache, MySQL, etc, handle this.\r\n\r\nThank you",
"attachments": [],
"author": "nobody",
"timestamp": "2005-07-19 16:46:32",
"slug": "d267",
"subject": "#3 improper checking of fail2ban.pid file upon program startup"
},
{
"text": "Logged In: YES \nuser\\_id=820001\n\nPID files are a pain =\\) Many daemons/apps use them and \r\nlater fail to start when for some reason the file is still existing.\r\n\r\nI thought the reason to have the .pid file was not to use the .\r\npid file iteslf as evidence, but to also check the \"PID\" specified \r\ninside the file to see if the application is running. \r\n\r\nAnother, easy way is also to do \\`pidof fail2ban\\` which is \r\ncleaner and nicer than a .pid file. What do you think of this?",
"attachments": [],
"author": "andewid",
"timestamp": "2005-07-20 10:42:06",
"slug": "c825",
"subject": "#3 improper checking of fail2ban.pid file upon program startup"
},
{
"text": "Logged In: YES \nuser\\_id=634475\n\nI made an init.d script previously I can adapt to fit this.\r\nI'll send it over this week. :\\)",
"attachments": [],
"author": "neversleepy",
"timestamp": "2005-07-20 17:02:53",
"slug": "8fe3",
"subject": "#3 improper checking of fail2ban.pid file upon program startup"
},
{
"text": "Logged In: NO \n\nDo you think it would be better to use \"pidof\" or \"ps|grep\"\r\nin order to :\r\n\r\n1/ Check if a fail2ban process is already running\r\n2/ Get the PID of the running process in order to kill it\r\n\\(fail2ban -k\\)\r\n\r\nI don't really like using system commands to do that :-/\r\nMoreover is \"pidof\" available on all systems? Does someone\r\nknow how this is handle in mysql or apache?",
"attachments": [],
"author": "nobody",
"timestamp": "2005-07-22 07:44:48",
"slug": "0664",
"subject": "#3 improper checking of fail2ban.pid file upon program startup"
},
{
"text": "Logged In: YES \nuser\\_id=933467\n\nShould be \"fixed\" in CVS branch FAIL2BAN-0\\_5.\r\n\r\nThe PID lock file should be removed when Fail2Ban crashes.",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2005-08-04 20:54:36",
"slug": "6f0a",
"subject": "#3 improper checking of fail2ban.pid file upon program startup"
},
{
"text": "- **status**: open --> closed",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2005-08-04 20:54:36",
"slug": "934f",
"subject": "#3 improper checking of fail2ban.pid file upon program startup"
}
],
"discussion_id": "51acf2192718464f1a12f6bd",
"subject": ""
},
"mod_date": "2005-08-04 20:54:36",
"votes_down": 0,
"votes_up": 0,
"_id": "51acf2262718464f1a12f70a",
"discussion_thread_url": "http://sourceforge.net/rest/p/fail2ban/bugs/_discuss/thread/7d264d04/",
"ticket_num": 3,
"custom_fields": {
"_priority": "5"
},
"created_date": "2005-07-16 21:04:10"
},{
"status": "closed",
"reported_by_id": "50279623fd48f80fdc30fb9f",
"related_artifacts": [],
"attachments": [],
"reported_by": "tom_crane",
"description": "I have encountered some problems using fail2ban.\r\n\r\n\\(1\\) With version 0.4.1 it is being confused by the\r\ntimestamps obtained from the logfile\r\n\\(/var/log/messages\\). This file is fairly large: 69MB &\r\n788233 lines. It also claims the logfile has been\r\nrotated which it certainly has not. After processing\r\nthe whole file, it appears to go back to the beginning\r\nand start all over again, unbanning the just-banned IPs\r\nin the process.\r\n\r\n\\(2\\) I tried version 0.5.0 but it fails crashes at startup.\r\n\r\n\\(3\\) Here are my system details;\r\nOS: Slackware 9.0-current Linux\r\nlog4py: version 1.3\r\nPython: Version 2.4.1\r\n\r\n\\(4\\) I am attaching the conf files and debug O/P in a\r\ntarball.\r\nThe file miscinfo.txt contains some samples from my\r\nmessages file, taken from the top & bottom for the\r\ntimestamp information, and a sample of some sshd probers.\r\n\r\n\\(5\\) Finally, an iptables suggestion: I think it would\r\nbe preferable to have fail2ban write its stuff to a\r\nprivate chain, which could then optionally be inserted\r\ninto the input chain a few places downstream, eg.\r\n\r\niptables -N fail2ban\r\niptables -I INPUT 5 -j fail2ban\r\n\r\nThanks\r\nTom Crane",
"labels": [],
"assigned_to": "nobody",
"assigned_to_id": null,
"private": false,
"summary": "Some misc. fail2ban problems",
"discussion_thread": {
"_id": "cd592130",
"posts": [
{
"text": "tarball with debugging O/P, conf files etc.",
"attachments": [
{
"url": "http://sourceforge.net/p/fail2ban/bugs/_discuss/thread/cd592130/e0e5/attachment/debugging.tar.gz",
"bytes": 63069
}
],
"author": "tom_crane",
"timestamp": "2005-07-20 18:08:43",
"slug": "e0e5",
"subject": "#4 Some misc. fail2ban problems"
},
{
"text": "Logged In: NO \n\n1/ You are right. Fail2ban is being confused by the\r\ntimestamps. When no year field is available, Fail2ban uses\r\nthe current year. Thus, it thinks that Oct 10 is Oct 10\r\n2005\\. I will fix this. Thank you :-\\)\r\n\r\n2/ With Fail2Ban >= 0.5, you must start it with\r\n\"/usr/bin/fail2ban\". You must also delete the file\r\n\"/usr/bin/fail2ban.py\".\r\n\r\n5/ This is the default config in CVS and will be in 0.5.1\r\n\r\nThank you very much for the tarball, it was really helpful \\!",
"attachments": [],
"author": "nobody",
"timestamp": "2005-07-22 20:02:35",
"slug": "91d6",
"subject": "#4 Some misc. fail2ban problems"
},
{
"text": "Logged In: YES \nuser\\_id=933467\n\nFixed in CVS branch FAIL2BAN-0\\_5",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2005-07-22 21:16:32",
"slug": "2b59",
"subject": "#4 Some misc. fail2ban problems"
},
{
"text": "- **status**: open --> closed",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2005-07-22 21:16:32",
"slug": "977f",
"subject": "#4 Some misc. fail2ban problems"
}
],
"discussion_id": "51acf2192718464f1a12f6bd",
"subject": ""
},
"mod_date": "2005-07-22 21:16:32",
"votes_down": 0,
"votes_up": 0,
"_id": "51acf2292718464f1a12f733",
"discussion_thread_url": "http://sourceforge.net/rest/p/fail2ban/bugs/_discuss/thread/cd592130/",
"ticket_num": 4,
"custom_fields": {
"_priority": "5"
},
"created_date": "2005-07-20 18:08:42"
},{
"status": "closed",
"reported_by_id": "50279623fd48f80fdc30fb9f",
"related_artifacts": [],
"attachments": [],
"reported_by": "tom_crane",
"description": "I'm pleased to say that I now have version 0.5.1\r\nworking. However, I feel the memory usage is\r\nexcessive. It increases as it initially processes my\r\nrather large \\(69MB\\) syslog file and then retains it\r\nthereafter. Currently the fail2ban process has >100MB\r\nvirtual size.\r\n\r\nI presume fail2ban is storing the entire contents of\r\nthe syslog file in memory? Does it really need to do\r\nthis? Would a 'tail -f' type scheme be better?\r\n\r\nAn unrelated suggestion: Could you provide an option to\r\nlog via syslogd instead of a plain logfile.\r\n\r\nThanks\r\nTom Crane \r\n",
"labels": [],
"assigned_to": "nobody",
"assigned_to_id": null,
"private": false,
"summary": "Excessive memory usage",
"discussion_thread": {
"_id": "2ccf5a6b",
"posts": [
{
"text": "Logged In: YES \nuser\\_id=933467\n\nFixed in CVS branch FAIL2BAN-0\\_5\r\n\r\nI was using readlines\\(\\) which load the whole file in memory\r\n:-/ Fail2ban now uses around 7MB when parsing a >100MB log file.\r\n\r\nFor syslogd, please look at the \"logtargets\" in\r\nfail2ban.conf.default ;-\\)\r\n\r\nThank you for this bug report",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2005-07-28 20:43:55",
"slug": "4ea6",
"subject": "#5 Excessive memory usage"
},
{
"text": "- **status**: open --> closed",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2005-07-28 20:43:55",
"slug": "067f",
"subject": "#5 Excessive memory usage"
}
],
"discussion_id": "51acf2192718464f1a12f6bd",
"subject": ""
},
"mod_date": "2005-07-28 20:43:55",
"votes_down": 0,
"votes_up": 0,
"_id": "51acf22b2718464f1a12f755",
"discussion_thread_url": "http://sourceforge.net/rest/p/fail2ban/bugs/_discuss/thread/2ccf5a6b/",
"ticket_num": 5,
"custom_fields": {
"_priority": "5"
},
"created_date": "2005-07-27 19:24:05"
},{
"status": "closed-fixed",
"reported_by_id": "50279623fd48f80fdc30fb9f",
"related_artifacts": [],
"attachments": [],
"reported_by": "tom_crane",
"description": "Hello,\r\nI have installed 0.5.2 but am still encountering\r\nproblems. Fail2ban is still incorrectly claiming that\r\nmy /var/log/messages file is being rotated, leading to\r\nthe file being rescanned and some old sshd logfails\r\nbeing banned. I have been running 0.5.2 with -vv and\r\nresults are in the attached tarball. NB: re; the sample\r\nof my mesages file, the entries dated the 9th August --\r\nthese logs are from at least a year ago.\r\n\r\nPrior to installing 0.5.2 I was running the CVS version\r\nof 0.5.1. There was also spurious rescanning but I\r\ndon't have much detail \\(was running without -v\\). The\r\nreason for mentioning this, is that some local IPs with\r\nvery old logfails in the messages file were being\r\nspuriously banned -- despite their IP block being\r\nexcluded via the conf file ignoreip line. See my\r\ncurrent conf file in the tarball.\r\n\r\nThanks\r\nTom Crane.\r\n\r\nPs. apologies for the double post",
"labels": [],
"assigned_to": "nobody",
"assigned_to_id": null,
"private": false,
"summary": "Datastamp / spurious log rotation",
"discussion_thread": {
"_id": "641941e9",
"posts": [
{
"text": "tarball",
"attachments": [
{
"url": "http://sourceforge.net/p/fail2ban/bugs/_discuss/thread/641941e9/f68b/attachment/09aug05.tar.gz",
"bytes": 11846
}
],
"author": "tom_crane",
"timestamp": "2005-08-10 18:18:41",
"slug": "f68b",
"subject": "#6 Datastamp / spurious log rotation"
},
{
"text": "Logged In: YES \nuser\\_id=933467\n\n\"despite their IP block being excluded via the conf file\r\nignoreip line\"\r\n\r\nmmhh... Try \"ignoreip = 134.219.0.0/16\" and not /24\r\n\r\nDo you have different timestamp patterns in\r\n/var/log/messages or line with no timestamp ? If the latest\r\nline of the file has no timestamp, getTime\\(\\) will return 0.\r\nThis could be the problem...",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2005-08-11 21:57:47",
"slug": "e3f0",
"subject": "#6 Datastamp / spurious log rotation"
},
{
"text": "Logged In: YES \nuser\\_id=1222528\n\nThanks for pointing out the ignoreip problem. I'd just\r\ncopied the example without remembering I was on a class B\r\nnetwork\\!\r\n\r\nre; the timestamps -- there are no lines without timestamps\r\nor an alternative format. The following regex egrep matches\r\nall lines and with -v it matches no lines.\r\n\r\negrep '^\\[\\[:alpha:\\]\\]\\{3\\} \\{1,2\\}\\[0-9\\]\\{1,2\\}\r\n\\[0-9\\]\\{2\\}:\\[0-9\\]\\{2\\}:\\[0-9\\]\\{2\\} ' /var/log/messages\r\n\r\nI have never seen an incomplete latest line. One thing the\r\nfile does contain are instances where the time occasionally\r\n'goes backards'. It takes a few seconds after the system\r\nboots for the xntpd daemon to kick in and set the correct\r\nsystem time. Surely fail2ban should not choke on that?\r\n\r\nI have put a file of the first 16 columns of my messages\r\nfile on http://www.mklab.rhul.ac.uk/~tom/messages.16nq.bz2\r\nsince it is quite big.\r\nI hope this is helpful.\r\n\r\nThanks Tom.\r\n",
"attachments": [],
"author": "tom_crane",
"timestamp": "2005-08-12 17:28:54",
"slug": "cd13",
"subject": "#6 Datastamp / spurious log rotation"
},
{
"text": "Logged In: YES \nuser\\_id=933467\n\nI have not had enough time yet to look at your log file :-\\(\r\nSorry...\r\n\r\nThe ignoreip problem could also be caused by bug \\#1262345.\r\nIt is fixed in CVS.\r\n\r\nThank you",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2005-08-17 19:38:24",
"slug": "b367",
"subject": "#6 Datastamp / spurious log rotation"
},
{
"text": "Logged In: YES \nuser\\_id=1222528\n\nre; the datestamping problem -- I don't know Python at all\r\nbut had a quick look at the source and I agree it looks like\r\na last-line-blank problem. I imagine if syslogd just writes\r\nits logfile as a Unix byte stream, it must be possible for a\r\nprogram reading that file as a byte stream to catch it\r\nhaving just written an \\n. A few suggestions/questions;\r\n\r\n\\(1\\) If fail2ban encounters a blank line should it not simply\r\nskip it? Ie. not parse anything as a date that does not\r\nmatch a regex like the one I gave below?\r\n\r\n\\(2\\) Could you make me a debugging-modded fail2ban.py which\r\nchecks for and explicitly prints out a suitable message when\r\n-vv is given -- so we can tell for sure if it is blank lines?\r\n\r\n\\(3\\) If you don't agree with \\(1\\) above, how about simply\r\nrejecting any date parsed from the messages file which has a\r\nvalue of zero, for log-rotation checking purposes. Afterall\r\n\\(time\\_t\\)0 amounts to 1-jan-1970:00:00:00 or similar doesn't\r\nit? -- which should never be legitimately encountered...\r\n\r\nThanks\r\nTom.",
"attachments": [],
"author": "tom_crane",
"timestamp": "2005-08-19 19:18:55",
"slug": "f30a",
"subject": "#6 Datastamp / spurious log rotation"
},
{
"text": "Logged In: YES \nuser\\_id=933467\n\nI can not reproduce this bug... However I hope it is fixed\r\nin the latest CVS.\r\n\r\nMaybe you should purge your logs from time to time ;-\\)",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2005-09-05 19:58:33",
"slug": "ccc1",
"subject": "#6 Datastamp / spurious log rotation"
},
{
"text": "- **status**: open --> open-fixed",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2005-09-05 19:58:33",
"slug": "00a0",
"subject": "#6 Datastamp / spurious log rotation"
},
{
"text": "Logged In: YES \nuser\\_id=933467\n\nNo more news... Should be fixed now",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2005-11-20 17:13:10",
"slug": "3558",
"subject": "#6 Datastamp / spurious log rotation"
},
{
"text": "- **status**: open-fixed --> closed-fixed",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2005-11-20 17:13:10",
"slug": "75f4",
"subject": "#6 Datastamp / spurious log rotation"
}
],
"discussion_id": "51acf2192718464f1a12f6bd",
"subject": ""
},
"mod_date": "2005-11-20 17:13:10",
"votes_down": 0,
"votes_up": 0,
"_id": "51acf22c2718464f1a12f766",
"discussion_thread_url": "http://sourceforge.net/rest/p/fail2ban/bugs/_discuss/thread/641941e9/",
"ticket_num": 6,
"custom_fields": {
"_priority": "5"
},
"created_date": "2005-08-10 18:18:40"
},{
"status": "closed",
"reported_by_id": "512533472718463538332bc1",
"related_artifacts": [],
"attachments": [],
"reported_by": "ud3",
"description": "After the fix to \\#1239557, ignoreip no longer accepts\r\na.b.c.d/m as input.",
"labels": [],
"assigned_to": "nobody",
"assigned_to_id": null,
"private": false,
"summary": "ignoreip for networks broken",
"discussion_thread": {
"_id": "6ec8852a",
"posts": [
{
"text": "Logged In: YES \nuser\\_id=933467\n\nThank you \\!\r\n\r\nShould be fixed in CVS branch FAIL2BAN-0\\_5",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2005-08-17 19:33:29",
"slug": "f3cd",
"subject": "#7 ignoreip for networks broken"
},
{
"text": "- **status**: open --> closed",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2005-08-17 19:33:29",
"slug": "a027",
"subject": "#7 ignoreip for networks broken"
}
],
"discussion_id": "51acf2192718464f1a12f6bd",
"subject": ""
},
"mod_date": "2005-08-17 19:33:29",
"votes_down": 0,
"votes_up": 0,
"_id": "51acf22f2718464f1a12f79f",
"discussion_thread_url": "http://sourceforge.net/rest/p/fail2ban/bugs/_discuss/thread/6ec8852a/",
"ticket_num": 7,
"custom_fields": {
"_priority": "5"
},
"created_date": "2005-08-17 17:35:49"
},{
"status": "closed-fixed",
"reported_by_id": null,
"related_artifacts": [],
"attachments": [],
"reported_by": "*anonymous",
"description": "Hi,\r\n\r\nwhen sending email, fail2ban does not add a \"Date:\" header. Not all MTAs correct this error \\(and some will even correctly refuse mail without a Date\\). Below patch should solve the issue \\(note I'm not a python programmer, this was largely copied from http://groups.google.de/group/comp.lang.python/browse\\_thread/thread/8a9cfb2f9122ff06/7b8851a5e19cc839?lnk=st&q=smtplib+%22date+header%22&rnum=3&hl=de\\#7b8851a5e19cc839 \\).\r\n\r\n\\--- /usr/share/fail2ban/utils/mail.py-old 2005-09-09 19:04:30.000000000 +0200\r\n+++ /usr/share/fail2ban/utils/mail.py 2005-09-09 19:36:15.000000000 +0200\r\n@@ -27,6 +27,7 @@\r\nimport logging, smtplib\r\n\r\nfrom utils.strings import replaceTag\r\n+from time import strftime,gmtime\r\n\r\n\\# Gets the instance of the logger.\r\nlogSys = logging.getLogger\\(\"fail2ban\"\\)\r\n@@ -55,8 +56,9 @@\r\nsubj = replaceTag\\(subject, aInfo\\)\r\nmsg = replaceTag\\(message, aInfo\\)\r\n\r\n\\- mail = \\(\"From: %s\\r\\nTo: %s\\r\\nSubject: %s\\r\\n\\r\\n\" %\r\n\\- \\(self.fromAddr, \", \".join\\(self.toAddr\\), subj\\)\\) + msg\r\n\\+ mail = \\(\"From: %s\\r\\nTo: %s\\r\\nDate: %s\\r\\nSubject: %s\\r\\n\\r\\n\" %\r\n\\+ \\(self.fromAddr, \", \".join\\(self.toAddr\\),\r\n\\+ strftime\\(\"%a, %d %b %Y %H:%M:%S +0000\", gmtime\\(\\)\\), subj\\)\\) + msg\r\n\r\ntry:\r\nserver = smtplib.SMTP\\(self.host, self.port\\)\r\n",
"labels": [],
"assigned_to": "nobody",
"assigned_to_id": null,
"private": false,
"summary": "Add Date to email header (patch included)",
"discussion_thread": {
"_id": "3ea0161b",
"posts": [
{
"text": "- **status**: open --> closed",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2005-09-12 14:46:32",
"slug": "0dcb",
"subject": "#8 Add Date to email header (patch included)"
},
{
"text": "Logged In: YES \nuser\\_id=933467\n\nThank you \\!\r\n\r\nFixed in CVS branch FAIL2BAN-0\\_5",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2005-09-12 14:46:33",
"slug": "cf10",
"subject": "#8 Add Date to email header (patch included)"
},
{
"text": "- **status**: closed --> closed-fixed",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2005-09-12 14:46:33",
"slug": "4cfc",
"subject": "#8 Add Date to email header (patch included)"
}
],
"discussion_id": "51acf2192718464f1a12f6bd",
"subject": ""
},
"mod_date": "2005-09-12 14:46:33",
"votes_down": 0,
"votes_up": 0,
"_id": "51acf22f2718464f1a12f7b0",
"discussion_thread_url": "http://sourceforge.net/rest/p/fail2ban/bugs/_discuss/thread/3ea0161b/",
"ticket_num": 8,
"custom_fields": {
"_priority": "5"
},
"created_date": "2005-09-09 17:41:43"
},{
"status": "closed-fixed",
"reported_by_id": null,
"related_artifacts": [],
"attachments": [],
"reported_by": "*anonymous",
"description": "fail2ban is not finding failures that I'd like it to to\r\nprevent spam-probing of virtual domains on my server.\r\n\r\nhere is the configuration as I've entered it:\r\n\r\n\\[CourierSMTP\\]\r\nenabled = true\r\nlogfile = /var/log/mail.err\r\nfwstart = iptables -N fail2ban-smtp\r\niptables -I INPUT -p tcp --dport smtp -j\r\nfail2ban-smtp\r\niptables -A fail2ban-smtp -j RETURN\r\n\r\nfwend = iptables -D INPUT -p tcp --dport smtp -j\r\nfail2ban-smtp\r\niptables -D fail2ban-smtp -j RETURN\r\niptables -X fail2ban-smtp\r\n\r\nfwban = iptables -I fail2ban-smtp 1 -s <ip> -j DROP\r\nfwunban = iptables -D fail2ban-smtp -s <ip> -j DROP\r\n\r\ntimeregex = \\S\\{3\\} \\d\\{2\\} \\d\\{2\\}:\\d\\{2\\}:\\d\\{2\\}\r\ntimepattern = %%b %%d %%H:%%M:%%S\r\n\r\nfailregex = 550 User Unknown\r\n\r\nThe logs look like this:\r\n\r\nSep 23 13:19:04 SERVER courieresmtpd:\r\nerror,relay=::ffff:200.138.205.232,from=<pliq\\_ljgg\\_o\\_r\\[email protected]>,to=<[email protected]>:\r\n550 User unknown.\r\n\r\nYes, the from domain name is set to the to in this\r\nexample. As far as I can see the RE in the dns.py\r\nstringtoip function should catch the ip addres by\r\npattern here. SSH is working fine, but I'm getting\r\nabout a thousand of these probes a day in my mail.err,\r\nand I'd like very much to cut down on these.\r\n\r\nThanks,\r\n\r\n-Peter",
"labels": [],
"assigned_to": "lostcontrol",
"assigned_to_id": "4e8a1d76b9363c20cf000dcf",
"private": false,
"summary": "not finding failures four courier-smtp",
"discussion_thread": {
"_id": "a0dd4894",
"posts": [
{
"text": "Logged In: YES \nuser\\_id=933467\n\nFail2ban 0.6 and previous version cannot handle such things\r\nright. This will be changed in 0.7.",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2006-02-16 13:18:54",
"slug": "cbb4",
"subject": "#9 not finding failures four courier-smtp"
},
{
"text": "- **status**: open --> open-accepted",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2006-02-16 13:18:54",
"slug": "705d",
"subject": "#9 not finding failures four courier-smtp"
},
{
"text": "Logged In: YES \nuser\\_id=933467\n\nFixed in Subversion repository. Will be in 0.7.0.\r\n\r\nThere is no courier-smtp configuration yet but everything\r\nneeded to create one should be available.",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2006-08-22 06:19:09",
"slug": "6aad",
"subject": "#9 not finding failures four courier-smtp"
},
{
"text": "- **status**: open-accepted --> closed-fixed",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2006-08-22 06:19:09",
"slug": "5c4e",
"subject": "#9 not finding failures four courier-smtp"
}
],
"discussion_id": "51acf2192718464f1a12f6bd",
"subject": ""
},
"mod_date": "2006-08-22 06:19:09",
"votes_down": 0,
"votes_up": 0,
"_id": "51acf2302718464f1a12f7c6",
"discussion_thread_url": "http://sourceforge.net/rest/p/fail2ban/bugs/_discuss/thread/a0dd4894/",
"ticket_num": 9,
"custom_fields": {
"_priority": "5"
},
"created_date": "2005-09-23 17:44:17"
},{
"status": "closed-accepted",
"reported_by_id": "51acf2322718464f1a12f7e2",
"related_artifacts": [],
"attachments": [],
"reported_by": "zugeschmiert",
"description": "hi, here is a template that seems to work for me with\r\nvsftpd:\r\n\r\n\\[VSFTPD\\]\r\n\\# Option: enabled\r\n\\# Notes.: enable monitoring for this section.\r\n\\# Values: \\[true | false\\] Default: true\r\n\\#\r\nenabled = true\r\n\r\n\\# Option: logfile\r\n\\# Notes.: logfile to monitor.\r\n\\# Values: FILE Default: /var/log/secure\r\n\\#\r\nlogfile = /var/log/vsftpd.log\r\n\r\n\\# Option: fwstart\r\n\\# Notes.: command executed once at the start of Fail2Ban\r\n\\# Values: CMD Default:\r\n\\#\r\nfwstart = iptables -N fail2ban-vsftpd\r\niptables -I INPUT -p tcp --dport ftp -j\r\nfail2ban-vsftpd\r\niptables -A fail2ban-vsftpd -j RETURN\r\n\r\n\\# Option: fwend\r\n\\# Notes.: command executed once at the end of Fail2Ban\r\n\\# Values: CMD Default:\r\n\\#\r\nfwend = iptables -D INPUT -p tcp --dport ftp -j\r\nfail2ban-vsftpd\r\niptables -F fail2ban-vsftpd\r\niptables -X fail2ban-vsftpd\r\n\r\n\\# Option: fwcheck\r\n\\# Notes.: command executed once before each fwban command\r\n\\# Values: CMD Default:\r\n\\#\r\nfwcheck = iptables -L INPUT | grep -q fail2ban-vsftpd\r\n\r\n\\# Option: fwbanrule\r\n\\# Notes.: command executed when banning an IP. Take\r\ncare that the\r\n\\# command is executed with Fail2Ban user rights.\r\n\\# Tags: <ip> IP address\r\n\\# <failures> number of failures\r\n\\# <failtime> unix timestamp of the last failure\r\n\\# <bantime> unix timestamp of the ban time\r\n\\# Values: CMD\r\n\\# Default: iptables -I INPUT 1 -s <ip> -j DROP\r\n\\#\r\nfwban = iptables -I fail2ban-vsftpd 1 -s <ip> -j DROP\r\n\r\n\\# Option: fwunbanrule\r\n\\# Notes.: command executed when unbanning an IP. Take\r\ncare that the\r\n\\# command is executed with Fail2Ban user rights.\r\n\\# Tags: <ip> IP address\r\n\\# <bantime> unix timestamp of the ban time\r\n\\# <unbantime> unix timestamp of the unban time\r\n\\# Values: CMD\r\n\\# Default: iptables -D INPUT -s <ip> -j DROP\r\n\\#\r\nfwunban = iptables -D fail2ban-vsftpd -s <ip> -j DROP\r\n\r\n\\# Option: timeregex\r\n\\# Notes.: regex to match timestamp in VSFTPD logfile.\r\n\\# Values: \\[Mar 7 17:53:28\\]\r\n\\# Default: \\S\\{3\\}\\s\\{1,2\\}\\d\\{1,2\\} \\d\\{2\\}:\\d\\{2\\}:\\d\\{2\\}\r\n\\#\r\ntimeregex = \\S\\{3\\}\\s\\{1,2\\}\\d\\{1,2\\} \\d\\{2\\}:\\d\\{2\\}:\\d\\{2\\}\r\n\r\n\\# Option: timepattern\r\n\\# Notes.: format used in \"timeregex\" fields\r\ndefinition. Note that '%' must be\r\n\\# escaped with '%' \\(see\r\nhttp://rgruet.free.fr/PQR2.3.html\\#timeModule\\)\r\n\\# Values: TEXT Default: %%b %%d %%H:%%M:%%S\r\n\\#\r\ntimepattern = %%b %%d %%H:%%M:%%S\r\n\r\n\\# Option: failregex\r\n\\# Notes.: regex to match the password failures\r\nmessages in the logfile.\r\n\\# Values: TEXT Default: Authentication\r\nfailure|Failed password|Invalid user\r\n\\#\r\nfailregex = FAIL LOGIN\r\n",
"labels": [],
"assigned_to": "nobody",
"assigned_to_id": null,
"private": false,
"summary": "support for vsftpd",
"discussion_thread": {
"_id": "4f95a106",
"posts": [
{
"text": "Logged In: YES \nuser\\_id=933467\n\nThank you. Added to CVS. Will be in 0.6.1",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2006-02-11 15:30:46",
"slug": "32f7",
"subject": "#10 support for vsftpd"
},
{
"text": "- **status**: open --> closed-accepted",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2006-02-11 15:30:46",
"slug": "6a07",
"subject": "#10 support for vsftpd"
},
{
"text": "Logged In: YES \nuser\\_id=930060\n\nCan you please show us what settings you used for the \r\nvsftpd server?\r\n\r\nIn particular, can you display the settings you used \r\nfor /etc/vsftpd/vsftpd.conf that enabled vsftpd to generate \r\nlogin failure messages with the correct timestamps in a \r\nformat that could be recongnized by fail2ban?\r\n\r\nMuch tnx\\!\r\n\r\nHarry",
"attachments": [],
"author": "rarig",
"timestamp": "2006-02-15 13:51:56",
"slug": "eb7f",
"subject": "#10 support for vsftpd"
},
{
"text": "Logged In: YES \nuser\\_id=1442281\n\nmy vsftpd config is nothing special i think.\r\n\r\nmy sw versions:\r\n\r\nsys-apps/iproute2 2.6.11.20050310-r1\r\nnet-firewall/shorewall 2.4.2\r\nnet-analyzer/fail2ban 0.6.0\r\nsys-kernel/gentoo-sources 2.6.12-r6\r\nnet-ftp/vsftpd 2.0.3-r1\r\n\r\nwhen i try to login with ftp several times, my ip gets\r\nbanned. or am i wrong?\r\n\r\nhere is what fail2ban.log says:\r\n\r\n2006-02-15 14:54:21,801 INFO: VSFTPD: 89.53.40.xxx has 5\r\nlogin failure\\(s\\). Banned.\r\n2006-02-15 14:54:21,802 WARNING: VSFTPD: Ban 89.53.40.xxx\r\n\r\n\r\nhere is the output of 'cat /etc/vsftpd.conf | grep -v \"\\#\"':\r\n\r\nbackground=YES\r\nlisten=YES\r\nanonymous\\_enable=NO\r\nlocal\\_enable=YES\r\nwrite\\_enable=YES\r\nlocal\\_umask=022\r\ndirmessage\\_enable=YES\r\nconnect\\_from\\_port\\_20=YES\r\nxferlog\\_enable=YES\r\nxferlog\\_file=/var/log/vsftpd.log\r\nnopriv\\_user=nobody\r\nchroot\\_list\\_enable=YES\r\nchroot\\_list\\_file=/etc/vsftpd/chroot\\_list\r\nchroot\\_local\\_user=YES\r\n",
"attachments": [],
"author": "zugeschmiert",
"timestamp": "2006-02-15 14:31:21",
"slug": "3854",
"subject": "#10 support for vsftpd"
},
{
"text": "- **status**: closed-accepted --> open-accepted",
"attachments": [],
"author": "zugeschmiert",
"timestamp": "2006-02-15 14:31:21",
"slug": "6a94",
"subject": "#10 support for vsftpd"
},
{
"text": "Logged In: YES \nuser\\_id=933467\n\nLocal time problem seems to be related to chroot. A\r\n\"etc/localtime\" file needs to be present in the chrooted\r\nenvironnement. Please look at:\r\n\r\nhttp://groups.google.com/group/novell.support.suse.linux.enterprise-server/browse\\_thread/thread/17d3ff88e32465fd/74b6b7ab9612f231?lnk=st&q=vsftpd+localtime&rnum=1&hl=en\\#74b6b7ab9612f231",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2006-02-15 14:59:27",
"slug": "672b",
"subject": "#10 support for vsftpd"
},
{
"text": "Logged In: YES \nuser\\_id=930060\n\nMuch tnx for the configuration file info\\!\r\n\r\nThis helped identify the culprit: The following \r\nconfiguration option:\r\n\r\nlog\\_ftp\\_protocol=YES\r\n\r\nappears to cause some FTP Protocol commands to be logged in \r\nGMT instead of local time, which is inconsistent with all \r\nthe other vsftpd logging that takes place. This behavior \r\ncauses fail2ban to miss the authentication failures, \r\nbecause it is using the wrong timestamps. After dropping \r\nthis option, fail2ban started working on my server as \r\nadvertised\\!\r\n\r\n\\(The only downside is that my log files are missing the FTP \r\nfile xfer info I wanted to log. I filed a bug report on \r\nhttp://freshmeat.net/projects/vsftpd/, hopefully this \r\nproblem will be addressed by the vsftpd developers\\)\r\n",
"attachments": [],
"author": "rarig",
"timestamp": "2006-02-16 11:50:01",
"slug": "3904",
"subject": "#10 support for vsftpd"
},
{
"text": "- **status**: open-accepted --> closed-accepted",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2006-02-16 13:16:16",
"slug": "6158",
"subject": "#10 support for vsftpd"
}
],
"discussion_id": "51acf2192718464f1a12f6bd",
"subject": ""
},
"mod_date": "2006-02-16 13:16:16",
"votes_down": 0,
"votes_up": 0,
"_id": "51acf2322718464f1a12f7e1",
"discussion_thread_url": "http://sourceforge.net/rest/p/fail2ban/bugs/_discuss/thread/4f95a106/",
"ticket_num": 10,
"custom_fields": {
"_priority": "5"
},
"created_date": "2006-02-02 11:36:13"
},{
"status": "closed-accepted",
"reported_by_id": "501198b6fd48f81dfd00a6f7",
"related_artifacts": [],
"attachments": [],
"reported_by": "ticho",
"description": "fail2ban often crashes here, it has never survived a\r\nsingle whole ssh flood.\r\n\r\nThis is my system log output:\r\n\r\nFeb 19 01:23:48 src@thelair sshd\\(pam\\_unix\\)\\[20961\\]:\r\ncheck pass; user unknown\r\nFeb 19 01:23:48 src@thelair sshd\\(pam\\_unix\\)\\[20961\\]:\r\nauthentication failure; logname= uid=0 euid=0 tty=ssh\r\nruser= rhost=195.26.34.19 \r\nFeb 19 01:23:50 src@thelair sshd\\[20961\\]: Failed\r\npassword for invalid user trevor from 195.26.34.19 port\r\n35783 ssh2\r\nFeb 19 01:23:52 src@thelair sshd\\[21244\\]: Invalid user\r\njade from 195.26.34.19\r\nFeb 19 01:23:52 src@thelair sshd\\(pam\\_unix\\)\\[21244\\]:\r\ncheck pass; user unknown\r\nFeb 19 01:23:52 src@thelair sshd\\(pam\\_unix\\)\\[21244\\]:\r\nauthentication failure; logname= uid=0 euid=0 tty=ssh\r\nruser= rhost=195.26.34.19 \r\nFeb 19 01:23:54 src@thelair sshd\\[21244\\]: Failed\r\npassword for invalid user jade from 195.26.34.19 port\r\n35793 ssh2\r\nFeb 19 01:25:55 src@thelair fail2ban\\[11740\\]: ERROR:\r\nFail2Ban got an unhandled exception and died.\r\nFeb 19 01:25:55 src@thelair fail2ban\\[11740\\]: ERROR:\r\nType: 'ValueError' Value: \\('invalid literal for long\\(\\):\r\n24,',\\) TB: \\[\\('/usr/bin/fail2ban', 46, '?',\r\n'fail2ban.main\\(\\)'\\), \\('/usr/lib/fail2ban/fail2ban.py',\r\n453, 'main', 'e = element\\[1\\].getFailures\\(\\)'\\),\r\n\\('/usr/lib/fail2ban/logreader/logreader.py', 148,\r\n'getFailures', 'if self.inIgnoreIPList\\(ip\\):'\\),\r\n\\('/usr/lib/fail2ban/logreader/logreader.py', 78,\r\n'inIgnoreIPList', 's\\[1\\] = long\\(s\\[1\\]\\)'\\)\\]\r\nFeb 19 01:25:55 src@thelair fail2ban\\[11740\\]: WARNING:\r\nRestoring firewall rules...",
"labels": [],
"assigned_to": "lostcontrol",
"assigned_to_id": "4e8a1d76b9363c20cf000dcf",
"private": false,
"summary": "fail2ban 0.6.0 dies: invalid literal for long()",
"discussion_thread": {
"_id": "cc2be5cb",
"posts": [
{
"text": "Logged In: YES \nuser\\_id=933467\n\nHi,\r\n\r\nCould you check that the \"ignoreip\" option in\r\n/etc/fail2ban.conf is valid?\r\n\r\nMaybe try with:\r\nignoreip = \r\n\r\nThank you",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2006-02-21 12:53:55",
"slug": "bad9",
"subject": "#11 fail2ban 0.6.0 dies: invalid literal for long()"
},
{
"text": "- **status**: open --> open-accepted",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2006-02-21 12:53:55",
"slug": "2cb6",
"subject": "#11 fail2ban 0.6.0 dies: invalid literal for long()"
},
{
"text": "Logged In: YES \nuser\\_id=861633\n\nI'm using following:\r\n\r\nignoreip = 192.168.??.0/24, 192.168.??.0/24\r\n\r\nThose are two private LANs the box is connected to.\r\n\r\nI tried running fail2ban with \"ignoreip = \" instead, I'll\r\nreport back after next ssh attack flood.",
"attachments": [],
"author": "ticho",
"timestamp": "2006-02-22 09:39:56",
"slug": "4433",
"subject": "#11 fail2ban 0.6.0 dies: invalid literal for long()"
},
{
"text": "Logged In: YES \nuser\\_id=933467\n\nHi,\r\n\r\nCould you remove the ',' in \"ignoreip\"?\r\n\r\nignoreip = 192.168.??.0/24 192.168.??.0/24\r\n\r\nIt should fix the issue ;\\)",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2006-02-22 10:11:12",
"slug": "162b",
"subject": "#11 fail2ban 0.6.0 dies: invalid literal for long()"
},
{
"text": "Logged In: NO \n\nYes, that works\\! Thanks and sorry for bothering. :\\) Keep up\r\nthe good work\\!",
"attachments": [],
"author": "nobody",
"timestamp": "2006-02-23 18:18:50",
"slug": "8ffc",
"subject": "#11 fail2ban 0.6.0 dies: invalid literal for long()"
},
{
"text": "Logged In: YES \nuser\\_id=861633\n\n...forgot to log in again",
"attachments": [],
"author": "ticho",
"timestamp": "2006-02-23 18:20:00",
"slug": "732e",
"subject": "#11 fail2ban 0.6.0 dies: invalid literal for long()"
},
{
"text": "Logged In: NO \n\ni dont know if here is the right place to ask for\r\nbut fail2ban doesn't work for me in fedora\r\ni had always:\r\nERROR: Unable to get stat on /var/log/secure\r\nin /var/log/fail2ban.log\r\n\r\nplease help me",
"attachments": [],
"author": "nobody",
"timestamp": "2006-02-28 00:36:35",
"slug": "9c30",
"subject": "#11 fail2ban 0.6.0 dies: invalid literal for long()"
},
{
"text": "- **status**: open-accepted --> closed-accepted",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2006-03-16 18:54:35",
"slug": "fc7a",
"subject": "#11 fail2ban 0.6.0 dies: invalid literal for long()"
}
],
"discussion_id": "51acf2192718464f1a12f6bd",
"subject": ""
},
"mod_date": "2006-03-16 18:54:35",
"votes_down": 0,
"votes_up": 0,
"_id": "51acf2362718464f1a12f833",
"discussion_thread_url": "http://sourceforge.net/rest/p/fail2ban/bugs/_discuss/thread/cc2be5cb/",
"ticket_num": 11,
"custom_fields": {
"_priority": "5"
},
"created_date": "2006-02-19 00:52:02"
},{
"status": "closed-fixed",
"reported_by_id": null,
"related_artifacts": [],
"attachments": [],
"reported_by": "*anonymous",
"description": "when i start fail2ban it gives me error-messages\r\ncomplaining \r\n\"2006-03-24 10:54:51,022 ERROR: time data did not match\r\nformat: data=Mar 21 10:00:50 fmt=%b %d %H:%M:%S\r\n2006-03-24 10:54:51,024 ERROR: Please check the format\r\nand your locale settings.\"\r\neven though that this scheme applies to my system:\r\n\r\n/var/log/messages:\r\n\"Mar 24 10:10:42 localhost sshd\\[10775\\]: Connection\r\nclosed by ::ffff:XX.X.X.XXX\"\r\n\r\ntimeregex and timepattern are default:\r\n\r\n\"timeregex = \\S\\{3\\}\\s\\{1,2\\}\\d\\{1,2\\} \\d\\{2\\}:\\d\\{2\\}:\\d\\{2\\}\"\r\n\"timepattern = %%b %%d %%H:%%M:%%S\"\r\n\r\ndistribution is suse 9.2, fail2ban was compiled with\r\npython 2.3+",
"labels": [],
"assigned_to": "lostcontrol",
"assigned_to_id": "4e8a1d76b9363c20cf000dcf",
"private": false,
"summary": "v0.6.1 trouble with locale-setting",
"discussion_thread": {
"_id": "d985785f",
"posts": [
{
"text": "Logged In: YES \nuser\\_id=933467\n\nCould you post the output of the \"locale\" command?\r\n\r\nThank you",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2006-03-25 18:12:40",
"slug": "74ce",
"subject": "#12 v0.6.1 trouble with locale-setting"
},
{
"text": "- **assigned_to**: nobody --> lostcontrol",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2006-03-25 18:12:40",
"slug": "1154",
"subject": "#12 v0.6.1 trouble with locale-setting"
},
{
"text": "Logged In: NO \n\nLANG=de\\_DE.UTF-8\r\nLC\\_CTYPE=\"de\\_DE.UTF-8\"\r\nLC\\_NUMERIC=\"de\\_DE.UTF-8\"\r\nLC\\_TIME=\"de\\_DE.UTF-8\"\r\nLC\\_COLLATE=\"de\\_DE.UTF-8\"\r\nLC\\_MONETARY=\"de\\_DE.UTF-8\"\r\nLC\\_MESSAGES=\"de\\_DE.UTF-8\"\r\nLC\\_PAPER=\"de\\_DE.UTF-8\"\r\nLC\\_NAME=\"de\\_DE.UTF-8\"\r\nLC\\_ADDRESS=\"de\\_DE.UTF-8\"\r\nLC\\_TELEPHONE=\"de\\_DE.UTF-8\"\r\nLC\\_MEASUREMENT=\"de\\_DE.UTF-8\"\r\nLC\\_IDENTIFICATION=\"de\\_DE.UTF-8\"\r\nLC\\_ALL=\r\n\r\n\\--this is the output from sue10 on which i encountered the\r\nsame problems - UTF8, german",
"attachments": [],
"author": "nobody",
"timestamp": "2006-03-26 10:22:03",
"slug": "55ec",
"subject": "#12 v0.6.1 trouble with locale-setting"
},
{
"text": "Logged In: NO \n\nLANG=de\\_DE.UTF-8\r\nLC\\_CTYPE=\"de\\_DE.UTF-8\"\r\nLC\\_NUMERIC=\"de\\_DE.UTF-8\"\r\nLC\\_TIME=\"de\\_DE.UTF-8\"\r\nLC\\_COLLATE=\"de\\_DE.UTF-8\"\r\nLC\\_MONETARY=\"de\\_DE.UTF-8\"\r\nLC\\_MESSAGES=\"de\\_DE.UTF-8\"\r\nLC\\_PAPER=\"de\\_DE.UTF-8\"\r\nLC\\_NAME=\"de\\_DE.UTF-8\"\r\nLC\\_ADDRESS=\"de\\_DE.UTF-8\"\r\nLC\\_TELEPHONE=\"de\\_DE.UTF-8\"\r\nLC\\_MEASUREMENT=\"de\\_DE.UTF-8\"\r\nLC\\_IDENTIFICATION=\"de\\_DE.UTF-8\"\r\nLC\\_ALL=\r\n\r\n\\--this is the output from sue10 on which i encountered the\r\nsame problems - UTF8, german",
"attachments": [],
"author": "nobody",
"timestamp": "2006-03-26 10:23:20",
"slug": "be35",
"subject": "#12 v0.6.1 trouble with locale-setting"
},
{
"text": "Logged In: NO \n\nSame error here with German Debian \\(Sid\\)\r\n\r\n\\[~ \\#\\] locale\r\nLANG=de\\_DE.UTF-8\r\nLC\\_CTYPE=\"de\\_DE.UTF-8\"\r\nLC\\_NUMERIC=\"de\\_DE.UTF-8\"\r\nLC\\_TIME=\"de\\_DE.UTF-8\"\r\nLC\\_COLLATE=\"de\\_DE.UTF-8\"\r\nLC\\_MONETARY=\"de\\_DE.UTF-8\"\r\nLC\\_MESSAGES=\"de\\_DE.UTF-8\"\r\nLC\\_PAPER=\"de\\_DE.UTF-8\"\r\nLC\\_NAME=\"de\\_DE.UTF-8\"\r\nLC\\_ADDRESS=\"de\\_DE.UTF-8\"\r\nLC\\_TELEPHONE=\"de\\_DE.UTF-8\"\r\nLC\\_MEASUREMENT=\"de\\_DE.UTF-8\"\r\nLC\\_IDENTIFICATION=\"de\\_DE.UTF-8\"\r\nLC\\_ALL=\r\n",
"attachments": [],
"author": "nobody",
"timestamp": "2006-03-30 12:31:53",
"slug": "3e84",
"subject": "#12 v0.6.1 trouble with locale-setting"
},
{
"text": "Logged In: NO \n\nSame here :\r\n\r\n2006-04-03 19:49:17,307 ERROR: Please check the format and \r\nyour locale settings.\r\n2006-04-03 19:49:17,308 ERROR: time data did not match \r\nformat: data=Apr 3 19:49:01 fmt=%b %d %H:%M:%S\r\n\r\nLANG=fr\\_FR.UTF-8\r\nLC\\_CTYPE=fr\\_FR.UTF-8\r\nLC\\_NUMERIC=fr\\_FR.UTF-8\r\nLC\\_TIME=fr\\_FR.UTF-8\r\nLC\\_COLLATE=fr\\_FR.UTF-8\r\nLC\\_MONETARY=fr\\_FR.UTF-8\r\nLC\\_MESSAGES=fr\\_FR.UTF-8\r\nLC\\_PAPER=fr\\_FR.UTF-8\r\nLC\\_NAME=fr\\_FR.UTF-8\r\nLC\\_ADDRESS=fr\\_FR.UTF-8\r\nLC\\_TELEPHONE=fr\\_FR.UTF-8\r\nLC\\_MEASUREMENT=fr\\_FR.UTF-8\r\nLC\\_IDENTIFICATION=fr\\_FR.UTF-8\r\nLC\\_ALL=\r\n\r\nPython 2.4.1",
"attachments": [],
"author": "nobody",
"timestamp": "2006-04-03 18:21:48",
"slug": "6925",
"subject": "#12 v0.6.1 trouble with locale-setting"
},
{
"text": "Logged In: YES \nuser\\_id=675287\n\nSame for me. But there's one thing that come to my mind.\r\nDuring March the abbreviation of that month was 'Mar' either\r\nin French or in English. Now we're in April and the french\r\nabbrev is not Apr but Avr. My syslog-ng writes lines like\r\nthis ones in /var/log/messages:\r\nApr 12 16:45:32 marge sshd\\[20849\\]: Accepted publickey for\r\nroot from 192.168.0.2 port 2265 ssh2\r\n\r\nAs you can see this is the English abbrev even if all my\r\nlocales are in french:\r\n\r\n\r\nmarge log \\# locale\r\nLANG=fr\\_FR@euro\r\nLC\\_CTYPE=\"fr\\_FR@euro\"\r\nLC\\_NUMERIC=\"fr\\_FR@euro\"\r\nLC\\_TIME=\"fr\\_FR@euro\"\r\nLC\\_COLLATE=\"fr\\_FR@euro\"\r\nLC\\_MONETARY=\"fr\\_FR@euro\"\r\nLC\\_MESSAGES=\"fr\\_FR@euro\"\r\nLC\\_PAPER=\"fr\\_FR@euro\"\r\nLC\\_NAME=\"fr\\_FR@euro\"\r\nLC\\_ADDRESS=\"fr\\_FR@euro\"\r\nLC\\_TELEPHONE=\"fr\\_FR@euro\"\r\nLC\\_MEASUREMENT=\"fr\\_FR@euro\"\r\nLC\\_IDENTIFICATION=\"fr\\_FR@euro\"\r\nLC\\_ALL=fr\\_FR@euro\r\n\r\nAs is is written in the fail2ban.conf file, the %b refers to\r\nthe locale's abbreviated month name \\(as described in\r\nhttp://rgruet.free.fr/PQR2.3.html\\#timeModule\\). Unfortunately\r\nit seems that syslog-ng writes the month in English\r\nwhatever the locales are.\r\n\r\nHth.\r\nChristophe Garault",
"attachments": [],
"author": "letoff",
"timestamp": "2006-04-12 14:54:24",
"slug": "de66",
"subject": "#12 v0.6.1 trouble with locale-setting"
},
{
"text": "Logged In: YES \nuser\\_id=675287\n\nIt looks like using tai64n format solved the problem.",
"attachments": [],
"author": "letoff",
"timestamp": "2006-04-16 17:31:29",
"slug": "aa21",
"subject": "#12 v0.6.1 trouble with locale-setting"
},
{
"text": "Logged In: NO \n\nThe same at FC3, Polish locale set.\r\n\\[root@link ~\\]\\# locale\r\nLANG=pl\\_PL\r\nLC\\_CTYPE=\"pl\\_PL\"\r\nLC\\_NUMERIC=\"pl\\_PL\"\r\nLC\\_TIME=\"pl\\_PL\"\r\nLC\\_COLLATE=\"pl\\_PL\"\r\nLC\\_MONETARY=\"pl\\_PL\"\r\nLC\\_MESSAGES=\"pl\\_PL\"\r\nLC\\_PAPER=\"pl\\_PL\"\r\nLC\\_NAME=\"pl\\_PL\"\r\nLC\\_ADDRESS=\"pl\\_PL\"\r\nLC\\_TELEPHONE=\"pl\\_PL\"\r\nLC\\_MEASUREMENT=\"pl\\_PL\"\r\nLC\\_IDENTIFICATION=\"pl\\_PL\"\r\nLC\\_ALL=\r\n\\[root@link ~\\]\\#\r\n",
"attachments": [],
"author": "nobody",
"timestamp": "2006-04-22 11:00:35",
"slug": "00c3",
"subject": "#12 v0.6.1 trouble with locale-setting"
},
{
"text": "Logged In: NO \n\nI noticed this problem on Debian Linux since May 1. While\r\nlogged in as root via ssh, locale returns:\r\n\r\nLANG=de\\_DE@euro\r\nLC\\_CTYPE=\"de\\_DE@euro\"\r\nLC\\_NUMERIC=\"de\\_DE@euro\"\r\nLC\\_TIME=\"de\\_DE@euro\"\r\nLC\\_COLLATE=\"de\\_DE@euro\"\r\nLC\\_MONETARY=\"de\\_DE@euro\"\r\nLC\\_MESSAGES=\"de\\_DE@euro\"\r\nLC\\_PAPER=\"de\\_DE@euro\"\r\nLC\\_NAME=\"de\\_DE@euro\"\r\nLC\\_ADDRESS=\"de\\_DE@euro\"\r\nLC\\_TELEPHONE=\"de\\_DE@euro\"\r\nLC\\_MEASUREMENT=\"de\\_DE@euro\"\r\nLC\\_IDENTIFICATION=\"de\\_DE@euro\"\r\nLC\\_ALL=\r\n\r\nAfter restarting fail2ban with\r\n\r\nLANG= /etc/init.d/fail2ban restart\r\n\r\nthe error message was gone. So probably the trouble was\r\ntriggered by manual \\(re\\)start of fail2ban.",
"attachments": [],
"author": "nobody",
"timestamp": "2006-05-02 08:09:42",
"slug": "743d",
"subject": "#12 v0.6.1 trouble with locale-setting"
},
{
"text": "Logged In: YES \nuser\\_id=933467\n\nThis is not fixed in Subversion repository yet.\r\n\r\nFor those who have this one, please try:\r\n\r\nLANG=en\\_US /etc/init.d/fail2ban restart",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2006-08-22 06:28:41",
"slug": "6849",
"subject": "#12 v0.6.1 trouble with locale-setting"
},
{
"text": "- **status**: open --> open-accepted",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2006-08-22 06:28:41",
"slug": "bb9e",
"subject": "#12 v0.6.1 trouble with locale-setting"
},
{
"text": "Logged In: NO \n\nSame for norwegian no\\_NO settings.\r\n\r\nLANG=no\\_NO.UTF-8\r\nLC\\_CTYPE=\"no\\_NO.UTF-8\"\r\nLC\\_NUMERIC=\"no\\_NO.UTF-8\"\r\nLC\\_TIME=\"no\\_NO.UTF-8\"\r\nLC\\_COLLATE=\"no\\_NO.UTF-8\"\r\nLC\\_MONETARY=\"no\\_NO.UTF-8\"\r\nLC\\_MESSAGES=\"no\\_NO.UTF-8\"\r\nLC\\_PAPER=\"no\\_NO.UTF-8\"\r\nLC\\_NAME=\"no\\_NO.UTF-8\"\r\nLC\\_ADDRESS=\"no\\_NO.UTF-8\"\r\nLC\\_TELEPHONE=\"no\\_NO.UTF-8\"\r\nLC\\_MEASUREMENT=\"no\\_NO.UTF-8\"\r\nLC\\_IDENTIFICATION=\"no\\_NO.UTF-8\"\r\nLC\\_ALL=\r\n\r\n\"LANG= /etc/init.d/fail2ban restart\" works though.\r\n\r\nYou can also edit the script /etc/init.d/fail2ban and add \r\nLANG= after SCRIPTNAME= so it looks like this:\r\n\\----\r\nPATH=/usr/sbin:/usr/bin:/sbin:/bin\r\nDESC=\"authentication failure monitor\"\r\nNAME=fail2ban\r\nDAEMON=/usr/bin/$NAME\r\nPIDFILE=/var/run/$NAME.pid\r\nSCRIPTNAME=/etc/init.d/$NAME\r\nLANG=\r\n\r\n\\# Exit if the package is not installed\r\n\\-----\r\n\r\nI found that editing the startup script was the best, \r\nbecause then I don't have to manually restart it after \r\nrebooting.\r\n\r\nIt will only occur in months that are spellt different \r\nfrom english, and that will only be a few months when \r\nusing three letters for months.",
"attachments": [],
"author": "nobody",
"timestamp": "2006-10-23 00:34:56",
"slug": "2541",
"subject": "#12 v0.6.1 trouble with locale-setting"
},
{
"text": "Logged In: YES \nuser\\_id=487166\n\nI can not correct this problem. My locale is as follows:\r\n\r\nLANG=tr\\_TR.UTF-8\r\nLC\\_CTYPE=tr\\_TR.UTF-8\r\nLC\\_NUMERIC=en\\_US.UTF-8\r\nLC\\_TIME=tr\\_TR.UTF-8\r\nLC\\_COLLATE=tr\\_TR.UTF-8\r\nLC\\_MONETARY=en\\_US.UTF-8\r\nLC\\_MESSAGES=tr\\_TR.UTF-8\r\nLC\\_PAPER=en\\_US.UTF-8\r\nLC\\_NAME=en\\_US.UTF-8\r\nLC\\_ADDRESS=en\\_US.UTF-8\r\nLC\\_TELEPHONE=en\\_US.UTF-8\r\nLC\\_MEASUREMENT=en\\_US.UTF-8\r\nLC\\_IDENTIFICATION=en\\_US.UTF-8\r\nLC\\_ALL=\r\n\r\nNeither \"LANG=en\\_US /etc/init.d/fail2ban restart\" nor\r\nmodifying the /etc/init.d/fail2ban script coorects the\r\nproblem. I even tried \"LANG=en\\_US.UTF-8\r\n/etc/init.d/fail2ban restart\", it did not work either.\r\n\r\nAny input is welcome\\!\r\n\r\nhakova",
"attachments": [],
"author": "hakova",
"timestamp": "2006-11-05 05:13:34",
"slug": "c313",
"subject": "#12 v0.6.1 trouble with locale-setting"
},
{
"text": "Logged In: NO \n\nSame for french fr\\_FR settings.\r\n\r\n...\r\n\r\nBut I opened /usr/bin/fail2ban and there was these lines :\r\n\\# Set the locale with the user's default setting\r\ntry:\r\nlocale.setlocale\\(locale.LC\\_ALL, ''\\)\r\nexcept Exception:\r\nprint \"Unable to set locale to \" + \\`locale.getdefaultlocale\\(\\)\\`\r\nsys.exit\\(-1\\)\r\n\r\nI cut off these line ...\r\nI launch /etc/init.d/fail2ban restart\r\n\r\nAnd no : Please check the format and your locale settings.\r\n\r\nThis is an idea ?",
"attachments": [],
"author": "nobody",
"timestamp": "2006-12-06 19:58:03",
"slug": "c918",
"subject": "#12 v0.6.1 trouble with locale-setting"
},
{
"text": "Logged In: YES \nuser\\_id=933467\nOriginator: NO\n\nCould you post the output of \"locale\"? Are the date in your log files displayed using fr\\_FR or any other locale? Is there a mix of several locales in your log files?\r\n\r\nThank you",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2006-12-06 23:05:31",
"slug": "15e3",
"subject": "#12 v0.6.1 trouble with locale-setting"
},
{
"text": "Logged In: NO \n\nSame for finish fi\\_FI settings\r\n\r\nLANG=fi\\_FI.UTF-8\r\nLC\\_CTYPE=\"fi\\_FI.UTF-8\"\r\nLC\\_NUMERIC=\"fi\\_FI.UTF-8\"\r\nLC\\_TIME=\"fi\\_FI.UTF-8\"\r\nLC\\_COLLATE=\"fi\\_FI.UTF-8\"\r\nLC\\_MONETARY=\"fi\\_FI.UTF-8\"\r\nLC\\_MESSAGES=\"fi\\_FI.UTF-8\"\r\nLC\\_PAPER=\"fi\\_FI.UTF-8\"\r\nLC\\_NAME=\"fi\\_FI.UTF-8\"\r\nLC\\_ADDRESS=\"fi\\_FI.UTF-8\"\r\nLC\\_TELEPHONE=\"fi\\_FI.UTF-8\"\r\nLC\\_MEASUREMENT=\"fi\\_FI.UTF-8\"\r\nLC\\_IDENTIFICATION=\"fi\\_FI.UTF-8\"\r\nLC\\_ALL=\r\n",
"attachments": [],
"author": "nobody",
"timestamp": "2007-01-31 03:40:44",
"slug": "fc20",
"subject": "#12 v0.6.1 trouble with locale-setting"
},
{
"text": "Logged In: YES \nuser\\_id=933467\nOriginator: NO\n\nPlease try 0.6.2 and set the value of \"locale\" in fail2ban.conf to \"C\", \"en\\_US\" or \"POSIX\". You can use \"locale -a\" to see which locales are available on your system.\r\n\r\n\\# Option: locale\r\n\\# Notes.: global \\(cannot be redefined per section\\) locale to use for\r\n\\# timestamp pattern matching by changing LC\\_TIME for\r\n\\# fail2ban process. Empty entry sets locale to default one\r\n\\# \\(usually specified by LC\\_ALL environment variable\\).\r\n\\# Values: LOCALE Default:\r\n\\#\r\nlocale =\r\n\r\nThank you",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2007-02-04 23:02:53",
"slug": "d5d0",
"subject": "#12 v0.6.1 trouble with locale-setting"
},
{
"text": "Logged In: YES \nuser\\_id=933467\nOriginator: NO\n\nI close this bug as this should be fixed in 0.6.2. If not, please reopen.",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2007-02-16 08:11:56",
"slug": "1383",
"subject": "#12 v0.6.1 trouble with locale-setting"
},
{
"text": "- **status**: open-accepted --> closed-fixed",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2007-02-16 08:11:56",
"slug": "7887",
"subject": "#12 v0.6.1 trouble with locale-setting"
},
{
"text": "problem with proftpd.conf and Russian locale\n\nparse problem\nFound a match for ' my\\_host proftpd\\[5391\\] 127.0.0.1 \\(111.222.333.444\\[111.222.333.444\\]\\): SECURITY VIOLATION: root login attempted.\n' but no valid date/time found for '\u041e\u043a\u0442 03 14:13:08'. Please contact the author in order to get support for this format\nFound a match for ' my\\_host proftpd\\[5392\\] 127.0.0.1 \\(111.222.333.444\\[111.222.333.444\\]\\): SECURITY VIOLATION: root login attempted.\n' but no valid date/time found for '\u041e\u043a\u0442 03 14:13:09'. Please contact the author in order to get support for this format\nFound a match for ' my\\_host proftpd\\[5393\\] 127.0.0.1 \\(111.222.333.444\\[111.222.333.444\\]\\): SECURITY VIOLATION: root login attempted.\n' but no valid date/time found for '\u041e\u043a\u0442 03 14:13:35'. Please contact the author in order to get support for this format\n\n\nOriginal log file:\n\u041e\u043a\u0442 03 14:13:08 my\\_host proftpd\\[5391\\] 127.0.0.1 \\(111.222.333.444\\[111.222.333.444\\]\\): SECURITY VIOLATION: root login attempted.\n\u041e\u043a\u0442 03 14:13:09 my\\_host proftpd\\[5392\\] 127.0.0.1 \\(111.222.333.444\\[111.222.333.444\\]\\): SECURITY VIOLATION: root login attempted.\n\u041e\u043a\u0442 03 14:13:35 my\\_host proftpd\\[5393\\] 127.0.0.1 \\(111.222.333.444\\[111.222.333.444\\]\\): SECURITY VIOLATION: root login attempted.\n\n\n\n",
"attachments": [],
"author": "linvinus",
"timestamp": "2011-10-03 17:04:10",
"slug": "ae5c",
"subject": "#12 v0.6.1 trouble with locale-setting"
}
],
"discussion_id": "51acf2192718464f1a12f6bd",
"subject": ""
},
"mod_date": "2007-02-16 08:11:56",
"votes_down": 0,
"votes_up": 0,
"_id": "51acf2392718464f1a12f865",
"discussion_thread_url": "http://sourceforge.net/rest/p/fail2ban/bugs/_discuss/thread/d985785f/",
"ticket_num": 12,
"custom_fields": {
"_priority": "5"
},
"created_date": "2006-03-24 10:05:48"
},{
"status": "open",
"reported_by_id": "516c4f0c34309d2f53b02cf6",
"related_artifacts": [],
"attachments": [],
"reported_by": "jasonaward",
"description": "I'm currently running fail2ban-0.7.2 with 5 jails and\r\nit's taking roughly 20MB / jail \\(for a total of almost\r\nexactly 100MB\\). Maybe I'm wrong, but this seems like a\r\nlot. Any thoughts on what may cause it?\r\n\r\nI can help debug in any way if needed. Thanks.",
"labels": [],
"assigned_to": "lostcontrol",
"assigned_to_id": "4e8a1d76b9363c20cf000dcf",
"private": false,
"summary": "Excessive memory usage?",
"discussion_thread": {
"_id": "7d1728c7",
"posts": [
{
"text": "Logged In: YES \nuser\\_id=933467\n\nHi,\r\n\r\nThat's a lot indeed. I look at /proc/\\*/status and in fact,\r\nthe memory usage reported is quite huge :-/\r\n\r\n1/ fail2ban-server -f: 14360 kB\r\n2/ fail2ban-client status: 22556 kB\r\n3/ fail2ban-client reload: 47240 kB \\(1 jail\\)\r\n4/ test-server: 121136 kB \\(send random command, created 6 jails\\)\r\n\r\nI must look into this issue. Thanks a lot for reporting it.\r\n",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2006-09-21 21:55:02",
"slug": "5fb0",
"subject": "#13 Excessive memory usage?"
},
{
"text": "- **assigned_to**: nobody --> lostcontrol",
"attachments": [],
"author": "lostcontrol",
"timestamp": "2006-09-21 21:55:02",
"slug": "870d",