From nobody Thu Dec 5 10:51:03 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 4Y3rlz6XrDz5gJbB for ; Thu, 05 Dec 2024 10:51:11 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp052.goneo.de (smtp5.goneo.de [IPv6:2001:1640:5::8:30]) (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 4Y3rlz4Wp5z4kDJ for ; Thu, 5 Dec 2024 10:51:11 +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 smtp5.goneo.de (Postfix) with ESMTPS id 072D8240E51; Thu, 5 Dec 2024 11:51:08 +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 2DB182402D8; Thu, 5 Dec 2024 11:51:06 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1733395866; 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=w9mqz/VRZUfR7JG2pXywXz0fqchkkz73/ZV+e0YKOrA=; b=fmvnvL30/+uzhJXE6p17Zer/9qQw1dpJogt2wUeMK9pni1TTFGQUmTdNb9Y7cKSYNLoT0k L4IoWclVAzwN5Ww9doXlr8xYk7DAhbwtaWx2PtIOaVoSDJM/JEHQI3DtIHn7jnkKvEPeUA QtT0x1PvWvDrRwOIG6oqtXhIQel8IwsCwUhDobOwX6EdqyhpAg3gGTMQGOhw0AFk/mFb9N 9JgtsGSZn57PSn+WhjNeF5h8nw6bXgHZDuHiy6uy3WHxkxFBCSYN7whTrJpcvjga0lBTSY zqznRVrAqtEQtSAaER2MAL5jbTsYXIIHDSjcVHNzOH2oy7NYLK9QrMsvMBquxw== 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 DBE472402D6; Thu, 5 Dec 2024 11:51:05 +0100 (CET) Date: Thu, 5 Dec 2024 11:51:03 +0100 From: FreeBSD User To: "Dave Cottlehuber" Cc: freebsd-current Subject: Re: HELP! fetch: stuck forever OR error: RPC failed: curl 56 recv failure: Operation timed out Message-ID: <20241205115103.1ed6d7f6@hermann.intern.walstatt.dynvpn.de> In-Reply-To: <6626e5c0-ba01-4966-a28c-82a25251ca3f@app.fastmail.com> References: <20241203204609.68e04364@hermann.dmz.walstatt.dynvpn.de> <6626e5c0-ba01-4966-a28c-82a25251ca3f@app.fastmail.com> 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: ada1e8 X-Rspamd-UID: b1c219 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: 4Y3rlz4Wp5z4kDJ X-Spamd-Bar: ---- 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