>
>
> > I'm delighted to report that this patch has worked for me with Ubuntu
> 16.04
> > / fail2ban 0.9.3. Thanks and kudos!
>
> > On 24 July 2017 at 21:41, Jonathan Kamens <j...@kamens.us> wrote:
>
> > You should be able to make this change in Ubuntu 16.04 by applying this
> > patch to /usr/lib/python3/dist-packages/fail2ban/server/database.py and
> > then restarting fail2ban:
> >
> > --- database.py.orig 2017-07-24 16:38:31.910178301 -0400
> > +++ database.py 2017-07-24 16:40:04.754185435 -0400
> > @@ -183,6 +183,8 @@
> >
> > cur = self._db.cursor()
> > cur.execute("PRAGMA foreign_keys = ON;")
> > + cur.execute("PRAGMA synchronous = OFF")
> > + cur.execute("PRAGMA temp_store = MEMORY")
> >
> > try:
> > cur.execute("SELECT version FROM fail2banDb LIMIT
> 1")
>
> In Fedora 26, 0.9.7-2, it doesn't appear this patch has been applied.
/root/fail2ban-0.9.4/fail2ban/server/database.py
cur = self._db.cursor()
cur.execute("PRAGMA foreign_keys = ON;")
try:
rpm -q fail2ban
fail2ban-0.9.7-2.fc26.noarch
I manually patched the file and fail2ban started fine.
Just wondering what tools were you using, e.g., top, htop, to observe:
1) The sqlite DB is causing high disk writes - ~600kB/s to disk
with a 130k DB file.
2) The sqlite DB appears to be writing very small chunks of data
resulting in a high write amplification factor.
3) The sqlite DB appears to be forcing a sync to disk at a high rate.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Fail2ban-users mailing list
Fail2ban-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fail2ban-users
