From nobody Thu Dec 5 15:55:00 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Y3zVf0VY2z5ggH9 for ; Thu, 05 Dec 2024 15:55:06 +0000 (UTC) (envelope-from tamelingdaniel@gmail.com) Received: from mail-ej1-x62f.google.com (mail-ej1-x62f.google.com [IPv6:2a00:1450:4864:20::62f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Y3zVd1rmTz3xB2 for ; Thu, 5 Dec 2024 15:55:05 +0000 (UTC) (envelope-from tamelingdaniel@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=algA1LAn; spf=pass (mx1.freebsd.org: domain of tamelingdaniel@gmail.com designates 2a00:1450:4864:20::62f as permitted sender) smtp.mailfrom=tamelingdaniel@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ej1-x62f.google.com with SMTP id a640c23a62f3a-aa1e6ecd353so165326466b.1 for ; Thu, 05 Dec 2024 07:55:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1733414102; x=1734018902; darn=freebsd.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=kjyfxYNNZDc+NH+SmiTaSl5+hGAaKXTYSiokRshpguY=; b=algA1LAnsXUsDNQa6bGC3SEjQvvx+YBNtsTtb1ao3VnbolXm/IggzYNZZb9httcQEl h2O6zLCPRAVk5LXGyKR8TDkgOhyH5Dq2+9rtr4sPz3ZmToZdX26FVN+DmQXnSXvqXp2a IDaXtPTC2dMUUZE+8dd/KGsns5bUbTkcrE/dorqiHMu6ivQj+1wr5ECM7J7D3aeTzPTd 7N2qPTQdpf99cIkOmUctJcvDiFMqx0xeFrU4rFXuzaSK3EsfV5uoNLiErnG3GEsTNdsz 94lw9aJ9Uo1zdTxrvIY2yC8LgY4Jmnovq/Cxw1pslLGO9UidurCnFt/DJpXJDQst12Y4 aykQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1733414102; x=1734018902; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=kjyfxYNNZDc+NH+SmiTaSl5+hGAaKXTYSiokRshpguY=; b=VVTnMentTD3C54gpHTp0twChgDmYUMK42icYnj2TEz5R4/FUYiPUb6AzhReoJmqIHn nzis4I1YImfmEQ8q5HyMtKOAovX2CZ/Yz9dnBfP0VnnLlkWQGsBw9DubNB3KyaOuQZXg eRcImwauCT58l0eHjy2toDMDdKuCM7s6YvjjoIi6Gk6vRB1qdo3ONL8Zb7tuwJHHXdFH Wyr8bYUVJjA1ZJf7wPSr6ZESsGK84q26WJr8or9bLBQ/L4De9vFj5FaS30q7Q2VmSAwh shP/Fh3oQvzLqJOjIitCLB6ZqHmiHKE88csLwBaq2NU+55hm9mLnLw4DPJ6GHoVNFIpZ RqwA== X-Gm-Message-State: AOJu0YzHhD3QH6BxfQ4fvAPBzoLSv2d/kvSXDkZDYnHYJ4yem/Ouj48c xZQ8L0ZsRByB/n1R9GVpEdo6YNU0kWqqC8j+YyVeHWRvGtl+5AYq1RqSUA== X-Gm-Gg: ASbGncvDu88MMWfy3goJp5gKxHE8l5/HdDdvyjX9oxpzDRlQ5fiv7+m28LmbZlpzMN8 i41f3Lc+m1+OziOPoAYBEscEdPXki1GR0CDMavWdFRFHwWFii5UQ3u7+P5bOUkETi8Ef0YSokst uD2+YDaCu3pGpP5wAHFuCT/zO/2YCQlU9PHlm7K4JRsz158fq7fc8loqq/oXbuZ9pJxzwYevo5A 0sxVB1fSqnACbRN90SXjHQtVlwIl9yXwIovrfJTEhKWQqUgi1ParLdd X-Google-Smtp-Source: AGHT+IH/WhYrOdn4vZoecf7iX7JszQ0xDM7C9IGNMW0FPKKhPe2X4DE1mLG2nminTthzvtNaWvRTVg== X-Received: by 2002:a05:6402:34d5:b0:5d0:e9b7:170c with SMTP id 4fb4d7f45d1cf-5d10cb5c39fmr15791488a12.18.1733414102194; Thu, 05 Dec 2024 07:55:02 -0800 (PST) Received: from localhost ([2001:9e8:c402:7000:5ec9:c431:7277:2312]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-aa6260ae4f3sm108460366b.159.2024.12.05.07.55.01 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 05 Dec 2024 07:55:01 -0800 (PST) Date: Thu, 5 Dec 2024 16:55:00 +0100 From: Daniel Tameling To: freebsd-current@freebsd.org Subject: Re: HELP! fetch: stuck forever OR error: RPC failed: curl 56 recv failure: Operation timed out Message-ID: References: <20241203204609.68e04364@hermann.dmz.walstatt.dynvpn.de> <6626e5c0-ba01-4966-a28c-82a25251ca3f@app.fastmail.com> <20241205115103.1ed6d7f6@hermann.intern.walstatt.dynvpn.de> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20241205115103.1ed6d7f6@hermann.intern.walstatt.dynvpn.de> X-Spamd-Result: default: False [-3.96 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.96)[-0.959]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; SUBJECT_HAS_EXCLAIM(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; MISSING_XM_UA(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; MID_RHS_MATCH_FROMTLD(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::62f:from] X-Rspamd-Queue-Id: 4Y3zVd1rmTz3xB2 X-Spamd-Bar: --- On Thu, Dec 05, 2024 at 11:51:03AM +0100, FreeBSD User wrote: > On Wed, 04 Dec 2024 17:20:39 +0000 > "Dave Cottlehuber" wrote: > > Thank you very much for responding! > > > On Tue, 3 Dec 2024, at 19:46, FreeBSD User wrote: > > > On most recent CURRENT (on some boxes of ours, not all) fetch/git seem > > > to be stuck > > > forever fetching tarballs from ports, fetching Emails via claws-mail > > > (TLS), opening > > > websites via librewolf and firefox or pulling repositories via git. > > > > > > CURRENT: FreeBSD 15.0-CURRENT #1 main-n273978-b5a8abe9502e: Mon Dec 2 > > > 23:11:07 CET 2024 > > > amd64 > > > > > > When performing "git pull" und /usr/ports, I received after roughly 5-7 minutes: > > > > > > error: RPC failed: curl 56 recv failure: Operation timed out > > > > Generally it would be worth seeing if the HTTP(S) layers are doing the right thing or > > not, and then working down from there, to tcpdump / wireshark and then if necessary > > into kernel itself. > > My skills are limited, according to packet analysis utilizing tcpdum/wireshark (and > theory,of course). I tried due to "a feeling" my used older Intel based NIC could have > some checksum issues like in the past (I saw e1000 driver updates recently flowing into > FreeBSD CURRENT). > > > > If fetch fails reliably in ports distfile fetching, then isolate a suitable tarball, > > and try it again in curl, with tcpdump already prepared to capture traffic to the > > remote host. > > > > tcpdump -w /tmp/curl.pcap -i ... host ... > > > > env SSLKEYLOGFILE=/tmp/ssl.keys curl -vsSLo /dev/null --trace > > /tmp/curl.log https://what.ev/er > > > > I would guess that between the two something useful should pop up. > > > > I like opening the pcap in wireshark, it often has angry red and black highlighted > > lines already giving me a hint. > > > > The SSLKEYLOGFILE can be imported into wireshark, and allows decrypting the TLS traffic > > as well in case there are issues further in. Very handy, > > see https://everything.curl.dev/usingcurl/tls/sslkeylogfile.html for how to do that. > > > > If your issues only occur with git pull, its also curl inside and supports similar > > debugging. Ferreting > > through https://stackoverflow.com/questions/6178401/how-can-i-debug-git-git-shell-related-problems/56094711#56094711 should get you similar info. > > > > A+ > > Dave > > > > Thanks for the hints and precious tips! I'll digg deeper into the matter. > > In the meanwhile, I updated some other machines running CURRENT since approx. two weeks > with an older CURRENT to the most recent one - and face similar but not identical > problems! > Updating exiting FreeBSD repositories, like src.git and ports.git, show no problems > except they take longer to accomplish than expected. > Cloning a repo is impossible, after 10 or 15 minutes I receive a timeout. > > On aCURRENT recently updated and worked flawlessly before (CURRENT now: FreeBSD > 15.0-CURRENT #5 main-n274014-b2bde8a6d39: Wed Dec 4 22:22:22 CET 2024 amd64), cloning > attempts for 14.2-RELENG ends up in this mess: > > # git clone --branch releng/14.2 https://git.freebsd.org/src.git 14.2-RELENG/src/ > Cloning into '14.2-RELENG/src'... > error: RPC failed; curl 56 Recv failure: Operation timed out > fatal: expected 'packfile' > > This is nasty. The host now in question has an i350 based dual-port NIC - the host's > kernel is very similar to the box I reported the issue first time, both do have > customized kernels (in most cases, I compile several modules like ZFS and > several NETGRAPH modules statically into the kernel - a habit inherited from a small FBSD > project I configured (I wouldn't say developed) which does not allow loadable kernel > modules due to regulations. > > I hoped others would stumble over this tripwire in recent CURRENT sources, since the > phenomena and its distribution over a bunch of CURRENT boxes with different OS states > seemingly show different behviour. > > And for the record: I also build my ports via poudriere and mostly via make. I also > rebuilt in a two day's marathon all packages via "make -f" - for librewolf, curl and so > on to ensure having latest sources/packages. > > (I repeat myself here again, sorry, its for the record). > > Will report in on further development and "investigations" > > Kind regards and thanks, > > oh > > This is a shot into the dark but is this a virtual machine? VirtualBox 7.1.0 had some networking issues that got fixed later. Otherwise I would start with ping and traceroute to figure out if they show this issue and where it occurs. -- Best regards, Daniel