"Error: getaddrinfo ENOTFOUND review-api.udacity.com review-api.udacity.com:443" and "Error: socket hang up"

[kartikarora]

Guidelines to submit an issue

I'm opening this issue because:

• urcli is crashing.

What's going wrong?

List of errors:

• The API is returning the following error: "Error: getaddrinfo ENOTFOUND review-api.udacity.com review-api.udacity.com:443" -The API is returning the following error: "Error: socket hang up"

If gone unnoticed for over an hour, the submission request is deleted from udacity's end.

How can the urcli team reproduce the problem?

• Run urcli assign.
• Leave it running and forget about it. Wait for the error to appear.
• Restart the script.
  • If it was within 1 hour, your queue position will be the same or you would have been assigned submissions.
  • If beyond 1 hour, you will given a new submission request id.

supporting information:

• [x] node -v prints: 6.11.1
• [x] urcli -V prints: 4.0.10
• [x] Windows, OS X/macOS, or Linux?: Linux

[Sinapse87]

I think this is due to udacity messing up with the ip addresses of its machines. Try to change your dns to google dns

[gabraganca]

I had a similar issue yesterday. It seems that the API is unstable.@trolster mentioned in #97, a related issue:

It's definitely a new thing. It's a DNS error, and I have no idea why it's happening. You should forward it to the reviews team and I'll leave this up in case someone else comes here with the same issue.

Mikkel, should we implement a patch that would catch API error and keep urcli running, as you mentioned in #97 ? I'll check the forever package you mentioned to see if it is a viable solution.

[trolster]

I don't think it's wise to change anything before we understand the error, and where it's coming from. Has anyone reported this to Udacity as a bug? If not, then let's all simply start reporting it and hopefully it will resolve itself.

I do look forward to hearing if the forever package will work. You may have to start the command from a shell script though. forever start assign.sh or something, as I assume that you can't just run forever start urcli assign all. I have not really had the time to look into it, but it would be a great way to keep urcli going through errors, without having to patch for every new individual error. I assume that we will at some point get every conceivable error with a large userbase on every different kind of platform and network.

[trolster]

Yeah, after some consideration, I've come to the conclusion that this is caused by the API and may not actually be fixable at all. For anyone who comes here in the future, report it to the API dev team at Udacity.