{"action":"created","issue":{"url":"https://api.github.com/repos/awslabs/dynamodb-document-js-sdk/issues/27","labels_url":"https://api.github.com/repos/awslabs/dynamodb-document-js-sdk/issues/27/labels{/name}","comments_url":"https://api.github.com/repos/awslabs/dynamodb-document-js-sdk/issues/27/comments","events_url":"https://api.github.com/repos/awslabs/dynamodb-document-js-sdk/issues/27/events","html_url":"https://github.com/awslabs/dynamodb-document-js-sdk/issues/27","id":63262005,"number":27,"title":"Network Errors Being Reported Incorrectly?","user":{"login":"rickwaugh1","id":4514070,"avatar_url":"https://avatars.githubusercontent.com/u/4514070?v=3","gravatar_id":"","url":"https://api.github.com/users/rickwaugh1","html_url":"https://github.com/rickwaugh1","followers_url":"https://api.github.com/users/rickwaugh1/followers","following_url":"https://api.github.com/users/rickwaugh1/following{/other_user}","gists_url":"https://api.github.com/users/rickwaugh1/gists{/gist_id}","starred_url":"https://api.github.com/users/rickwaugh1/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rickwaugh1/subscriptions","organizations_url":"https://api.github.com/users/rickwaugh1/orgs","repos_url":"https://api.github.com/users/rickwaugh1/repos","events_url":"https://api.github.com/users/rickwaugh1/events{/privacy}","received_events_url":"https://api.github.com/users/rickwaugh1/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-03-20T16:45:29Z","updated_at":"2015-03-20T21:36:45Z","closed_at":null,"body":"I have now twice run into problems using this library, once during load testing, once in production with a very lightly used app, where it reports that the dynamo end point is not found, and the service may not be available in that region.\r\n\r\nIs this a spurious error? I find it hard to believe that I can't get at Dynamo from an EC2 instance running in the same region. There were no errors reported from Dynamo, no throttled requests, no reports of having gone over capacity. So, I'm at a loss to explain why the following would turn up. The message comes from an event listener set up in the event_listeners.js file, in the lib directory.\r\n\r\n{\"level\":\"error\",\"message\":\"{\\\"message\\\":\\\"Inaccessible host: `dynamodb.us-west-2.amazonaws.com'. This service may not be available in the `us-west-2' region.\\\",\\\"stack\\\":\\\"UnknownEndpoint: Inaccessible host: `dynamodb.us-west-2.amazonaws.com'. This service may not be available in the `us-west-2' region.\\\\n    at Request.ENOTFOUND_ERROR (/var/app/current/node_modules/aws-sdk/lib/event_listeners.js:355:46)\\\\n at Request.callListeners (/var/app/current/node_modules/aws-sdk/lib/sequential_executor.js:100:18)\\\\n at Request.emit (/var/app/current/node_modules/aws-sdk/lib/sequential_executor.js:77:10)\\\\n at Request.emit (/var/app/current/node_modules/aws-sdk/lib/request.js:604:14)\\\\n at ClientRequest.error (/var/app/current/node_modules/aws-sdk/lib/event_listeners.js:204:22)\\\\n at ClientRequest.<anonymous> (/var/app/current/node_modules/aws-sdk/lib/http/node.js:61:19)\\\\n at ClientRequest.EventEmitter.emit (events.js:117:20)\\\\n    at CleartextStream.socketErrorListener (http.js:1547:9)\\\\n    at CleartextStream.EventEmitter.emit (events.js:95:17)\\\\n    at Socket.onerror (tls.js:1431:17)\\\"}\",\"timestamp\":\"2015-03-20T14:42:54.403Z\"}\r\n"},"comment":{"url":"https://api.github.com/repos/awslabs/dynamodb-document-js-sdk/issues/comments/84155696","html_url":"https://github.com/awslabs/dynamodb-document-js-sdk/issues/27#issuecomment-84155696","issue_url":"https://api.github.com/repos/awslabs/dynamodb-document-js-sdk/issues/27","id":84155696,"user":{"login":"rickwaugh1","id":4514070,"avatar_url":"https://avatars.githubusercontent.com/u/4514070?v=3","gravatar_id":"","url":"https://api.github.com/users/rickwaugh1","html_url":"https://github.com/rickwaugh1","followers_url":"https://api.github.com/users/rickwaugh1/followers","following_url":"https://api.github.com/users/rickwaugh1/following{/other_user}","gists_url":"https://api.github.com/users/rickwaugh1/gists{/gist_id}","starred_url":"https://api.github.com/users/rickwaugh1/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rickwaugh1/subscriptions","organizations_url":"https://api.github.com/users/rickwaugh1/orgs","repos_url":"https://api.github.com/users/rickwaugh1/repos","events_url":"https://api.github.com/users/rickwaugh1/events{/privacy}","received_events_url":"https://api.github.com/users/rickwaugh1/received_events","type":"User","site_admin":false},"created_at":"2015-03-20T21:36:45Z","updated_at":"2015-03-20T21:36:45Z","body":"Two separate applications, different servers. Most of the time, \nfunctioning properly. Then get intermittent messages. One was being load \ntested, so conceivably, could have nuked the network. Other one, it's a \nsmall, single server application, that works fine. Except for twice this \nmorning.\n\nI have a ticket in with AWS on the application. But I'm confused as to \nwhy it would start then stop doing this.\n\nOn 2015-03-20 2:15 PM, raymolin wrote:\n>\n> From what it looks like, this error stems from a networking issue. Can \n> you verify that the EC2 node is getting traffic properly?\n>\n> —\n> Reply to this email directly or view it on GitHub \n> <https://github.com/awslabs/dynamodb-document-js-sdk/issues/27#issuecomment-84149738>.\n>\n\n-- \nServer Developer\nFinger Food Studios Inc.\ntel: 604-475-0350\nemail: rick@fingerfoodstudios.com\n\nskype: rick.waugh4\n\nwww.fingerfoodstudios.com\n\nMESSAGES / COMMENTS This message is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately and return the original message to us at the above address. Thank you.\n\n"}}