Amazingly one of the characters said he knows how horrible content becomes when it is open to just anyone. Well we got angelfire and tripod today to do just that.
I don’t really remember the tech stack, but it was something like 10-15 web servers, probably pentium II or III.
One detail I do remember is the original setup had an Apache log rotation script that would try several times to restart Apache and if it didn’t succeed, it would reboot the server. This ran nightly...
Not sure what bug or issue they were working around. But I thought it was quite an aggressive solution!
"oh, we forgot the print. lets retry tonight."
"darn, did not happen. lets leave this part in our infra for now until we trigger the edgecase again."
5 weeks (or days...) later: "damn, why did we do that again? better not touch it"
i love it when i find myself cargo culting code like that and finally have the time (and courage) to remove it :)
What’s your log rotation code look like?
What I meant was you should be using pipes and apaches own log rotate code.
Read the “Logging Using Pipes” section at the very end.
https://www.digitalocean.com/community/tutorials/how-to-conf...
(Excuse the DO link, it was just the first result in Duck Duck Go. There’s nothing specific about DO or Ubuntu in this approach)
I’ve used this method on large clusters of very heavily utilised web servers and it works great. No restarts required.
The '90s were definitely a time!