From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 896A01FF191 for ; Tue, 23 Sep 2025 18:48:40 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id ECBD5139F4; Tue, 23 Sep 2025 18:49:10 +0200 (CEST) Mime-Version: 1.0 Date: Tue, 23 Sep 2025 18:49:07 +0200 Message-Id: To: "Max R. Carrara" , From: "Max R. Carrara" X-Mailer: aerc 0.18.2-0-ge037c095a049 References: <20250923151929.415784-1-m.carrara@proxmox.com> In-Reply-To: <20250923151929.415784-1-m.carrara@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1758646134829 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.086 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pmg-devel] superseded: [PATCH pmg-api master v1] systemd: fix report services failing if triggered to early by timers X-BeenThere: pmg-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Mail Gateway development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pmg-devel-bounces@lists.proxmox.com Sender: "pmg-devel" v2: https://lore.proxmox.com/pmg-devel/20250923164723.532488-1-m.carrara@proxmox.com/ On Tue Sep 23, 2025 at 5:19 PM CEST, Max R. Carrara wrote: > Currently, the `pmgreport.service` and `pmgspamreport.service` units > might fail if their corresponding timers activate them too early. > > To elaborate, both timers have `Persistent=true` in addition to their > `OnCalendar` option. `Persistent=true` means that the timer's service > unit will be triggered immediately when the timer is activated, but > only if it would have been triggered while the timer was inactive [0]. > > Since the timers are activated relatively early, they might trigger > their service units before postfix.service and postgresql.service have > come up, causing `pmgreport.service`, or `pmgspamreport.service`, or > both of them to fail. > > Fix this by letting both service units wait until postfix and postgres > are up, which are necessary for the units to run successfully. Do this > by adding the `After` and `Wants` options for `postfix.service` and > `postgresql.service` to both service units. > > [...] _______________________________________________ pmg-devel mailing list pmg-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel