> On 22 Sep 2017, at 16:31, Stroller <strol...@stellar.eclipse.co.uk> wrote:
>
> The problem I have today is that fail2ban doesn't seem to be creating a
> dbfile - as per the subject line, `fail2ban-client get dbfile` shows
> "Database currently disabled", ...
>
> I get the same thing if I stop the jails manually using fail2ban-client and
> try to set the dbfile manually with it:
>
> $ sudo bash -c 'for foo in sshd-badusername sshd-wrongpassword ; do
> fail2ban-client stop $foo ; done'
> Jail stopped
> Jail stopped
> $ sudo fail2ban-client set dbfile /var/lib/fail2ban/fail2ban.
> sqlite3
> Database currently disabled
>
> $ sudo fail2ban-client set dbpurgeage 260000
> Database currently disabled
>
> $
An off-list reply from a fellow Gentoo user has found the problem. He reported
a problem with sqlite and getting fail2ban working after installing that
package.
Perhaps that was a previous version of fail2ban, because the current version
displays this message (which I overlooked) when installed:
"If you want to use fail2ban's persistent database, then reinstall"
"dev-lang/python with USE=sqlite"
After remerging dev-lang/python-3.4.5 with USE=sqlite (which pulls in
dev-db/sqlite), and restarting fail2ban, the dbfile is created.
I appreciate your help,
Stroller.
------------------------------------------------------------------------------
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
