Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dynect APIs throw "login: There was a problem with your credentials" errors from time to time #106

Closed
allenxwang opened this issue Mar 27, 2013 · 1 comment

Comments

@allenxwang
Copy link
Contributor

Once a while I observe this type of error if I keep using Dynect APIs from my application. Usually a restart will fix it.

org.jclouds.http.HttpResponseException: command: GET https://api2.dynect.net/REST/Zone HTTP/1.1 failed with response: HTTP/1.1 400 Bad Request; content: [{"status": "failure", "data": {}, "job_id": 305900967, "msgs": [{"INFO": "login: IP address does not match current session", "SOURCE": "BLL", "ERR_CD": "INVALID_DATA", "LVL": "ERROR"}, {"INFO": "login: There was a problem with your credentials", "SOURCE": "BLL", "ERR_CD": null, "LVL": "INFO"}]}]
at org.jclouds.dynect.v3.handlers.DynECTErrorHandler.handleError(DynECTErrorHandler.java:45)
at org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:69)
at org.jclouds.http.internal.BaseHttpCommandExecutorService.shouldContinue(BaseHttpCommandExecutorService.java:182)
at org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:152)
at org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:131)
at org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:97)
at org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:59)
at org.jclouds.reflect.FunctionalReflection$FunctionalInvocationHandler.handleInvocation(FunctionalReflection.java:119)
at com.google.common.reflect.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:70)
at com.sun.proxy.$Proxy95.list(Unknown Source)
at denominator.dynect.DynECTZoneApi.list(DynECTZoneApi.java:19)

org.jclouds.http.HttpResponseException: command: GET https://api2.dynect.net/REST/TXTRecord/allen.com./test.allen.com. HTTP/1.1 failed with response: HTTP/1.1 400 Bad Request; content: [{"status": "failure", "data": {}, "job_id": 305897866, "msgs": [{"INFO": "login: IP address does not match current session", "SOURCE": "BLL", "ERR_CD": "INVALID_DATA", "LVL": "ERROR"}, {"INFO": "login: There was a problem with your credentials", "SOURCE": "BLL", "ERR_CD": null, "LVL": "INFO"}]}]
at org.jclouds.dynect.v3.handlers.DynECTErrorHandler.handleError(DynECTErrorHandler.java:45)
at org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:69)
at org.jclouds.http.internal.BaseHttpCommandExecutorService.shouldContinue(BaseHttpCommandExecutorService.java:182)
at org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:152)
at org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:131)
at org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:97)
at org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:59)
at org.jclouds.reflect.FunctionalReflection$FunctionalInvocationHandler.handleInvocation(FunctionalReflection.java:119)
at com.google.common.reflect.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:70)
at com.sun.proxy.$Proxy146.listByFQDNAndType(Unknown Source)
at denominator.dynect.DynECTResourceRecordSetApi.exisingRecordIdsByNameAndType(DynECTResourceRecordSetApi.java:237)
at denominator.dynect.DynECTResourceRecordSetApi.existingRecordsByNameAndType(DynECTResourceRecordSetApi.java:184)
at denominator.dynect.DynECTResourceRecordSetApi.replace(DynECTResourceRecordSetApi.java:158)

@codefromthecrypt
Copy link
Contributor

Looks like over zealous ip matching on their sessions. Ive notice this
happen when running from a host that has ptr for both ipv4 and ipv6.

We can add an exception handler to relogin or retry on this error. I'll
work on it next week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants