Jump to content

Flakey API


jholly
Followers 3

Recommended Posts

There have been lots of problems lately with API usage with GSAK.

It might help if you describe the problems you're seeing. "It doesn't work" is hard to troubleshoot.

 

FWIW, I haven't experienced a single problem with the API recently, whether through GSAK or the official iPhone app. Regarding DanPan's post about PQs, I just tried it and GSAK had no problems fetching the PQ list.

 

Edit to add: Also, I can't recall seeing any recent bug reports in this forum or the iPhone bug report forum, so any such problems don't seem to be widespread.

Edited by The A-Team
Link to comment

There have been lots of problems lately with API usage with GSAK.

It might help if you describe the problems you're seeing. "It doesn't work" is hard to troubleshoot.

 

FWIW, I haven't experienced a single problem with the API recently, whether through GSAK or the official iPhone app. Regarding DanPan's post about PQs, I just tried it and GSAK had no problems fetching the PQ list.

 

Edit to add: Also, I can't recall seeing any recent bug reports in this forum or the iPhone bug report forum, so any such problems don't seem to be widespread.

 

Flaky in that there are frequent 503 returns, returns with no results and the need for frequent retries to get results.

Link to comment

There have been lots of problems lately with API usage with GSAK.

It might help if you describe the problems you're seeing. "It doesn't work" is hard to troubleshoot.

 

FWIW, I haven't experienced a single problem with the API recently, whether through GSAK or the official iPhone app. Regarding DanPan's post about PQs, I just tried it and GSAK had no problems fetching the PQ list.

 

Edit to add: Also, I can't recall seeing any recent bug reports in this forum or the iPhone bug report forum, so any such problems don't seem to be widespread.

 

There's been a lot of talk on the GSAK forums. I most cases, the Groundspeak servers are simply not answering. In other cases, for "get geocaches", it's answering and indicating that everything is good, but it's sending an empty GPX file. This all started at about the same time as the website slow downs of the past few weeks.

Link to comment

I am getting 503 errors on my API calls also meaning there's a problem with the Geocaching API servers. I am wondering why there has not been any acknowledgement of these errors.

 

Only 4 out of my 5 PQs also ran and I can't reset the one so I am really pissed off at GS right now about these long going errors. I really need that PQ to run but it said it ran when it didn't run properly.

Link to comment

Howdy,

 

It seems there have been changes going on at GC.com. The api is seeming flakier. Also the pocket query from email address has changed.

 

I have been having problems with gsak and A:Drake using the api. gsak has trouble with the PQ files not being available when it goes to download them. Adrake is just unusable to find nearby caches.

 

Would it be possible for GC.com to post what information they want in bug reports so that the developers can be recording that for the users to submit? I imagine it includes IP addresses, times (UTC), all http traffic including headers, perhaps some API specific information as well.

 

If my apps are collecting this then they need to make it easier for me to report the issues.

 

Thanks

Link to comment

Today i did a "Refresh cache data" and got the message "Previous request ended in error, now doing a retry..."

 

The API does appear to be not as reliable as it was previously.

 

Are the API servers overloaded?

Edited by DanPan
Link to comment

Only GSAK's recently introduced retry mechanism is making the API usable at the moment. Even so, today has been the worst I've seen: almost every call fails at least once, some many times.

 

Even worse, every failed call still causes the cache count to be decremented. Refreshing 1500 caches has just used almost all of my daily quota :mad:.

 

Five days after this thread was started, it would be good to have a response from Groundspeak.

Link to comment

I am having trouble refreshing cache data in GSAK through the API. Here is the error message I am receiving:

 

ChilkatLog:

PostXml:

DllDate: Aug 5 2012

UnlockPrefix: GSAKNEHttp

Username: GORDONBOSLE8A6B:Owner

Architecture: Little Endian; 32-bit

Language: ActiveX

url: https://api.Groundspeak.com/LiveV6/Geocaching.svc/SearchForGeocaches

charset: utf-8

xmlSizeInChars: 3458

RegistryQueryError: The system cannot find the file specified.

ValueName: ProxyServer

Failed to get key value

valueName: ProxyServer

Failed to read registry: CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/Internet Settings/ProxyServer

httpConnect:

hostname: api.Groundspeak.com

port: 443

ssl: 1

Need to establish connection to the HTTP server...

RegistryQueryError: The system cannot find the file specified.

ValueName: ProxyServer

Failed to get key value

valueName: ProxyServer

Failed to read registry: CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/Internet Settings/ProxyServer

ConnectTimeoutMs_1: 45000

Multi-threaded hostname to IP address resolution

Resolving domain name (IPV4/IPV6)...

AddrInfoList:

AddrInfo:

ai_flags: 0

ai_family: 2

ai_socktype: 1

ai_protocol: 0

ai_addrlen: 16

ai_canonname: (NULL)

--AddrInfo

--AddrInfoList

Connecting to IPV4 address.

ipAddress2: 66.150.167.177

myIP_5: 10.211.55.3

myPort_5: 1545

connect successful (3)

clientHelloMajorMinorVersion: 3.1

buildClientHello:

majorVersion: 3

minorVersion: 1

numRandomBytes: 32

sessionIdSize: 0

numCipherSuites: 10

numCompressionMethods: 1

--buildClientHello

handshakeMessageType: ServerHello

handshakeMessageLen: 0x46

processHandshakeMessage:

MessageType: ServerHello

Processing ServerHello...

ServerHello:

MajorVersion: 3

MinorVersion: 1

SessionIdLen: 32

CipherSuite: RSA_WITH_RC4_128_SHA

CipherSuite: 00,05

CompressionMethod: 0

Queueing ServerHello message.

ServerHello is OK.

--ServerHello

--processHandshakeMessage

HandshakeQueue:

MessageType: ServerHello

--HandshakeQueue

Dequeued ServerHello message.

handshakeMessageType: Certificate

handshakeMessageLen: 0xdda

processHandshakeMessage:

MessageType: Certificate

ProcessCertificates:

Certificate:

derSize: 1266

certSubjectCN: api.Groundspeak.com

certSerial: 35D2CA3BBBED67F0DD0C2853AA1C06C6

certIssuerCN: Thawte DV SSL CA

--Certificate

Certificate:

derSize: 1171

certSubjectCN: Thawte DV SSL CA

certSerial: 7610128A17B682BB3A1F9D1A9A35C092

certIssuerCN: thawte Primary Root CA

--Certificate

Certificate:

derSize: 1097

certSubjectCN: thawte Primary Root CA

certSerial: 3365500879AD73E230B9E01D0D7FAC91

certIssuerCN: Thawte Premium Server CA

--Certificate

NumCertificates: 3

Queueing Certificates message...

--ProcessCertificates

--processHandshakeMessage

Dequeued Certificate message.

handshakeMessageType: ServerHelloDone

handshakeMessageLen: 0x0

processHandshakeMessage:

MessageType: ServerHelloDone

Queueing HelloDone message.

--processHandshakeMessage

DequeuedMessageType: ServerHelloDone

OK to ServerHelloDone!

No client certificate required by the server.

Encrypted pre-master secret with server certificate RSA public key is OK.

Sending ClientKeyExchange...

Sent ClientKeyExchange message.

Sending ChangeCipherSpec...

Sent ChangeCipherSpec message.

Derived keys.

Installed new outgoing security params.

Sending FINISHED message..

algorithm: arc4

keyLength: 128

Sent FINISHED message..

ccsProtocolType: 1

handshakeMessageType: HandshakeFinished

handshakeMessageLen: 0xc

processHandshakeMessage:

MessageType: HandshakeFinished

FinishedMsgLen: 12

Queueing Finished message.

--processHandshakeMessage

Dequeue the FINISHED message...

Dequeued Finished message.

Handshake completed successfully.

Secure Channel Established.

Connected

--httpConnect

connectTime1: Elapsed time: 328 millisec

sendRequestGetResponse_1:

Auto-adding any accumulated cookies.

CookieDir: memory

CookieDomain: api.Groundspeak.com

CookiePath: /LiveV6/Geocaching.svc/SearchForGeocaches

LoadCookieJar:

Path: /LiveV6/Geocaching.svc/SearchForGeocaches

GetDomainCookiesXml:

CookieDir: memory

Domain: api.Groundspeak.com

HashKey: groundspeak_com.xml

No cookies exist yet.

--GetDomainCookiesXml

--LoadCookieJar

No cookie jar found.

RegistryQueryError: The system cannot find the file specified.

ValueName: ProxyServer

Failed to get key value

valueName: ProxyServer

Failed to read registry: CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/Internet Settings/ProxyServer

sendRequestTime: Elapsed time: 0 millisec

---- Reading HTTP Response ----

sslReceiveBytes:

Timeout waiting to read socket or accept connection

timeoutMs: 45000

Timed out waiting for incoming SSL/TLS messages.

timeoutMs: 45000

Failed to read SSL/TLS application messages.

--sslReceiveBytes

Failed to get response header on SSL connection.

Use the SessionLogFilename property to log the HTTP traffic to a file to examime the response.

readResponseTime: Elapsed time: 46890 millisec

--sendRequestGetResponse_1

PostXml request failed.

--PostXml

--ChilkatLog

Link to comment

Shouldn't you be posting your GSAK apilogs to the GSAK forum? It's of no use to anyone at Groundspeak.

 

Huh? apilogs are the client side view of the conversation between the Groundspeak servers and the GSAK clients. It would seem to me that they are of use to Groundspeak. If they are not then Groundspeak should help define what they contain.

 

Think of it as ordering a pizza and it arrives with the wrong topping. The pizza guy could say "It left here with the right topping". You respond showing the pizza. He says, "That is not what our log said and that record is not useful to us."

Link to comment

Shouldn't you be posting your GSAK apilogs to the GSAK forum? It's of no use to anyone at Groundspeak.

 

Huh? apilogs are the client side view of the conversation between the Groundspeak servers and the GSAK clients. It would seem to me that they are of use to Groundspeak. If they are not then Groundspeak should help define what they contain.

 

Think of it as ordering a pizza and it arrives with the wrong topping. The pizza guy could say "It left here with the right topping". You respond showing the pizza. He says, "That is not what our log said and that record is not useful to us."

 

To be honest, I don't know how much help it can or can't be to Groundspeak, but considering that they are likely to not even read it, I see no point in posting it.

 

The purpose of the GSAK apilog is to help GSAK's developer analyze problems that his program is having communicating with the api. If he had posted this in the GSAK forum, he more than likely would have had an answer, and possibly a solution within a few hours.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Followers 3
×
×
  • Create New...