From nobody Fri Dec 6 18:40:02 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 4Y4g6Z46n3z5ggQt; Fri, 06 Dec 2024 18:40:06 +0000 (UTC) (envelope-from SRS0=L9Uk=S7=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (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 4Y4g6Z1Vxrz4wb4; Fri, 6 Dec 2024 18:40:06 +0000 (UTC) (envelope-from SRS0=L9Uk=S7=klop.ws=ronald-lists@realworks.nl) Authentication-Results: mx1.freebsd.org; none Date: Fri, 6 Dec 2024 19:40:02 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1733510404; 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: in-reply-to:in-reply-to; bh=wo6irttu6YzvMgBq3VfIeBYeAmjweovonVFsAZ24vFg=; b=U+U5Nn05GL3kaCyQ5MF0Krv15x9TrfxRKXAwM8KX2Jvz62ezUOITVH0Z4BdL3YT9oGD2T3 2YYzk8Bbz6cvgmXhgnITDIAKIEezIIu2uqRf1Kgco0DPTywoQbtOu5DIQ7g1GmJZPqjh6s I3hXnypwwAyyKEWVtD54RdsWDj419/caI15l5xvm4+kbNXpk2WUKx1cT+/72uVhQp54Dlk C1eCL8fGczTTt1sV22L4Av1ORMwTtsNe6B0fR45wpxe8UrYcKcTA/i2iEFLrK/TujP/Tvx tJGumj357Jhv4fGPJFgrscg3YYOJzQWIf/k+examNoh81ncvGdRnC4VCNDd/4w== From: Ronald Klop To: FreeBSD User Cc: freebsd-ipfw@freebsd.org, freebsd-current@freebsd.org Message-ID: <279848701.11738.1733510402875@localhost> In-Reply-To: <20241206034709.4dd32cc5@thor.intern.walstatt.dynvpn.de> Subject: Re: HELP! fetch: stuck forever OR error: RPC failed: curl 56 recv failure: Operation timed out 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: multipart/alternative; boundary="----=_Part_11737_1079703555.1733510402870" X-Mailer: Realworks (731.101) Importance: Normal X-Priority: 3 (Normal) 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:3265, ipnet:194.109.0.0/16, country:NL] X-Rspamd-Queue-Id: 4Y4g6Z1Vxrz4wb4 X-Spamd-Bar: ---- ------=_Part_11737_1079703555.1733510402870 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Might be useful to share your ipfw config. Van: FreeBSD User Datum: 6 december 2024 03:47 Aan: freebsd-current@freebsd.org, freebsd-ipfw@freebsd.org Onderwerp: Re: HELP! fetch: stuck forever OR error: RPC failed: curl 56 recv failure: Operation timed out > > > Am Thu, 5 Dec 2024 17:33:54 +0100 > FreeBSD User schrieb: > > I found the culprit! > > Disabling IPFW ("ipfw disable firewall") turns system back to normal! > > For the record: on recent CURRENT, since approx. Nov. 30 and/or December 1st CURRENT seems to > corrupt network connections. > > IPFW is compiled statically into the kernel. > > The problem sketched below can be reproduced in a more or less obvious manner on recent > CURRENT: git pull/git clone of a regular FreeBSD source repo or ports via git+https takes > either a couple of time (up to several mintes to initiate the pull) - or, in some worse cases > here, the box runs into > error: RPC failed; curl 56 Recv failure: Operation timed out > > claws-mail complains about "corrupted/broken stream", fetching emails takes Aeons - forever, > the client does not come back even after several hours. > > > 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. > > > > > > > > > > > -- > O. Hartmann > > > > > ------=_Part_11737_1079703555.1733510402870 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Might be useful to share your ipfw config. 

Van: FreeBSD User <freebsd@walstatt-de.de>
Datum: 6 december 2024 03:47
Aan: freebsd-current@freebsd.org, freebsd-ipfw@freebsd.org
Onderwerp: Re: HELP! fetch: stuck forever OR error: RPC failed: curl 56 recv failure: Operation timed out

Am Thu, 5 Dec 2024 17:33:54 +0100
FreeBSD User schrieb:

I found the culprit!

Disabling IPFW ("ipfw disable firewall") turns system back to normal!

For the record: on recent CURRENT, since approx. Nov. 30 and/or December 1st CURRENT seems to
corrupt network connections.

IPFW is compiled statically into the kernel.

The problem sketched below can be reproduced in a more or less obvious manner on recent
CURRENT: git pull/git clone of a regular FreeBSD source repo or ports via git+https takes
either a couple of time (up to several mintes to initiate the pull) - or, in some worse cases
here, the box runs into
error: RPC failed; curl 56 Recv failure: Operation timed out

claws-mail complains about "corrupted/broken stream", fetching emails takes Aeons - forever,
the client does not come back even after several hours.

> 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.
> >   
>
>



-- 
O. Hartmann




------=_Part_11737_1079703555.1733510402870--