About 11 hours from now the bz.bzflag.bz computer will be down while it is physically moved to a new location. This computer hosts the forums you are currently reading, the general list of BZFlag game servers, global authentication, the Ducati League web site, and probably other important things.
The planned downtime is September 30 from 3:00 AM to 5:00 AM UTC. A time converter such as the one at http://www.timeanddate.com/worldclock/converter.html will help you convert that to your local time.
During this period you will be unable to read this forum, get the list of BZFlag game servers, or authenticate to a specific BZFlag server. Even if you already have the address of a server it may take several minutes to connect while authentication times out and fails.
"We apologize for the inconvenience."
List server downtime
- Bullet Catcher
- Captain
- Posts: 564
- Joined: Sat Dec 23, 2006 7:56 am
- Location: Escondido, California
Re: List server downtime
The wiki will be affected as well.
There is nothing worse than aggressive stupidity. -- Johann Wolfgang von Goethe
"How many legs does a dog have if you call his tail a leg? Four. Calling a tail a leg doesn't make it a leg." -- Abraham Lincoln
"How many legs does a dog have if you call his tail a leg? Four. Calling a tail a leg doesn't make it a leg." -- Abraham Lincoln
Re: List server downtime
In the client you can cache the list of servers and play with an unregistered callsign during the downtime except you have it locally registered of course. I write unregistered callsign because global authentication won't work until connection to the list server will work again.
- Bullet Catcher
- Captain
- Posts: 564
- Joined: Sat Dec 23, 2006 7:56 am
- Location: Escondido, California
Re: List server downtime
The hardware move is now complete and bz.bzflag.bz is up at its new IP address.
Unfortunately, the bzfs server code caches the old IP address forever, so public bzfs servers must be restarted once to get the new list server IP address. This problem has already been fixed in the development trunk.
Thanks to everyone for their patience.
Unfortunately, the bzfs server code caches the old IP address forever, so public bzfs servers must be restarted once to get the new list server IP address. This problem has already been fixed in the development trunk.
Thanks to everyone for their patience.