---KNOWN ISSUES---
Blue Steel Style (and perhaps a couple of others) are not working properly - http://www.okshooters.com/forum.php?styleid=8
Search is currently broken.
---PROGRESS UPDATES---
2012-11-10 2:22PM
Search is now working.
2012-11-10 12:57PM
Login issues should all be fixed. Working on fixing theming issues.
If you're seeing "Array" in a lot of places, go here: http://www.okshooters.com/forum.php?styleid=8
2012-11-10 8:08AM
So nothing went as planned. However, we did get upgraded to 4.2.0.
2012-11-09 7:40PM
Around 1PM today while I was partaking in my lunch, I got the final issues on the new webservers fixed. You have been using them since. If there was a hiccough, it's because they are still pointed to the old server's database.
At approximately 2AM, I will be migrating the database to the new servers. Additionally, an upgrade to the software will be attempted. This will result in 30-45 minutes of downtime. However, in case of unforeseen issues, I'm reserving a window from 2AM to 4AM for the migration and upgrade.
Thank you for your patience!
2012-11-06 1:52AM
And back on track - should be point back to the new load balancer. The world's DNS network sure is getting a workout with this one.
Issue: vBulletin doesn't process HTTP headers properly out of the box, and apparently hasn't since 2005. I should really note that core patch before actually doing the upgrade process.
I'll probably do the webservers later this week.
2012-11-06 12:34AM
Everyone should be pointing back on the old server. vBulletin didn't like having several hundred users from the same IP and was getting confused resulting in password failures that should not have been failures. Since the load balancer that was being used can't pass the source IP, we'll have to put up our own load balancer that can handle it.
2012-11-05 8:56PM
The transition process to the new hosting platform has already begun. In an effort to minimize the downtime associated directly with the transfer, the load balancer at the new place has been setup to use the old server as the backend. This has allowed us to go ahead and update the DNS to point to the new location with no interruption. (At this time, about a third of the traffic is going through the load balancer. I've actually be posting through it for a couple of weeks now to make sure it worked properly.)
A side effect of this setup may be some minor slowdowns during peak times as more users are going through the load balancer instead of directly to the current server. Those slowdowns will go away when the entire system is at the new location.
Once we're confident that the DNS records have adequately propagated and nearly all of the traffic is coming through the new load balancer, we'll switch the load balancer to use the new webservers. Depending on where we are in the upgrade process, we'll either still be making database hits on the current server or we might also migrate the database to the new cluster at the same time.
There should not be any downtime during the transition other than when the database is migrated and vBulletin is upgraded. The downtime goal for the database migration and vBulletin upgrade is 30 minutes total, but there will be a two-hour window reserved as planned downtime just in case. I'm not sure if those two events will happen together or at separate times.
The new hosting platform is a high-availability cluster and should rid us of the downtime issues and database crashes we've been having.
---PROGRESS UPDATES---
2012-11-10 2:22PM
Search is now working.
2012-11-10 12:57PM
Login issues should all be fixed. Working on fixing theming issues.
If you're seeing "Array" in a lot of places, go here: http://www.okshooters.com/forum.php?styleid=8
2012-11-10 8:08AM
So nothing went as planned. However, we did get upgraded to 4.2.0.
2012-11-09 7:40PM
Around 1PM today while I was partaking in my lunch, I got the final issues on the new webservers fixed. You have been using them since. If there was a hiccough, it's because they are still pointed to the old server's database.
At approximately 2AM, I will be migrating the database to the new servers. Additionally, an upgrade to the software will be attempted. This will result in 30-45 minutes of downtime. However, in case of unforeseen issues, I'm reserving a window from 2AM to 4AM for the migration and upgrade.
Thank you for your patience!
2012-11-06 1:52AM
And back on track - should be point back to the new load balancer. The world's DNS network sure is getting a workout with this one.
Issue: vBulletin doesn't process HTTP headers properly out of the box, and apparently hasn't since 2005. I should really note that core patch before actually doing the upgrade process.
I'll probably do the webservers later this week.
2012-11-06 12:34AM
Everyone should be pointing back on the old server. vBulletin didn't like having several hundred users from the same IP and was getting confused resulting in password failures that should not have been failures. Since the load balancer that was being used can't pass the source IP, we'll have to put up our own load balancer that can handle it.
2012-11-05 8:56PM
The transition process to the new hosting platform has already begun. In an effort to minimize the downtime associated directly with the transfer, the load balancer at the new place has been setup to use the old server as the backend. This has allowed us to go ahead and update the DNS to point to the new location with no interruption. (At this time, about a third of the traffic is going through the load balancer. I've actually be posting through it for a couple of weeks now to make sure it worked properly.)
A side effect of this setup may be some minor slowdowns during peak times as more users are going through the load balancer instead of directly to the current server. Those slowdowns will go away when the entire system is at the new location.
Once we're confident that the DNS records have adequately propagated and nearly all of the traffic is coming through the new load balancer, we'll switch the load balancer to use the new webservers. Depending on where we are in the upgrade process, we'll either still be making database hits on the current server or we might also migrate the database to the new cluster at the same time.
There should not be any downtime during the transition other than when the database is migrated and vBulletin is upgraded. The downtime goal for the database migration and vBulletin upgrade is 30 minutes total, but there will be a two-hour window reserved as planned downtime just in case. I'm not sure if those two events will happen together or at separate times.
The new hosting platform is a high-availability cluster and should rid us of the downtime issues and database crashes we've been having.
Last edited:
