From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id A30DB81814 for ; Wed, 24 Nov 2021 17:04:24 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7B7BC22228 for ; Wed, 24 Nov 2021 17:04:24 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (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 firstgate.proxmox.com (Proxmox) with ESMTPS id AC4BD2220C for ; Wed, 24 Nov 2021 17:04:23 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 3CFF445FF3 for ; Wed, 24 Nov 2021 17:04:23 +0100 (CET) From: Stoiko Ivanov To: pmg-devel@lists.proxmox.com Date: Wed, 24 Nov 2021 17:04:07 +0100 Message-Id: <20211124160409.60966-1-s.ivanov@proxmox.com> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.315 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% 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] [PATCH pmg-api 0/2] improve restart behavior of api daemons 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: , X-List-Received-Date: Wed, 24 Nov 2021 16:04:24 -0000 Sending as two patches - since I tested them individually, think both do make sense, but consider them independent of each other. Currently limiting the scope to pmgdaemon and pmgproxy, since we observed problems with the current behavior with those 2 recently, while I'm not aware of any similar issues with the other daemons in PMG pveproxy, pvedaemon already have the Restart policy set - but I'll gladly send the OOMPolicy patch if wanted. Stoiko Ivanov (2): api-daemons: restart on-failure api-daemons: set oom-policy to continue debian/pmgdaemon.service | 2 ++ debian/pmgproxy.service | 2 ++ 2 files changed, 4 insertions(+) -- 2.30.2