I searched all the logs I could find for wget. Then I found “wget” in /var/log/foreman-proxy/proxy.log:
2020-05-15T11:56:54 229f1c45 [D] Starting task: /usr/bin/wget --connect-timeout=10 --dns-timeout=10 --read-timeout=60 --tries=3 --no-check-certificate -nv -c “http://ftp.debian.org/debian/dists/buster/main/installer-amd64/current/images/netboot/debian-installer/amd64/linux” -O “/srv/tftp/boot/debian-mirror-eZTy0v5ew0jk-linux”
2020-05-15T11:56:54 229f1c45 [D] Starting task: /usr/bin/wget --connect-timeout=10 --dns-timeout=10 --read-timeout=60 --tries=3 --no-check-certificate -nv -c “http://ftp.debian.org/debian/dists/buster/main/installer-amd64/current/images/netboot/debian-installer/amd64/initrd.gz” -O “/srv/tftp/boot/debian-mirror-eZTy0v5ew0jk-initrd.gz”
2020-05-15T11:56:57 2e04c71c [D] Starting task: /usr/bin/wget --connect-timeout=10 --dns-timeout=10 --read-timeout=60 --tries=3 --no-check-certificate -nv -c “http://ftp.debian.org/debian/dists/buster/main/installer-amd64/current/images/netboot/debian-installer/amd64/linux” -O “/srv/tftp/boot/debian-mirror-eZTy0v5ew0jk-linux”
2020-05-15T11:56:57 2e04c71c [D] Starting task: /usr/bin/wget --connect-timeout=10 --dns-timeout=10 --read-timeout=60 --tries=3 --no-check-certificate -nv -c “http://ftp.debian.org/debian/dists/buster/main/installer-amd64/current/images/netboot/debian-installer/amd64/initrd.gz” -O “/srv/tftp/boot/debian-mirror-eZTy0v5ew0jk-initrd.gz”
This was about an hour ago. Seems that there is some cron job or similar, which did that (I was afk the last hour). Now there are two more files in /srv/tftp/boot/:
debian-mirror-eZTy0v5ew0jk-initrd.gz
debian-mirror-eZTy0v5ew0jk-linux
I will try to provision a host as soon as I made progress with this: Creating discovered hosts is not working
To be honest, I am kind of surprised regarding the development of this topic. I had a similar experience before (Tasks is no longer working after update - #8 by kiigass). On one hand it is nice, that foreman is kind of “self-repairing” on the other hand I would have liked to know what the issue is and how to solve it, if it comes back.
This is the whole /var/log/foreman-proxy/proxy.log (70.5 KB)