Am Montag, dem 12.04.2021 um 21:13 +0200 schrieb Eduard Bloch: > 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 > > 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?
Until now I have no hint to that direction, but I will test memory and / or replace the machine. > Please send the output of > journalctl -b0 -u apt-cacher-ng For today (and cron driven restarts on errors every 3 minutes) it is: Apr 13 07:57:37 121-My apt-cacher-ng[202463]: [warn] Epoll ADD(1) on fd 13 failed. Old events were 0; read change was 1 (add); write change was 0 (none); close change was 0 (none): Bad file descriptor Apr 13 08:00:02 121-My systemd[1]: Stopping Apt-Cacher NG software download proxy... Apr 13 08:00:02 121-My systemd[1]: apt-cacher-ng.service: Succeeded. Apr 13 08:00:02 121-My systemd[1]: Stopped Apt-Cacher NG software download proxy. Apr 13 08:00:02 121-My systemd[1]: apt-cacher-ng.service: Consumed 55.182s CPU time. Apr 13 08:00:02 121-My systemd[1]: Starting Apt-Cacher NG software download proxy... Apr 13 08:00:02 121-My systemd[1]: Started Apt-Cacher NG software download proxy. Apr 13 08:00:40 121-My apt-cacher-ng[389015]: [warn] Epoll ADD(1) on fd 13 failed. Old events were 0; read change was 1 (add); write change was 0 (none); close change was 0 (none): Bad file descriptor Apr 13 08:03:02 121-My systemd[1]: Stopping Apt-Cacher NG software download proxy... Apr 13 08:03:02 121-My systemd[1]: apt-cacher-ng.service: Succeeded. Apr 13 08:03:02 121-My systemd[1]: Stopped Apt-Cacher NG software download proxy. Apr 13 08:03:02 121-My systemd[1]: apt-cacher-ng.service: Consumed 2.402s CPU time. Apr 13 08:03:02 121-My systemd[1]: Starting Apt-Cacher NG software download proxy... Apr 13 08:03:02 121-My systemd[1]: Started Apt-Cacher NG software download proxy. Apr 13 10:42:12 121-My apt-cacher-ng[391899]: [warn] Epoll ADD(1) on fd 13 failed. Old events were 0; read change was 1 (add); write change was 0 (none); close change was 0 (none): Bad file descriptor Apr 13 10:43:25 121-My apt-cacher-ng[391899]: [warn] Epoll ADD(1) on fd 13 failed. Old events were 0; read change was 1 (add); write change was 0 (none); close change was 0 (none): Bad file descriptor Apr 13 10:45:02 121-My systemd[1]: Stopping Apt-Cacher NG software download proxy... Apr 13 10:45:02 121-My systemd[1]: apt-cacher-ng.service: Succeeded. Apr 13 10:45:02 121-My systemd[1]: Stopped Apt-Cacher NG software download proxy. Apr 13 10:45:02 121-My systemd[1]: apt-cacher-ng.service: Consumed 56.112s CPU time. Apr 13 10:45:02 121-My systemd[1]: Starting Apt-Cacher NG software download proxy... Apr 13 10:45:02 121-My systemd[1]: Started Apt-Cacher NG software download proxy. Apr 13 11:36:26 121-My apt-cacher-ng[414217]: [warn] Epoll ADD(1) on fd 13 failed. Old events were 0; read change was 1 (add); write change was 0 (none); close change was 0 (none): Bad file descriptor Apr 13 11:39:02 121-My systemd[1]: Stopping Apt-Cacher NG software download proxy... Apr 13 11:39:02 121-My systemd[1]: apt-cacher-ng.service: Succeeded. Apr 13 11:39:02 121-My systemd[1]: Stopped Apt-Cacher NG software download proxy. Apr 13 11:39:02 121-My systemd[1]: apt-cacher-ng.service: Consumed 2min 47.837s CPU time. Apr 13 11:39:02 121-My systemd[1]: Starting Apt-Cacher NG software download proxy... Apr 13 11:39:02 121-My systemd[1]: Started Apt-Cacher NG software download proxy. > and also please set debug=7 in acng.conf or similar conf file. I did so an now I'm waiting for new errors. > If that's a crash, please install systemd-coredump service and we can > debug the corefiles later. > 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? Yes, there is an elderly squid upstream proxy: Proxy: http://user:pass@myProxy:8080 and I ReuseConnections: 0 These are tho only modifications of the config-file > > 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? I didn't install (or configure) it by hand, but obviously it is pulled in by $something in Bullseye: At least 'dpkg -i apparmor' says something like: ii apparmor 2.13.6-10 amd64 user-space parser utility for AppArmor un apparmor-profiles-extra <keine> <keine> (keine Beschreibung vorhanden) un apparmor-utils <keine> <keine> (keine Beschreibung vorhanden) > We can have an interactive Jitsi session if you prefer to get this > solved in realtime and it can be made reproducible somehow. Thanks for your offer. Actually I don't see a way to reproduce it by demand. I will have a look at the memory (memtest) and report the 'debug: 7' output in apt-cacher-ng.err Christian
