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 2D5287C562 for ; Fri, 15 Jul 2022 15:02:55 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 1A77B29172 for ; Fri, 15 Jul 2022 15:02:25 +0200 (CEST) Received: from mail.corep.it (mail.corep.it [93.186.252.128]) by firstgate.proxmox.com (Proxmox) with ESMTP for ; Fri, 15 Jul 2022 15:02:24 +0200 (CEST) Message-ID: <0bdcf88d-a22d-117b-269f-c765681d67c7@corep.it> Date: Fri, 15 Jul 2022 15:02:23 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.0.2 To: Thomas Lamprecht , Proxmox Backup Server development discussion , Mark Schouten References: <3283c4b8-7df3-8cd8-2886-b6d14ee3633b@proxmox.com> <4a05245f-6bd1-02da-f600-9976c4f1abf5@proxmox.com> <961f333d-9b92-0dc9-52b5-5664a37d47e5@proxmox.com> From: dea In-Reply-To: <961f333d-9b92-0dc9-52b5-5664a37d47e5@proxmox.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.403 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 NICE_REPLY_A -0.001 Looks like a legit reply (A) 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] Scheduler causing connectivity issues? X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2022 13:02:55 -0000 retry to upgrade 2.2-1->2.2-4 and reboot... Il 15/07/22 14:57, Thomas Lamprecht ha scritto: > Am 15/07/2022 um 14:01 schrieb dea: >> Mmmmm no, for me the same problem. >> >> Rollback 2.2.4 -> 2.2.1 and works great. >> >> > how do you test? > > did you reboot in between or dropped the page cache? > > also what is your output for the requested info: > > Am 13/07/2022 um 10:14 schrieb Thomas Lamprecht: >> FWIW, it would be still interesting to see a few metrics/CLI outputs from an affected >> system to hopefully ensure that there's nothing additional to that problem. >> >> - `head /proc/pressure/*` for some general info if the system is overloaded >> - `ls /var/lib/proxmox-backup/jobstates` just out of interest >> - `ss -tlpn` to see if another (old) proxy process is still accepting >> - `uptime` > `lscpu` and `free` would be good to know too. >