Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
insidious Evils
East Khanid Trading Khanid Trade Syndicate
0
|
Posted - 2015.01.12 21:08:17 -
[1] - Quote
Hi all.
I am getting random illegal page requests 221, check the key access..... However, running the query manually works fine. I am mainly getting this error for starbase details, however i got it for corp contracts today as well. I thought it might be a flood issue, but i put a 1 second sleep between pulls to ensure that i am waiting and i am still getting them. The errors are random, not normally the same calls so its not the same towers for example with starbase details. I am obeying cache timers and data is pulled as soon as the timer expires. The script runs every 5 mins. Out of all of the calls in a 24 hour person i am getting about 6-8 errors, which is also pretty random, meaning 97% of the time the call works.......
Anyone else getting this and can shad some light.
cheer evils |
salacious necrosis
Federal Defense Union Gallente Federation
7
|
Posted - 2015.01.12 23:01:03 -
[2] - Quote
I haven't asked WHY this happens, but I see the same thing. Some days I see zero errors, other days I see a handful. My site makes ALL of the available API calls, but I only make them once every 20 minutes, so I may be seeing a different pattern than you. It's hard at the moment for me to get comparable stats as some of the accounts on my site have let their keys expiry. However, on the accounts I control, I only see a handful of these (for calls which should normally work).
So...you're not crazy :)
EveKit - your EVE data on the web!
|
Ydnari
Estrale Frontiers Project Wildfire
397
|
Posted - 2015.01.12 23:47:23 -
[3] - Quote
It's done it for months, even with proper rate limiting and everything.
https://forums.eveonline.com/default.aspx?g=posts&t=331824 https://forums.eveonline.com/default.aspx?g=posts&t=357617
I no longer trust the 221 error, particularly since phealng does a pretty solid job of validating permissions up front so it's very unlikely to be a genuine 221 (someone would have had to have changed key permissions and a request made in the period when the key info is still cached - not a very big window).
So I treat 221 as a transient failure, ignore the cache timer and retry in 1 hour instead of the 24 hours it says - this pretty much always works, since it's always this false failure, whilst still slowing down since clearly something in the API is broken.
I've got 81 occurrences of this in my logs since 2014-12-18.
my teapot is ready
|
Smallevils
Association of Commonwealth Enterprises Nulli Secunda
2
|
Posted - 2015.01.14 11:30:45 -
[4] - Quote
Hi guys.
Thanks for your replies.
I will continue to log these errors but will pretty much ignore them. As they are fairly rare, and my calls are generally not time sensitive i can live with the odd missed update due to the 221s. Hopefully Foxfour is aware of this and a fix will appear in due course.
again, thanks for your assistance.
Evils |
qu1ckkkk
The Warp Core Stabilizers Tactical Narcotics Team
10
|
Posted - 2015.01.14 15:55:31 -
[5] - Quote
Be careful if you start to make large volumes of calls. Even though these 221's are occurring for ~reasons~, they still count towards your error threshold and will get your IP temp/perma banned if they happen too often. I have seen a number of cases with very large SeAT installs reporting this behavior.
Proud developer of SeAT: A Simple Eve API & Corporation Management Tool
http://eve-seat.github.io
|
Ydnari
Estrale Frontiers Project Wildfire
400
|
Posted - 2015.03.29 16:31:04 -
[6] - Quote
It's still doing this, seems to be increasing in frequency recently according to my logs - I've had 109 today! Which is up considerably.
Last dev message I can find on the subject is: https://forums.eveonline.com/default.aspx?g=posts&m=4793555#post4793555 but it's been doing it since the year 2013.
Any news on causes, reasons, fixes?
my teapot is ready
|
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |