Hallo, * Christian Meyer [Sun, Apr 11 2021, 01:26:01PM]: > Package: apt-cacher-ng > Version: 3.6.3-1 > Severity: important > X-Debbugs-Cc: c2h...@web.de > > Dear Maintainer, > > even after the recent acng updates I still see apt-cacher-ng (3.6.3-1 amd64) > stop working.
What you describe here does, all in one, not make much sense. Too many symptoms coming together which are not adding up. Are you sure that there is no bad memory or system instability involved? > Apt throws a bunch of errors like: > > E: Fehlschlag beim Holen von > http://deb.debian.org/debian/dists/bullseye/main/Contents-all Fehler beim > Lesen vom Server: Verbindung wurde durch den Se > rver auf der anderen Seite geschlossen. [IP: 127.0.0.1 3142] Closing connection is a potential outcome in worst situations but the connection wouldn't stay down permanently as seen in the rest of your log. Actually, that might be caused by periodic crashes so systemd keeps the server down for a while. Which brings me to the suspicion of system instability. Please send the output of journalctl -b0 -u apt-cacher-ng and also please set debug=7 in acng.conf or similar conf file. If that's a crash, please install systemd-coredump service and we can debug the corefiles later. > E: Einige Indexdateien konnten nicht heruntergeladen werden. Sie wurden > ignoriert oder alte an ihrer Stelle benutzt. > ... > > W: Das Depot »http://127.0.0.1:3142/deb.debian.org/debian bullseye Release« > enthält keine Release-Datei. > E: Fehlschlag beim Holen von > http://127.0.0.1:3142/deb.debian.org/debian/dists/bullseye/main/binary-i386/Packages > 503 Service Unavailable [IP: 127.0. > 0.1 3142] Oh, that's probably our "nice" apt hiding the actual error string and showing this dummy instead. It should match some error in the error log, though. This doesn't make sense. ACNG does not render this message string explicitly. Is there some proxy server involved? > Get:99 http://deb.debian.org/debian bullseye/main amd64 krb5-user amd64 > 1.18.3-4 [151 kB] > Get:100 http://deb.debian.org/debian bullseye/main amd64 ldap-utils amd64 > 2.4.57+dfsg-2 [206 kB] > Get:101 http://deb.debian.org/debian bullseye/main amd64 > linux-image-5.10.0-5-amd64 amd64 5.10.26-1 [53.4 MB] > Err:101 http://deb.debian.org/debian bullseye/main amd64 > linux-image-5.10.0-5-amd64 amd64 5.10.26-1 > Undetermined Error [IP: 127.0.0.1 3142] That's apt's insufficient error message which probably indicates a short read. Would fit to the connection refusal series. > Err:102 http://deb.debian.org/debian bullseye/main amd64 linux-image-amd64 > amd64 5.10.26-1 > Could not connect to 127.0.0.1:3142 (127.0.0.1). - connect (111: Connection > refused) [IP: 127.0.0.1 3142] > Err:103 http://deb.debian.org/debian bullseye/main amd64 whois amd64 5.5.8 > Unable to connect to 127.0.0.1:3142: [IP: 127.0.0.1 3142] > Since systemctl often tells me something about "Epoll ADD" failing: > # systemctl status apt-cacher-ng.service > apt-cacher-ng[646]: [warn] Epoll ADD(1) on fd 14 failed. Old events were 0; > read change was 1 (add); write change was 0 (none); close change was 0 > (none): Bad file descriptor > > my workaround is to automatically restart the service by a cronjob (and after > that /usr/lib/apt-cacher-ng/expire-caller.pl) when this line is seen. And now that is getting really odd. Do you have some kind of application firewall installed, like apparmor? > More information: > > Yes, my internet connection is very slow (around 8000 kbit/s) and that's my > reason to run acng). 8mbit/s isn't awful slow and it shouldn't make a difference anyway. > # less /var/log/apt-cacher-ng/apt-cacher.err.1 > Beside of tons of "Bad file descriptor" messages: > Fri Apr 9 11:13:05 > 2021|debrep/pool/main/f/ffmpeg/libavutil56_4.3.2-0+deb11u1_amd64.deb storage > error [HTTP/1.1 503 Bad file descriptor], last errno: Bad file descriptor > Fri Apr 9 11:13:06 > 2021|debrep/pool/main/c/codec2/libcodec2-0.9_0.9.2-4_amd64.deb storage error > [HTTP/1.1 503 Bad file descriptor], last errno: Bad file descriptor > Fri Apr 9 11:13:17 > 2021|debrep/pool/main/p/pulseaudio/libpulsedsp_14.2-2_amd64.deb storage error > [HTTP/1.1 503 Bad file descriptor], last errno: Bad file descriptor So I checked the code and it doesn't make sense. fileitem.cc:755 is the only location reporting that and it wouldn't get there when the filedescriptor is okay, and you cannot get that FD closed by any regular code path. We can have an interactive Jitsi session if you prefer to get this solved in realtime and it can be made reproducible somehow. Best regards, Eduard.
