From nobody Wed Dec 4 17:20:39 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 4Y3PSH31TFz5fv94 for ; Wed, 04 Dec 2024 17:21:03 +0000 (UTC) (envelope-from dch@skunkwerks.at) Received: from fout-a8-smtp.messagingengine.com (fout-a8-smtp.messagingengine.com [103.168.172.151]) (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 4Y3PSG571lz4p0h for ; Wed, 4 Dec 2024 17:21:02 +0000 (UTC) (envelope-from dch@skunkwerks.at) Authentication-Results: mx1.freebsd.org; none Received: from phl-compute-02.internal (phl-compute-02.phl.internal [10.202.2.42]) by mailfout.phl.internal (Postfix) with ESMTP id D2B7613806FC; Wed, 4 Dec 2024 12:21:01 -0500 (EST) Received: from phl-imap-02 ([10.202.2.81]) by phl-compute-02.internal (MEProxy); Wed, 04 Dec 2024 12:21:01 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=skunkwerks.at; h=cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1733332861; x=1733419261; bh=M19TfVtMsIWDvupMq2hb5wsBSZ/arqNNQKwCPt6fyLk=; b= SryuAbwjcUV4s96231RuSznS8UvsFzPF/5uXkMgxcWmx757fZWKadHw0KFv+9jFG xAePKpZZ2SUL1KT4m1eICGGIJlfPw+fWIdDwbPBHmNR9KSL+Z2uSl4/jRgUlE1tt 2KU8RY+wyD2xrtA10hUvnRy3xTk5eVbOgiWu7e/cj2FtMhBT+OLB+1EPlx+WQMWH M+67Q/b3/V570UqLv5wVA1r2I8X28LPDZC5GOm9+vgyc34MHk5lzKNPjd3oda1a0 MwcBXxw3pB/1iCVhYf52zIVqdJeOO8+eNCP2PgXKyABi3zv3egQwPCxKM0WFVUR7 PJDqxcxsDH9+jG72LbeKAg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; t=1733332861; x=1733419261; bh=M 19TfVtMsIWDvupMq2hb5wsBSZ/arqNNQKwCPt6fyLk=; b=GVGJRSeAEE1OWwiyD 3zMIW0sss/rl/oXt4bsBsyCDNNsdfiMtKX8hX15LLuJZkwnT28AdguZUzTEc6Uqe FJy2f3+rPLDiA3fq/QtosSUz4adDOt4LoOeBrU7AFOGTNOKY33t9n3d0kL9BOtkE 4J2ZTWL9WzyiElGYDAfISOWN1Ws6h6eXIy+5WH5OTPgJ0RO/Ehm8K1+26n8QcRJL J9/AAoyEZbGZy3LWFXTjCohZLtd7LiDdWDirnxwsJmUF+l7CWIxEEr303RHaSAk6 9lCOuywVt00UqHOgaYUoZuhCmBxLqmCHrvNDgWBxkSJ6ySBFkBPyryRvJhxpHBdp E21UA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddrieehgdeliecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdpuffr tefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnth hsucdlqddutddtmdenucfjughrpefoggffhffvkfgjfhfutgfgsehtjeertdertddtnecu hfhrohhmpedfffgrvhgvucevohhtthhlvghhuhgsvghrfdcuoegutghhsehskhhunhhkfi gvrhhkshdrrghtqeenucggtffrrghtthgvrhhnpefgjeetffdutdduhedttefgteegvdeh feefgfektdefhfekudevhfefheekveeuteenucffohhmrghinheptghurhhlrdguvghvpd hsthgrtghkohhvvghrfhhlohifrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfr rghrrghmpehmrghilhhfrhhomhepuggthhesshhkuhhnkhifvghrkhhsrdgrthdpnhgspg hrtghpthhtohepvddpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepfhhrvggvsghs ugdqtghurhhrvghnthesfhhrvggvsghsugdrohhrghdprhgtphhtthhopehfrhgvvggssh guseifrghlshhtrghtthdquggvrdguvg X-ME-Proxy: Feedback-ID: ic0e84090:Fastmail Received: by mailuser.phl.internal (Postfix, from userid 501) id 34268B0006A; Wed, 4 Dec 2024 12:21:01 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface 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 Date: Wed, 04 Dec 2024 17:20:39 +0000 From: "Dave Cottlehuber" To: "FreeBSD User" , freebsd-current Message-Id: <6626e5c0-ba01-4966-a28c-82a25251ca3f@app.fastmail.com> In-Reply-To: <20241203204609.68e04364@hermann.dmz.walstatt.dynvpn.de> References: <20241203204609.68e04364@hermann.dmz.walstatt.dynvpn.de> Subject: Re: HELP! fetch: stuck forever OR error: RPC failed: curl 56 recv failure: Operation timed out Content-Type: text/plain Content-Transfer-Encoding: 7bit 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:209242, ipnet:103.168.172.0/24, country:US] X-Rspamd-Queue-Id: 4Y3PSG571lz4p0h X-Spamd-Bar: ---- 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. 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