AH API and error 500

Fuitad	wysłany: 14 lat temu Me and Ujournal have noticed a huge amount of error 500 being returned by the AH API. It appears to be mostly the same realms that always error out. I figure this is a known issue but just in case, here's the list: Aerie Peak Altar of Storms Alterac Mountains Andorhal Anetheron Anvilmar Archimonde Arygos Black Dragonflight Blackwing Lair Dalaran Dalvengyr Deathwing Demon Soul Dentarg Doomhammer Duskwood Executus Gnomeregan Haomarush Icecrown Jaedenar Kel'Thuzad Khadgar Lethon Mal'Ganis Norgannon Onyxia Scilla Sentinels Steamwheedle Cartel Tanaris The Venture Co Thrall Turalyon Uldaman Undermine Ysera Ysondre Zuluhed
Osundir	wysłany: 14 lat temu 1> The original reported issue was also affecting the Remote AH and was resolved yesterday (Though I'll be following up with the developers responsible for the AH as to why it caused 500s on these - I would have expected the worst behavior on the API to be that the data didn't update). 2> As noted elsewhere in the thread - the dump URL format is being changed to correct the issue with the EU Russian realms (If its not rolled out to EU by now it will be shortly) - if you have been following the API documentation, you should always be asking the API for what this exact URL is, for EXACTLY this reason.
Korigus	wysłany: 14 lat temu Greetings, The current issue causing the 500 error on the /api/wow/auction/ requests should be resolved for any US/EU realms experiencing this. All auction house data dumps should be updating like normal now. As part of this investigation, we have also planned to make a few upgrades which made lead to a brief period of where realm data may appear "temporarily unavailable". Any downtime from this should be very minimal and completed within a day or two.
Korigus	wysłany: 14 lat temu The previous stability updates should be finished at this point. The major 500s were while we were making the updates for EU, however it took somewhat longer than expected. As part of a separate investigation, there is a unrelated unique case specific to EU-Galakrond that we discovered. We'll look at getting out a possible fix for that shortly. That .tmp file entry is invalid and should be ignored -- It should disappear during the next refresh of the data. The real reason for multiple files in that list is if there are multiple snapshots available at the same time (in which case you can pick the most recent snapshot if you only want the current one).
Korigus	wysłany: 14 lat temu Thank you very much for your updates :). They are very appreciated. Regarding your third answer. Does this mean that when multiple files are provided, we can safely assume that a snapshop won't be split in two different files and that multiple files will only mean that they are different and complete? Yes, each file should always be a complete snapshot. This mechanism exists just in case we allow previous snapshots to exist beyond the next data refresh. We do not have any current plans to adjust the current deletion policy, but feel free to add support for this scenario if you would like.
Korigus	wysłany: 14 lat temu The issue with EU-Galakrond should also be fixed now: http://eu.battle.net/api/wow/auction/data/galakrond (no longer giving 500 errors) { "files":[ { "url":"http://eu.battle.net/auction-data/6a60b6f02d575a8f3aa64e065f23be00/auctions.json", "lastModified":1323915445000 } ] }