On Thu, Apr 9, 2020 at 6:04 pm, Eduard Bloch <e...@gmx.de> wrote:
Hallo,
* Pirate Praveen [Wed, Apr 08 2020, 03:31:59PM]:
On Sun, Apr 5, 2020 at 9:50 pm, Eduard Bloch <e...@gmx.de> wrote:
> Great. Anyway, after digging in messy code for days, I decided to
make a
> regular release ASAP. Please check version 3.4-1 when it has hit
your
> mirrors. If the problem does not go away then, again, please
provide a
> raw tcp dump.
The problem is still there. Weirdly, a package download failed
multiple
times succeded after I ran the tcpdump command. The tcp dump
attached. Will
try again to capture when it actually fails.
Something is REALLY strange on your systems. Looking at the dump, I
see
a flood of TCP retransmissions, for no apparent reason, basically
everything is retransmitted. That might happen sometimes but not in
such
massive amount, especially not in a LAN. And the actual header is
reassembled late in the stream.
TCP should be able to untangle this mess, but it's still too weird.
boutil and terceiro also reported same problem yesterday in
#debian-ruby irc (copying them). So I think the issue is not specific
to me.
boutil: hi! do you experience many "Hash Sum mismatch" when doing
upgrades with apt-cache-ng?
terceiro: I also get those sometimes, restarting usually helps
Is there a network switch inbetween?
It fails the same way with a wifi LAN and also via my mobile tethered
connection.
Did you modify global network
settings (via procfs or driver module options)?
No, no such changes.
Or using non-standard
kernels on any side?
No.
You might also try patching and recompilling apt-cacher-ng (version
3.4)
like this. It might mitigate the problem to a certain extent but even
if
it does, it cannot fully it.
I will try this and report how it goes.
diff --git a/debian/changelog b/debian/changelog
index 0ec3fa6..b509482 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,4 +1,4 @@
-apt-cacher-ng (3.4-1) unstable; urgency=low
+apt-cacher-ng (3.4-1.0.1) unstable; urgency=low
* New upstream release
+ potentially closes: #952811
diff --git a/debian/rules b/debian/rules
index 8121788..5a2fd1f 100755
--- a/debian/rules
+++ b/debian/rules
@@ -9,7 +9,7 @@ include /usr/share/dpkg/buildflags.mk
# cmake doesn't respect CPPFLAGS, use the workaround as suggested in
# https://wiki.debian.org/Hardening#Notes_for_packages_using_CMake
CFLAGS += $(CPPFLAGS)
-CXXFLAGS += $(CPPFLAGS)
+CXXFLAGS += $(CPPFLAGS) -DNO_TCP_TUNING
DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
Best regards,
Eduard.
--
<Tolimar> Nanu? Wird postrm remove nicht aufgerufen, wenn man ein
Paket gleich
purged?
<weasel> wer weiss das schon so genau
<weasel> ausser vielleicht ian und NMs
