![]() In the coming days I'll be making a news post with a user satisfaction survey (it'll be short, don't worry) and a Discord invite link for Service and what would make extras/credits more appealing to users as well. S-ul is still very much alive though and still my baby, we've currently been thinking of ways we can improve the The reason for that is there's not much newsworthy going on behind the scenes, we're all still busy working on other projects mostly! ![]() This is something I don't really have an excuse for, I keep forgetting to automate this and get sidetracked ontoĪnother thing I wanted to address is the inactivity/lack of news. The fourth and reoccurring issue is our DNSSEC signatures expire monthly. It's something I'm still looking into fixing up automation wise but we're getting there! Nameservers and have roughly 7 servers in s-uls infrastructure. Generally LE can auto-renew, but wildcard LE certs require certain DNS updates every time, and as we host our own Usually I'm on top of this but it slipped by me this This is your standard "SSL cert expired whoops" kinda outage. Third most recent was caused by our SSL certificate expiring. and 7.1 had been uninstalled for 7.3, big brain moves right there. Why? Because the cronjob pointed to /usr/bin/php7.1 instead of /usr/bin/php This was similar to a previous outage where the s-ul file cache filled up and basically crumbled. Second most recent was caused by the PHP7.3 update. It looks like during the Buster upgrade however it's re-enabled it and as a result, users were presented with the However, we never removed the apache2 package from Nekomata we simply disabled the startup "just in case". Implication and apache not being able to keep up with the requests as a result this caused us to move to Previously our servers used to use Apache HTTPd to power s-ul, but very quickly once we grew, we started to see the Seems a more recent reboot caused Apache to come back up without us noticing. While the upgrade went fine, the server came back up after a reboot, kernel updated, PHP updated to 7.3 etc and was The most recent (yesterday) issue was caused by me testing the waters on one of our masters (Nekomata) in order to Apologies for the recent server issues/downtime, this should hopefully address it also sorry for the long ass post.
0 Comments
Leave a Reply. |