Today I upgraded the slave databases to a new major release of the database engine. I'd like to use some of the new features to increase the performance of the system.
The upgrade itself, and the necessary conversions, wouldn't have caused any outages, since I can tell my software to do queries on another database server while upgrading one (in fact, they will automatically fail over to another server if one is down). But, as usual, there was something I overlooked, and for a few minutes about 50% of the /info/ page requests failed and complained about problems with looking up nearby cities. I had to improve the stored procedures a bit to get them working on the new database engine version.
Please, drop a note in the blog comments, if you notice any other problems.
The news of https://aprs.fi/ - new features and interesting attractions found in the APRS and AIS worlds.
Hi, aprs.fi is a great tool and we apprecaite all the work you do for us..Is there a way to have a maiden head grid square over lay implimented ?
ReplyDelete73 Phillip ZL2TZE
Thanks. I'll put it on the to-do list, but cannot guarantee anything on the schedule, as I have a few other items on the list that are more urgent.
ReplyDeleteDon't know if this is really a new bug, but an oddity.
ReplyDeleteIf you look at the raw packets from http://aprs.fi/info/K6DBG-1, you can see that it is being heard and digi'd at a slow but regular rate. Yet the summary page says it has been heard by 0 sites... what's up with that?
Thanks for all your work!
73,
chris
Chris: The wording on the info page seems to be wrong. 17 packets have been received, but the "heard by" counters only take APRS position packets into account, and apparently all of the packets were status message packets. I should fix that somehow.
ReplyDelete