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