From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id CFBBC1382C5 for ; Sun, 7 Feb 2021 02:03:50 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1D129E0874; Sun, 7 Feb 2021 02:03:45 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id B801FE0815 for ; Sun, 7 Feb 2021 02:03:44 +0000 (UTC) Message-ID: <5b67d37602eb7881f2f4c3f5ec689c022f5a3221.camel@gentoo.org> Subject: Re: [gentoo-user] fail2ban can't find sqlite? From: Michael Orlitzky To: gentoo-user@lists.gentoo.org Date: Sat, 06 Feb 2021 21:03:38 -0500 In-Reply-To: <77956fe4-829e-124e-7357-796716ebe0cd@newideatest.site> References: <77956fe4-829e-124e-7357-796716ebe0cd@newideatest.site> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Archives-Salt: 7cbc6462-2517-4958-8bf4-f989b37b3c98 X-Archives-Hash: fe51d93de7df6dce2cbafca3c85fca98 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.