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 F26A7E52F for ; Fri, 22 Apr 2022 18:55:31 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id E8F3029DA8 for ; Fri, 22 Apr 2022 18:55:01 +0200 (CEST) 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)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id A5B7B29D9A for ; Fri, 22 Apr 2022 18:55:00 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 7E75742763 for ; Fri, 22 Apr 2022 18:55:00 +0200 (CEST) Message-ID: Date: Fri, 22 Apr 2022 18:54:59 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:100.0) Gecko/20100101 Thunderbird/100.0 Content-Language: en-US To: Proxmox VE development discussion , Matthias Heiserer References: <20220422144358.3217098-1-m.heiserer@proxmox.com> <20220422144358.3217098-2-m.heiserer@proxmox.com> From: Thomas Lamprecht In-Reply-To: <20220422144358.3217098-2-m.heiserer@proxmox.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL 1.625 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 -3.185 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 URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [anyevent.pm] Subject: Re: [pve-devel] [PATCH v1 http-server 2/2] AnyEvent: disable upload timeout X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2022 16:55:32 -0000 On 22.04.22 16:43, Matthias Heiserer wrote: > During some testing, I had various requests time out. > Bug reports describing that behaviour include #795 from 2015 > and #66 from 2011. > While disabling the timeout is certainly not ideal, it should fix this > issue for now. > Alternatively, a long timout could be set (e.g. 60 seconds). what is the current timeout value? > > Signed-off-by: Matthias Heiserer > --- > src/PVE/APIServer/AnyEvent.pm | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/src/PVE/APIServer/AnyEvent.pm b/src/PVE/APIServer/AnyEvent.pm > index ade3c05..c143fb4 100644 > --- a/src/PVE/APIServer/AnyEvent.pm > +++ b/src/PVE/APIServer/AnyEvent.pm > @@ -1500,6 +1500,7 @@ sub unshift_read_header { > outfh => $outfh, > }; > $reqstate->{tmpfilename} = $tmpfilename; > + $reqstate->{hdl}->{timeout} = 0; > $reqstate->{hdl}->on_read(sub { > $self->file_upload_multipart($reqstate, $auth, $method, $path, $state); > });