@stefano I agree, it's certbot's behaviour that caused the issue in the end, not systemd doing a good job at system maintenance.

Monospace Mentor
@monospace@floss.social
Post
-
Spent my morning figuring out why Nginx was dead on a server with many days of uptime. -
Spent my morning figuring out why Nginx was dead on a server with many days of uptime.@stefano Wait, no, I see your point. I had to edit in "post-install restarts", and realized that systemd taking care of that is indeed something special. I will still put the blame on certbot for taking over port 80 even though instructed to use nginx. That should have resulted in a fatal error.
-
Spent my morning figuring out why Nginx was dead on a server with many days of uptime.@stefano To me, this is just a coincidence of two scheduled jobs (package upgrades and certificate renewal) running at the same time. Maybe I'm missing something, but port 80 being open to be taken over by certbot would have happened with a traditional cron job on any old Unix system just the same.
-
Spent my morning figuring out why Nginx was dead on a server with many days of uptime.@stefano I read this as a simple race condition for port 80, and can't see how this is an "only on Linux" thing.