From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id K3WTF/fIumDFBAAAgWs5BA (envelope-from ) for ; Sat, 05 Jun 2021 02:44:39 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id sNuxEvfIumAMBgAAB5/wlQ (envelope-from ) for ; Sat, 05 Jun 2021 00:44:39 +0000 Received: from mail.notmuchmail.org (nmbug.tethera.net [144.217.243.247]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id B1F7F1FD10 for ; Sat, 5 Jun 2021 02:44:38 +0200 (CEST) Received: from nmbug.tethera.net (localhost [127.0.0.1]) by mail.notmuchmail.org (Postfix) with ESMTP id 1C17B2B24D; Fri, 4 Jun 2021 20:44:33 -0400 (EDT) Received: from mail-wr1-x430.google.com (mail-wr1-x430.google.com [IPv6:2a00:1450:4864:20::430]) by mail.notmuchmail.org (Postfix) with ESMTPS id 8B51D2B23E for ; Fri, 4 Jun 2021 20:44:31 -0400 (EDT) Received: by mail-wr1-x430.google.com with SMTP id h8so10882417wrz.8 for ; Fri, 04 Jun 2021 17:44:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=PiRsB8pqfayPH/UHyehzvroBmfIvsxg71mIDJAqgbbU=; b=g7jN+d2MPZELvCBCPhvrPzIfcUGrPjdFK+d591pkifE4vnIQS8UMabX7e1sTD7ANeD bjMjkDqeRcTHb818UylVGYaeh1WjWA5PeBFLVt0iYes7TIpBjUPki4Ee5AMSJz8el4aD BaMQ1DjXFIAnjQCkdT6TmqHJfePkYgGcGjAksu7D7YMYCMwMiJk8l8w7XNv2k9L6ICw8 3dh8L5AB714IveL3wCO/CkRRoQ+Dss19DpupwnulvOU2VDeSCbUJ4OHMQik6nce5TOgT SO5AuxcPp3891JZsUQx8Xp+E0voOgKKr3TJOjQtJ8uYOeLB8psE5FSJcyLuFo5GfsbV7 k1cw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=PiRsB8pqfayPH/UHyehzvroBmfIvsxg71mIDJAqgbbU=; b=tSAnHAAsee9gWSwKIQxE1QVGW7uuffoDQ3Irj+F7kE+Cq+MI79yebwL5NEg3uObivb YXuWleTBZJAqqhTOscjkdRIpjGF1QUQFvywc6Fx/0CAZvI7i2gMh0hXfd2SKCEjb8dWt PbvZEIA+1m7aeWW3YzXHNWBkvkXAdC4aLcz/5QiRpt4kTy83SsXsIUI9pBIrnignVKjM iGEXwOpffjGfiHG0L3u7RBjCzWhlxYRhdxjJEzL89y6s7W4cWtdMkrb3vJ9awi0JfG21 20TszyzwBdSWitZImZlT7qpVsQqeymaivCZjtkE4jkQ+fZxKcCdgshSedEiGjH7YM1EX mdiQ== X-Gm-Message-State: AOAM530Yhn8sImJQXT69sv1trOmy80XUSaan1zNrRyE1kKU7fiYYn4oC FfZ9fSd3dTH5iok1VluuhA4VaRJYlp6Vc1VCUWICKx/tK2Duug== X-Google-Smtp-Source: ABdhPJwrSr2NTlN+/79wBcs+CdwN4Kagl1k6eP1c50WoXaS4E4GrayTdNa8WhL0fBD0X57Sb047VLonkfMDYtlj3bag= X-Received: by 2002:adf:f7d1:: with SMTP id a17mr6273275wrq.84.1622853870191; Fri, 04 Jun 2021 17:44:30 -0700 (PDT) MIME-Version: 1.0 From: Felipe Contreras Date: Fri, 4 Jun 2021 19:44:19 -0500 Message-ID: Subject: How to recover from this permanent fatal error? To: "notmuch@notmuchmail.org" Message-ID-Hash: PUCT4VH42DRMHBW2R2CMQDPNVJRBOYFN X-Message-ID-Hash: PUCT4VH42DRMHBW2R2CMQDPNVJRBOYFN X-MailFrom: felipe.contreras@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-notmuch.notmuchmail.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header X-Mailman-Version: 3.2.1 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Help: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1622853878; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=V/jtcXle1r/Z0URd1GpoNpB80LK9SsW1/U/cslAkvmE=; b=S5A3JScys2skdVwgB5St4MVgC5WcnJvTGxsHQaobJ2ww7OOpsJ+4s+ihmxki4imnA1FrGa trkdzhwIuqY+9MrB+NpbIcMSrvh9kJ3sAAV1RgiOtgJbAkcRh82EFZbFg3cYcJXl2d+cGH qJevc056FmmYyifPxnwStlju4PMhg0ln5gVawE3/SmCrr5h6QC6cdmz8UfEPpF8RMs2fpd OxhmCL3lWritUg+f0pL6OwQ5Cgxfil9oXGpre9XrRtuYu+H1Mhl1ElysozNwT8aJAlDHdJ tdaqOz+3Zup0i8BZnQFjCwNVRTSeveMJ/+xyNae8oyaRL93VNZFwJ+gcOgj2Lw== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1622853878; a=rsa-sha256; cv=none; b=Q/DYQQ7E3TYtYshHurhd2diV4LQXEIDZXDEQBy1r8pkS7dIz6zBZQte/Be7CI0/xYSz+m/ 8j3hVfar2BEt4ezvXXTWtVVEJZVFhPSITo5yFDCHHGQDjO9NG8BIGHGdhopt327D6jvzul e7M6ezBVYCEfAmPM4xIaG/XKXocbZ2K7WR1479/o2q1QMWunSJxZhqzy53bq2vYONr88Ec DB/HrtK9qf3dehqPP/K08Fc/UcZPNh+gfMV7Q8vV4T2YHwxz3fnUIRX/kbJUMWqwAZGwIG BhzOozbqvOSBNNMQRnP4q5Kwn2gUbxo2s6TgxQtoi/Z3ZkO/DfnnO5dkAM6oyQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("body hash did not verify") header.d=gmail.com header.s=20161025 header.b=g7jN+d2M; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=none); spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 144.217.243.247 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org X-Migadu-Spam-Score: 0.08 Authentication-Results: aspmx1.migadu.com; dkim=fail ("body hash did not verify") header.d=gmail.com header.s=20161025 header.b=g7jN+d2M; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=none); spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 144.217.243.247 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org X-Migadu-Queue-Id: B1F7F1FD10 X-Spam-Score: 0.08 X-Migadu-Scanner: scn0.migadu.com X-TUID: AChPZNgGtUiq Hello, I can't use notmuch anymore, I get this error: A Xapian exception occurred opening database: The revision being read has been discarded - you should call Xapian::Database::reopen() and retry the operation Context. In order to investigate a bug about mbsync I moved away the folder ~/mail/.notmuch. I have a timer that calls notmuch new after mbsync, so I paused that timer. Initially I used notmuch, only to see everything empty. Then I recalled what I did, removed all the files, and moved back the .nomuch directory. IIRC I was able to use notmuch without problems once, and then I got the issue. All I can find about the issue is that somebody reported the exact same message to the mailing list (id:87txmb4xyz.fsf@mcs.anl.gov), but did not receive any feedback. Ideas? -- Felipe Contreras