We're about 90% done with the migration to the new server platform now. Everything is installed and running except for some "minor" parts of the admin interface (like reports... because, well, you don't need to be running reports on a Saturday anyway). Chat, webchat, queues, gateways, and all the features you need to staff a service are all good.
But, we felt that we should post to explain some strangeness you might be seeing. It's possible to be logged in and see your gateways online, but a user visiting your web page might not see your widget, or might get notice that you're offline.
You see, what is going on right now is that there are two distinct libraryh3lp servers, the old and the new. Both are working, but they are not talking to each other. (The old server will not be part of the cluster, it's just going away.) So, if you're logged into one server and your user is on another, you'll miss each other. Which server you are logged into is just an accident of DNS caching. If you logged in early this morning before we threw the switch, your machine is talking to the old server, and no amount of logging out and in again will get it to talk to the new server, because of caching.
The way to fix this is to just log out of libraryh3lp at the end of your shift, forget about it, go home, and your computer will load the new values from the DNS servers tomorrow morning. It's that easy, it's just not immediate.
So that's where we stand right now. Because the new server is looking good, we'll be shutting down the old one sometime tonight, and once the DNS changes have had time to propagate throughout the internet, we'll all be running on the new server.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment