Database trouble on February 12th, 2020

18:18Z

We are currently experiencing some major weirdness with our database server. The issue is being investigated.

18:29Z

It has become apparent that something has gone very wrong with a recent database update done earlier today. The database is showing all airports as either "very old" or "to be included in future X-plane -release". Seeking a way to remedy the situation.

20:26Z

Turns out, this whole shenanigans with the database server is caused by ... "human error". One of the cache files that are used during the airport update was disabled during the database update mentioned above. This disabled cache file was supposed to track when a specific gateway airport was included and when it actually got released with some version of X-Plane.

Because of this, the data needs to be re-evaluated from the source data. This will take a while - unfortunately we can't just roll back to the old database contents.

At the time of writing, the update script is at ~37% of rebuilding the database. However ... until the update script hits 100%, the online database will not be updated ... because of this, site users are only seeing a single airport (which normally is not included on the site) at the moment.

20:52Z

At the time of writing, the update script is at ~45% of rebuilding the database.

LEGO

Regarding the only airport visible on the map at the moment, it is the one holding the available prefabricated Lego Bricks modules for Gateway scenery developers. If you don't know about them yet ... you should check them out.

And if You like our content, don't forget to subscribe to the channel and beat the heck out of that bell icon to ... no, wait ... this isn't a Youtube channel :) ... If you're a gateway artist and don't yet know about the "lego blocks", check out the link above and peruse the newfound knowledge to your liking.

23:07Z

At the time of writing, the update script is at ~80% of rebuilding the database.

23:30Z

At the time of writing, the update script is at ~96% of rebuilding the database.

23:40Z

The situation is normalizing... ;)

23:55Z

The situation has normalized.

In case you're interested, for each airport, it seems to take about 540ms for our backend system to

Naturally - if we knew that "nothing has changed", we could have had skipped quite a many of these steps. But since this time we didn't, we needed to "take the long route" to get "everything" on the same level playing field.


Other bulletins...

OLDER