Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Macdeth
Ephemeral Misgivings
|
Posted - 2008.12.19 19:38:00 -
[1]
For the past three-ish days, the API server has been giving me an unnumbered 'General error' when accessing the corporate kill logs of corporations with recent kills.
Looks a lot like this:
<eveapi version="2"> <currentTime>2008-12-19 19:32:41</currentTime> <error> A general error has occured, please try again later. </error> <cachedUntil>2008-12-19 20:32:41</cachedUntil> </eveapi>
On corporations with less frequent kills, I've sometimes been able to get it to load by calling it an additional time or three manually, but for GoonFleet I don't think I've been able to pull the kill log successfully a single time in the past few days.
As a result, I'm thinking this is some manner of timeout error caused by recent API server changes. (Although maybe it's luck of the draw and certain servers are randomly working/broken)
Would appreciate it if this was looked into, and as a random aside it'd be nice if the <error> element had a "code=###" attribute of its own in order to conform with the rest of the API.
Posting thread since I've seen nobody else complain of this yet.
|
Macdeth
Ephemeral Misgivings
|
Posted - 2008.12.22 15:06:00 -
[2]
Bumping for Monday since I'm still getting regular failures on several corporations in each of my batch runs of a few dozen. I think the errors are ALWAYS on corporations with fresh new kills.
|
Dragonaire
Caldari Corax.
|
Posted - 2008.12.22 18:12:00 -
[3]
Something you might also check is if they are trying to run any other killboards or other API relate application that might be pulling the KillLog and interfering with what you're doing. The way the cache on the API works makes having more than one application using the same API problematic at best without them all using a proxy get around it. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. |
Captain Thunk
Captain Morgan Society
|
Posted - 2008.12.23 04:35:00 -
[4]
Other people are having this issue as well.
Another problem is that KillLog has become 'flakey' in recent weeks - for some, it's been returning victimID or corpID correctly but returning victimName="" or corpName="" instead of the correct translated value. I'm assuming this will be a low priority like the old allianceName garbled return bug (I don't actually know if that was ever fixed, never actually checked the XML since) and could take months to fix. Annoying for me as i need to doublecheck anything that isn't a direct ID and convert if necessary now.
Captain Thunk
|
Bloemkoolsaus
Horizon.Inc OPUS Alliance
|
Posted - 2008.12.23 14:19:00 -
[5]
Edited by: Bloemkoolsaus on 23/12/2008 14:20:04 I once had the same error with the killLog (almost a year ago now). I tracked the problem to that one of the kills was made by an NPC. At the time, the killmails made by NPC's were buggy. The killLog problem corrected itself, and i don't recall any issues after that but there were also no kills from NPC's in our corp since then.
I'm not sure if this has been fixed or not yet, but i think it's worth checking your kills for NPC kills :D
====================== Horizon.Inc http://www.horizon-inc.nl |
Macdeth
Ephemeral Misgivings
|
Posted - 2008.12.24 08:02:00 -
[6]
[center] Originally by: Bloemkoolsaus Edited by: Bloemkoolsaus on 23/12/2008 14:20:04 I once had the same error with the killLog (almost a year ago now). I tracked the problem to that one of the kills was made by an NPC. At the time, the killmails made by NPC's were buggy. The killLog problem corrected itself, and i don't recall any issues after that but there were also no kills from NPC's in our corp since then.
I'm not sure if this has been fixed or not yet, but i think it's worth checking your kills for NPC kills :D
I saw the NPC-related errors back in the day, and think I still get a few invalid kills where the involved parties include rogue drones, but the invalid kills may be my bug rather than CCP's - haven't followed up to investigate since occasional missed deaths to NPC's aren't a priority. These don't make the API server error out anyway.
Kill log hasn't really been erroring out as reliably as in the last week since mid-October.
Regarding the getName() call bugs, I had a bug report on the older problem get marked as fixed in recent memory but who knows.
|
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |