These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE Technology Lab

 
  • Topic is locked indefinitely.
12Next page
 

Issues with KillLog.xml.aspx
Author
Previous Topic Next Topic
Zylinda
Deep Core Mining Inc.
Caldari State
#1 - 2012-04-02 13:33:09 UTC
I'm using PHP to retrieve data via the Eve API. Whilst most of the pages work as expected, I'm having issues pertaining to the kill log.

When I do a FIRST call to "KillLog.xml.aspx", I get an expected response, with kill details.
However, if I call the same page subsequently, I get:

"Eve API" wrote:
< eveapi version="2" >
< currentTime >2012-04-02 13:21:31< /currentTime >
< error code="119" >
Kill log exhausted (You can only fetch kills that are less than a month old): New kills will be accessible at: 2012-04-02 14:17:09. If you are not expecting this message it is possible that some other application is using this key!
< /error >
< cachedUntil >2012-04-02 14:17:09< /cachedUntil >
< /eveapi >


I've tried using the optional parameter "beforeKillID" (with both valid and text values) but this doesn't appear to do anything (that I can make work)

Does this call 'empty' the kill log list? Is there not a way to retrieve the data again? (ie if a fault occured?)
Khorkrak
KarmaFleet
Goonswarm Federation
#2 - 2012-04-02 14:55:57 UTC  |  Edited by: Khorkrak
Good question as I was experiencing the same thing. I ended up deleting the key I was using and I created a new one. Worked fine right away. Before doing that though I'd tried waiting a few times until after the date and time specified in the error message to retry but always received that weird error message.

What's this beforeKillID parameter? Something related to the EDK Killboard IDfeed? This will just be ignored by the EVE API if so.

Developer of http://www.decloaked.com and http://sourceforge.net/projects/pykb/
Zylinda
Deep Core Mining Inc.
Caldari State
#3 - 2012-04-02 17:28:30 UTC
It's the one listed on the http://wiki.eve-id.net site here:
http://wiki.eve-id.net/APIv2_Char_KillLog_XML

I've tried using different keys, but each time it just lets it be called once, then shows the error message any time after.
Artemus Black
Doomheim
#4 - 2012-04-03 20:57:50 UTC
I'd like to know the answer to this one!
Khorkrak
KarmaFleet
Goonswarm Federation
#5 - 2012-04-03 21:18:37 UTC
Yep same nonsense for me - even with different keys. I don't understand this.

Developer of http://www.decloaked.com and http://sourceforge.net/projects/pykb/
Equto
Imperium Technologies
Sigma Grindset
#6 - 2012-04-03 21:38:32 UTC
I have been wondering the same thing.
Zylinda
Deep Core Mining Inc.
Caldari State
#7 - 2012-04-04 15:10:38 UTC
After a bit of playing, I'm pretty sure this API is bugged as it certainly acts differently from all the other calls.

With any given key, when you make a first call to KillLog.xml.aspx, it will give you a list of the previous kills. It says up to a month, but if there aren't many kills, it will actually go back a LOT further than that, so perhaps it is actually just a max number of kills it returns.

After that, the call just returns an error message, even with the optional beforeKillID parameter

However, one hour later, the call will again return the full list of kills, once, before returning an error again.

Really irritating!
Dragonaire
Here there be Dragons
#8 - 2012-04-04 15:36:02 UTC
Zylinda wrote:
After a bit of playing, I'm pretty sure this API is bugged as it certainly acts differently from all the other calls.

With any given key, when you make a first call to KillLog.xml.aspx, it will give you a list of the previous kills. It says up to a month, but if there aren't many kills, it will actually go back a LOT further than that, so perhaps it is actually just a max number of kills it returns.

After that, the call just returns an error message, even with the optional beforeKillID parameter

However, one hour later, the call will again return the full list of kills, once, before returning an error again.

Really irritating!
In other words it's work exact like it is suppose to and you are ignoring the cachedUntil timer. CCP has changed some of the APIs to allow you to re-get the last data on some APIs but just because they sometimes allow it on some APIs doesn't mean you should expect to on them all. I know it can be confusing when they mess up the cachedUntil time they return in the returned data for new developers but you really need to obey the expected cache times which for killLogs is 1 hour. The problem with bad cachedUntil times in the XML finally drove me to using currentTime and a DB table to figure out the correct time myself in Yapeal. You can find the intervals in the utilCachedInterval table now from Yapeal.

Finds camping stations from the inside much easier. Designer of Yapeal for the Eve API. Check out the Yapeal PHP API Library thread.
Etil DeLaFuente
Aliastra
Gallente Federation
#9 - 2012-04-06 01:50:18 UTC
I find it quiet annoying too,

if a third party already called the api with another key, you won't get the kills.

I can understand the need to reduce the load on ccp servers however, that behavior should be applied per key.
Desmont McCallock
#10 - 2012-04-06 06:00:48 UTC
Same things goes for the ContractBids API call. Although I have reported it and mentioned it directly to CCP staff via irc channel, no action has been taken yet. That design patterns has many defects. CCP won't realize that and won't do nothing until this becomes an outcry.

I can only think of one solution: Jita protest.
Etil DeLaFuente
Aliastra
Gallente Federation
#11 - 2012-04-06 14:42:34 UTC  |  Edited by: Etil DeLaFuente
Desmont McCallock wrote:
I can only think of one solution: Jita protest.


Let's start with petition first
Desmont McCallock
#12 - 2012-04-06 17:11:14 UTC
Etil DeLaFuente wrote:
Desmont McCallock wrote:
I can only think of one solution: Jita protest.


Let's start with petition first


Good luck with that. Twisted
Ydnari
Estrale Frontiers
#13 - 2012-04-06 19:34:20 UTC
Etil DeLaFuente wrote:
I find it quiet annoying too,

if a third party already called the api with another key, you won't get the kills.

I can understand the need to reduce the load on ccp servers however, that behavior should be applied per key.



AARGH

Suspected that might be why I never get any kills showing up on one key, this just confirms it.

Makes a mockery of the error message since that says it's per key not per account...

--
Etil DeLaFuente
Aliastra
Gallente Federation
#14 - 2012-04-07 05:22:16 UTC
Petition sent, let's see how long it takes to get a response :)
Etil DeLaFuente
Aliastra
Gallente Federation
#15 - 2012-04-10 02:14:08 UTC
You can only use one key per account.

So, if multiple third parties need to access the killlog, you have to provide a different key from a different account each time.
Desmont McCallock
#16 - 2012-04-10 06:13:28 UTC
That sucks. Diff key I understand. But why diff account? (rhetorical question)
Milo Caman
Anshar Incorporated
#17 - 2012-05-17 18:18:49 UTC
Bit of a Necro, but has anyone managed to resolve this?

If not, can you seriously not have multiple corporate keys pulling kills to different places? (I.E. Key for EVE-Kill, Key for personal Killboard)
Artctura
SUNDERING
Goonswarm Federation
#18 - 2012-05-25 19:53:07 UTC
This is seriously, one of the things that amazes me was not fixed with the new API system. I can't think of a reason why this isn't technologically simple, but it is an absolute pain when your trying to keep track of multiple director API's for a kill board. I need to watch logs, stagger pull times and do all sorts of other stuff because this is a "BY CHARACTER" issue.

I can understand it being by key, I can't understand it being by character. It's almost as if someone put the wrong field in the code somewhere.

Artctura for CSM 2013
Desmont McCallock
#19 - 2012-05-25 20:42:32 UTC  |  Edited by: Desmont McCallock
And this is the reason why EVEMon can't have a Kill Reports monitor.
It's been two expansions now and I feel so neglected.
Khorkrak
KarmaFleet
Goonswarm Federation
#20 - 2012-05-26 16:47:50 UTC  |  Edited by: Khorkrak
This is pathetic on CCP's part. Along with the 1 month / 100 kill mails limit. What?! Great so only old sites get a monopoly on verified kills. Come on... The coupe de grace is the complete absence of a way to even dump your own combat log to a file from the client.

Developer of http://www.decloaked.com and http://sourceforge.net/projects/pykb/
12Next page