You were right. With the debugging tips from Alex Mishustin I was able
to determine that I had rebuilt 3.9 while fail2ban was using 3.8. I did
what I SHOULD have done in the first place and did an emerge -DN
fail2ban. That caused portage to see that Python 3.8 needed to be
rebuilt, and it did so. Now fail2ban is able to access the sqlite database.
Thanks!
On 2/6/2021 7:03 PM, Michael Orlitzky wrote:
On Sat, 2021-02-06 at 18:46 -0700, Dan Egli wrote:
At first I thought it was complaining about it's own missing module. But
there's no use flag for sqlite in fail2ban. So then I looked at python
itself. Sure enough, the sqlite use flag was disabled. So I turned it
on and re-emerged python. I also fixed a couple flags on sqlite itself
and re-emerged it. STILL I get this error. How do I fix this?
Just a guess: did you rebuild EVERY version of python, or just one? It
could be that fail2ban is running under a version that you didn't re-
emerge.
