Your message dated Wed, 30 Apr 2025 00:03:43 +0200 with message-id <[email protected]> and subject line Re: #998705 Many 502 errors, when using apt-cacher-ng for Debian installation has caused the Debian Bug report #998705, regarding Many 502 errors, when using apt-cacher-ng for Debian installation to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 998705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998705 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: apt-cacher-ng Severity: minor Hi, since some days I use apt-cacher-ng with Debian installer, via setting d-i mirror/http/proxy string http://192.168.10.200:3142 in my preseed file, which is great for installation tests and the like! While this works fine, when - for example - I install only the standard task (which means just a minimal text-based system without desktop environment), the installation fails due to many 502 Bad Gateway errors, when the installer has to download many packages (like ~1200 packages for an installation with GNOME desktop). This happens, when I set deb.debian.org as mirror to use, and also when I use ftp.de.debian.org directly. So, I guess the problem is not on the mirror/redirector-service side. When I retry the failed installation step (downloading package files) several times, I get all the needed packages downloaded at the end, and then the installation wents on and succeeds. Further info: when I then restart the whole installation again from scratch (with the same preseed file and therefore the new installation also uses apt-cacher-ng with its already downloaded files in cache), the installation succeeds directly without any error. So massively 'downloading-caching-serving' directly in chain seems to evoke the problem... Test environment: I have a Thinkpad laptop running Bullseye, and apt-cacher-ng is running on this machine. I'm performing the test installations in a qemu instance on the same laptop. Hmm, while writing this, something comes to mind: I have a high-performance FTTH internet connection, so package download is fast. Maybe the specific hardware/network setup here is part of the problem / is causing it? Ok, will sent this report anyway, setting the severity to minor. So long Holger -- Holger Wansing <[email protected]> PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
--- End Message ---
--- Begin Message ---Hi, I'm really sorry for the long delay on coming back to this report! I confirm that this bug is solved: on a bookworm machine, I used apt-cacher-ng for installing trixie via d-i, and this included downloading a massive amount of packages (I tested the installation of the different Debian Pure blends, now being provided by the d-i). And I did not get this 502 errors anymore, so I'm closing this report. Greetings Holger -- Holger Wansing <[email protected]> PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
--- End Message ---
