Hi Paul, On 2026-02-05 07:20, Paul Gevers wrote: > I'm recently seeing a lot of failures with apt-cacher-ng on the loong64 host > of ci.debian.net, which appeared to me to be related to parallel downloads > of InRelease. Chris only took the fuse3.patch to fix bug 1084459 (the bug > where this bug was cloned from) and now I'm wondering if the race you fixed > with fix-race.patch is more likely to occur after the switch to fuse3. What > happens if the race isn't fixed and two requests for the same file come in? > > What I'm seeing is a lot of failures with this error by apt: > 503 Cannot allocate memory [IP: 127.0.0.1 3142]
I'm having very frequent issues with InRelease too, in my case the error message is different though: 503 Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142] Relatedly, I see the following in /var/log/apt-cacher-ng/apt-cacher.err: Thu Aug 13 07:47:54 2026|Failure to move file /var/cache/apt-cacher-ng/uburep/dists/resolute/InRelease out of the way or cannot create /var/cache/apt-cacher-ng/uburep/dists/resolute/InRelease.1786607274 - errno: File exists Thu Aug 13 07:47:54 2026|Error creating file item for uburep/dists/resolute/InRelease -- check file permissions! This is with apt-cacher-ng 3.7.5-1, hence before the fuse2 -> fuse3 changes. HTH, ema
