From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <felix.lechner@lease-up.com>
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN: AS396097 208.82.96.0/21
X-Spam-Status: No, score=-2.6 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS,
	T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no
	version=3.4.6
Received: from sail-ipv4.us-core.com (sail-ipv4.us-core.com [208.82.101.137])
	(using TLSv1.3 with cipher TLS_CHACHA20_POLY1305_SHA256 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512)
	(No client certificate requested)
	by dcvr.yhbt.net (Postfix) with ESMTPS id A352D1F518
	for <meta@public-inbox.org>; Tue, 28 May 2024 02:43:23 +0000 (UTC)
Authentication-Results: dcvr.yhbt.net;
	dkim=pass (1024-bit key; secure) header.d=lease-up.com header.i=@lease-up.com header.a=rsa-sha256 header.s=2017 header.b=cstNulVb;
	dkim-atps=neutral
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; s=2017; bh=UDvH3Er3L1EUY/i
	InpR5uhlgbEHHXj+7lG9swVSpZTI=; h=date:references:in-reply-to:subject:
	cc:to:from; d=lease-up.com; b=cstNulVbZDwM122Sao1+8FRvXoaQqLFcs/i6Xx3i
	D4FVyia5LImy7BRf/QuZ/uKJvTgZLoQu0qna6pCJljE1F+D6eNt+4mhj4fij/zFP5aqmhh
	nacLxN+jQNkGarGaQwLOYOE/x12UOGWPNTsP76vjngso+pco5JV4qVCifVMf8=
Received: 
	by sail-ipv4.us-core.com (OpenSMTPD) with ESMTPSA id bd01e7cb (TLSv1.3:TLS_CHACHA20_POLY1305_SHA256:256:NO);
	Tue, 28 May 2024 02:43:17 +0000 (UTC)
From: Felix Lechner <felix.lechner@lease-up.com>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: Issuing rollback() due to DESTROY
In-Reply-To: <20240527225154.M531684@dcvr>
References: <87sey2q4b3.fsf@lease-up.com> <20240527225154.M531684@dcvr>
Date: Mon, 27 May 2024 19:43:16 -0700
Message-ID: <87plt6psfv.fsf@lease-up.com>
MIME-Version: 1.0
Content-Type: text/plain
List-Id: <meta.public-inbox.org>

Hi Eric,

On Mon, May 27 2024, Eric Wong wrote:

> Seems like error handling went wrong somewhere.  Could be caused
> by another error (OOM, open files limits, disk space, etc...)

Okay, I'll check, but I don't see anything unusual 12% disk space taken.

> What were you doing when this happened?  Were you using
> public-inbox-mda? public-inbox-watch? public-inbox-learn?

My mail server alerted me to the failure.  It uses public-inbox-mda.

> Is it reproducible?

The error occurred every five minutes for about three hours, until I
deactivated the timer triggering the action.

> I'm suffering from a nasty cold and insect bites

I'm sorry to read that.  What kind of insect bites?

Kind regards
Felix