From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <mark@tuxis.nl> 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 A0D48918BB for <pbs-devel@lists.proxmox.com>; Fri, 9 Sep 2022 10:31:58 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 9CF6724596 for <pbs-devel@lists.proxmox.com>; Fri, 9 Sep 2022 10:31:58 +0200 (CEST) Received: from kerio.tuxis.nl (alrami.saas.tuxis.net [31.3.111.57]) (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 for <pbs-devel@lists.proxmox.com>; Fri, 9 Sep 2022 10:31:57 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=tuxis.nl; s=mail; h=from:reply-to:subject:date:message-id:to:mime-version:content-type: content-transfer-encoding:in-reply-to:references; bh=qkJzg8XqmUBkiL/F2C7M4Gr5QI2EXO+QQVF4bAWelFs=; b=lsJFJLm7hYiCCzKGhVxREvGpPPnj/a/JitAse7nJyJZrLmK3rrBVR6ag2Me2mAe3/uSU1Hts+fQIr sN0KE4y+LFSF6h07eezAdPVfdBo5Kzo0z7/xYO9lJOOQZ/lTWuWBidLR4d2rZO2rqerdkef3YgkDK9 8RvtPi2eZ2dokSB2YphhK8ilrlrUFVGmWHm1IJE+v+rn+Tzu7nVM2Gur3WWbWbA4R0LASKcaEfuf31 X/kvxou1B5deCMR5nWM6tEj6B7LVCyLFO+mEgtnQv1JrC+3ku42Bc+EuI1oqaJT9CgQL7roVaczXbv JFp2jBOg5jG8nJ3sKruY9Q0NUUF7AaA== X-Footer: dHV4aXMubmw= Received: from [IPv6:2a03:7900:64::1001] ([2a03:7900:64::1001]) (authenticated user mark@tuxis.nl) by kerio.tuxis.nl (Kerio Connect 9.4.2) with ESMTPSA (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256 bits)); Fri, 9 Sep 2022 10:31:50 +0200 From: "Mark Schouten" <mark@tuxis.nl> To: "Thomas Lamprecht" <t.lamprecht@proxmox.com>, "Proxmox Backup Server development discussion" <pbs-devel@lists.proxmox.com> Date: Fri, 09 Sep 2022 08:31:44 +0000 Message-Id: <emda8dd7ed-8534-4281-ab2c-89ae1957db0c@3a15c2fd.com> In-Reply-To: <87a756b4-ef3a-47c4-2219-df252b7cce9d@proxmox.com> References: <emb468a227-f50d-49a8-92f2-1c3a0e7fa058@3a15c2fd.com> <87a756b4-ef3a-47c4-2219-df252b7cce9d@proxmox.com> Reply-To: "Mark Schouten" <mark@tuxis.nl> User-Agent: eM_Client/9.1.2109.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-SPAM-LEVEL: Spam detection results: 0 AWL 0.020 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: Re: [pbs-devel] Too many open files X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion <pbs-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pbs-devel>, <mailto:pbs-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pbs-devel/> List-Post: <mailto:pbs-devel@lists.proxmox.com> List-Help: <mailto:pbs-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel>, <mailto:pbs-devel-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Fri, 09 Sep 2022 08:31:58 -0000 Hi, >How many FDs are open for the proxy? > >ls -1 /proc/$(pidof proxmox-backup-proxy)/fd | wc -l This was not that much at this moment, but aroung 0.00 hours, the=20 counter increases, I suspect. ;) >No, but it doesn't increase it's soft limit to the hard limit, something w= e >want to do in the future. > >As workaround try increasing soft (and possible hard) limit for root and b= ackup >user, you can do that by editing `/etc/security/limits.conf`, adding lines = like: > >backup soft nofile 524288 >root soft nofile 524288 > >(should set soft to current hard limit) This did not work for me. >Or alternatively use a systemd service override to make it really process= specific: > ># systemctl edit proxmox-backup-proxy.service > >There add a "[Service]" Section, if not already existing and a "LimitNOFIL= E=3DX" below, >e.g.: > >[Service] >LimitNOFILE=3D524288 > >Save and close the editor and restart the service, then do the same for th= e >proxmox-backup.service > >As said, we plan to upper that soft limit too in the future. This worked like a charm. Let=E2=80=99s see if it helps tonight during peak= =20 hours. Thanks! =E2=80=94 Mark Schouten, CTO Tuxis B.V. mark@tuxis.nl