On Wed, 03 Dec 2014, László Böszörményi (GCS) wrote: > On Sat, Nov 29, 2014 at 4:36 PM, Yaroslav Halchenko <y...@debian.org> wrote: > > On Sat, 29 Nov 2014, László Böszörményi (GCS) wrote: > >> May you give me some details how it happened in Sid?
> > ok -- I will try to replicate again under sid (trickier since I have no sid > > on > > publicly bombarded servers) > You may also backport the recent, SQLite3 3.8.7.2-1 upload to your box. good idea... meanwhile #771549 confirmed issue on sid https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771341#20 > >> > unfortunately we haven't logged the sql queries so not sure on exact > >> > one, but I > >> > think it was this one, which if executed from the shell seems to not > >> > cause the > >> > segfault... > >> > n {1..100}; do sqlite3 -list fail2ban.sqlite3 'SELECT ip, timeofban, > >> > data FROM bans WHERE 1 AND jail="sshd" AND ip="111.74.239.35" ORDER BY > >> > ip, timeofban' >/dev/null && echo success; done > You may try the same loop with a Python script doing the same SQLite3 query. yet another good idea- - I will do when I hit it again (I have managed not to keep a copy of that DB as of during segfault :-/) > > FWIW -- I am the Fail2ban maintainer... but fail2ban is just a 'trigger' > > here -- it is a purely Python implementation so either it is sqlite3 or > > python > > bindings which are at fault here > Then I do wonder why do you use an unofficial fail2ban backport > instead of doing it yourself. doing what myself? backport? this my backport ;) -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Research Scientist, 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-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
