Site went offline.
Root / Site Discussion / [.]
This is just going to happen sometimes. It's either our provider messing up or... something else.It hopefully isn't what I think it is...
I got a DoS protection check, a 502 Bad Gateway from cloudflare, and served a cached version of the site in that order. Not sure where the verdict is on that honestly.This is just going to happen sometimes. It's either our provider messing up or... something else.It hopefully isn't what I think it is...
Site is exploding for me. Errors everywhere (like the one at the site header: Warning: mysqli_stmt::bind_param(): invalid object or resource mysqli_stmt in /var/www/html/include/database.php on line 195 and that's just one of them). Certain pages appear not to exist to my browser (any page under one of the tabs at the top), but subpages work fine. I've had to navigate to this page using the URL alone (and that wasn't too fun).
Yeah, chat's broken too. Not good. Any idea what happened?
EDIT: I'm on the PTC Wikia Chat if anyone wants to chat.
And CloudFlare activated for a minute. Sweet.
I um... I think everything is fine now? I'm going to reboot one last time and see what happens. I'll give an explanation when everything appears to be fixed.I blame uo.
OK so here's what happened (for those who want to know).
Ubuntu has been nagging me lately to perform an upgrade to the newest version of Ubuntu. Whatever, I knew it would be a mess, so I ignored it.
However, I finally caved in today when aptitude tells me there's like 532 updates and I'm a bad person for not keeping up with security. Fine, whatever, let's upgrade and blow everything up.
Everything DID blow up. For starters, php5 is basically trash now and ubuntu is like "Nope, I ain't havin nonna that" and forced me to upgrade to php7. php5 doesn't even exist in the general package archives anymore. Now it's php7 and whatever, which completely broke all my configurations. I spent a long time just reconfiguring nginx to use php7, and even after all that, it was still broken. Nginx was still throwing 500 errors, which after research I found out was because php7 defaults to "hidden internal server error" rather than "dump error to html". Cool, something finally showed up on screen.
Oh, and I should mention that "service" is being fazed out in favor of "systemctl" apparently, so I had to go through and switch everything over to the new system. This meant reinstalling basically everything: Nginx, php, mysql, and all that crap AGAIN.
Next we have the whole "oh yeah, your mysql is garbage too, so we're upgrading that". More configuration woes, since the new standard is to ensure full grouping or whatever, which I totally don't currently do. Blah blah blah mysql was back up after a while.
Since php is all new and shiny, I had to go through and reinstall all the modules and crap that we use. Imagick luckily updated to php7 a few weeks ago (wow), so I was able to easily reinstall that. Also some math library and whatever other crap we had.
After a gazillion restarts and lots of old & bad configurations, we're finally back up with probably only a few errors... maybe. Distribution upgrades are always a mess and you need to make sure you know what you're getting into before you start. I knew what I was getting into, but I unfortunately got reamed on the upgrade... sometimes you're fine, and sometimes you get throat punched.
Wait until 16.10 comes out in October 0_oHell, what version of Ubuntu were you on? Ubuntu 1932?Nah dawg, I just updated from 16.04 to 16.04.1.
How exactly is there not a more direct upgrade path to 16.04.1? You would think the package base of the former would work just fine with the latter and vice-versa, right? Unless you managed to somehow have lots of massively out of date packages. I know the feeling though, having gone from Mint 17.3 (which used 14 as package base) to 18 (which uses 16.04.)Hell, what version of Ubuntu were you on? Ubuntu 1932?Nah dawg, I just updated from 16.04 to 16.04.1.
With Ubuntu, these LTS 0.0.X releases are called "point releases" that include all the bugfixes and whatever that they've accumulated. This is so that you don't HAVE to upgrade if you don't want to (because you already have a stable, working installation), but if you're a new adopter, you'll get all the latest crap without having to perform a massive package update. They're still pretty big updates though. The reason it was so nasty for us is because we have a LOT of custom garbage. If were were running some Wordpress installation on Apache, it probably wouldn't have been a problem at all. But we use nginx with some fast plugin version of php, so anytime PHP changes, I have to go through and hook it all up again. Not to mention all the extensions we have that aren't included in new installations of php (like image magick, the math libraries, mysqli, whatever). Our nginx configuration is a huge custom nightmare, what with trying to bypass cloudflare in order to open websocket connections for the chat, special rules for the development website, and all these url switcheroos. Plus, a big change was them switching how we control services, which screwed a bunch of stuff up. All in all, not one of my more fun updates lol.How exactly is there not a more direct upgrade path to 16.04.1? You would think the package base of the former would work just fine with the latter and vice-versa, right? Unless you managed to somehow have lots of massively out of date packages. I know the feeling though, having gone from Mint 17.3 (which used 14 as package base) to 18 (which uses 16.04.)Hell, what version of Ubuntu were you on? Ubuntu 1932?Nah dawg, I just updated from 16.04 to 16.04.1.