Root causing it is on my todo. For now I just commented the config in my user-data.sh
But systemd itself was setting the squid service into stop then start. I don’t think by that time systemd knew the reason was to do with logs.
Re:Avoiding Complexity with Systemd
by WesolyKubeczek on Sunday June 27, 2021 @05:47PM
(#27655765)
I'm wondering if this new config made squid exceed any limits, causing it to hard stop. I'd expect the log trimmer to have/cause a bug in squid itself.
I feel your pain - I'm curious, was it a drop-in /etc/logrotate.d/ config which was sending a HUP? I don't run squid but Google'd up that it will take a USR1 to rotate logs which should not close the HTTP connections (allegedly HUP closes them). Perhaps the AL2 folks chose the wrong signal? https://wiki.squid-cache.org/SquidFaq/InstallingSquid#squid_...