From nobody Thu Dec 5 16:33:54 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 4Y40Mj0Qjyz5dlM2 for ; Thu, 05 Dec 2024 16:34:09 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp6.goneo.de (smtp6.goneo.de [IPv6:2001:1640:5::8:31]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Y40Mh52P5z436Q for ; Thu, 5 Dec 2024 16:34:08 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; none Received: from hub1.goneo.de (hub1.goneo.de [85.220.129.52]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp6.goneo.de (Postfix) with ESMTPS id 0405C240D59; Thu, 5 Dec 2024 17:33:59 +0100 (CET) Received: from hub1.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by hub1.goneo.de (Postfix) with ESMTPS id 234412402D6; Thu, 5 Dec 2024 17:33:57 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1733416437; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Iax3Dt/7wqw4yqL3X4GVNj9S2MuoIl6fkTnhJ7IUJ+8=; b=gdtq60DKWDkW9pmgmi662N0uiKu+K1XkrVnpiosGPDVmlz9+UqTfnUq3nTvFWNjnyr6L9M ChbthmvFsGPT1jXxGBT4i6A/wwL1SswiCff8ToUOGfO00Tjer6mcKgLNYYbQx/m/MHvP8O GY/3wXwm17e/PDWqg56zqwdhZkHa3BREu5y+6XPXhFzj2mxogbuDIm9Hqk6kvk/5KpOEEB A/hZKlWEDN84FhBf6YUyE6+SdcziYMzOA5Il530N853T9O5Tw1yXQWVOqSY/iMGrPEzbck Tu8q1QFwzrP28u9djwZXpRAdFI+gpSvdygbT+Si68/MnZHvLO99lR389Vmx39g== Received: from hermann.intern.walstatt.dynvpn.de (dynamic-077-183-116-031.77.183.pool.telefonica.de [77.183.116.31]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by hub1.goneo.de (Postfix) with ESMTPSA id CB74E24029B; Thu, 5 Dec 2024 17:33:56 +0100 (CET) Date: Thu, 5 Dec 2024 17:33:54 +0100 From: FreeBSD User To: Daniel Tameling Cc: freebsd-current@freebsd.org Subject: Re: HELP! fetch: stuck forever OR error: RPC failed: curl 56 recv failure: Operation timed out Message-ID: <20241205173354.23c4e592@hermann.intern.walstatt.dynvpn.de> In-Reply-To: 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=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-UID: 82e4cd X-Rspamd-UID: 2ceb5b X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:25394, ipnet:2001:1640::/32, country:DE] X-Rspamd-Queue-Id: 4Y40Mh52P5z436Q X-Spamd-Bar: ---- On Thu, 5 Dec 2024 16:55:00 +0100 Daniel Tameling wrote: > 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. No, pure Hardware and FreeBSD ... > > Otherwise I would start with ping and traceroute to figure out if they show this issue > and where it occurs. >