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

Unhandled rejection Error: getaddrinfo ENOTFOUND #966

Closed
sf-tyrone opened this issue Apr 1, 2021 · 14 comments
Closed

Unhandled rejection Error: getaddrinfo ENOTFOUND #966

sf-tyrone opened this issue Apr 1, 2021 · 14 comments

Comments

@sf-tyrone
Copy link

when

Summary

when i try to create a new scratch org , i keep getting this error: https://github.com/forcedotcom/cli

Steps To Reproduce:

create a scracth org and then use the sfdx command line "sfdx force:source:push -f"

Expected result

meta to be pushed into scratch org

Actual result

Unhandled rejection Error: getaddrinfo ENOTFOUND ...........at GetAddrInfoReqWrap.onlookup [as oncomplete]

Additional information

Feel free to attach a screenshot.

VS Code Version: 1.55.0

SFDX CLI Version:

OS and version: Darwin x64 19.3.0

@smaddox-sf
Copy link

Hi @sf-tyrone - You mention using the command line. Are you executing the commands from the command line? Or from VS Code?

Can you re-paste the error you receive? The text in the issue description has a link to another of our repos so it's unclear what the error is.

What version of the SFDX CLI are you using?

What version of the Salesforce extensions within VS Code are you using?

@sf-tyrone
Copy link
Author

sf-tyrone commented Apr 2, 2021 via email

@sfsholden
Copy link

@sf-tyrone Thank you for reaching out to us about this issue.

I've noticed that in the output from above it looks like sfdx force:source:push -f is using REST by default. This was a recent change made in the CLI (See March 4th).

Can you try adding one of the following? Please let us know if this unblocks you.

Either of the following should switch the deploy type back to SOAP:
sfdx config:set restDeploy=false --global
Or setting an environment variable SFDX_REST_DEPLOY to false

@sf-tyrone
Copy link
Author

sf-tyrone commented Apr 9, 2021 via email

@lcampos lcampos transferred this issue from forcedotcom/salesforcedx-vscode Apr 9, 2021
@pawel-id
Copy link

similar issues raised:
#529
#340

seems growing problem

@sf-tyrone
Copy link
Author

sf-tyrone commented Apr 17, 2021 via email

@shetzel
Copy link
Contributor

shetzel commented May 18, 2021

@sf-tyrone - ENOTFOUND is a DNS issue that the CLI is reporting. I'm guessing (hoping) that issue has been fixed for you. The remaining issue is that the CLI should generally handle these low level nodejs errors in a better way, ideally with options for retries. I'm going to close this in favor of #340.

@shetzel shetzel closed this as completed May 18, 2021
@sf-tyrone
Copy link
Author

sf-tyrone commented May 18, 2021 via email

@shetzel
Copy link
Contributor

shetzel commented May 18, 2021

What is the output of sfdx plugins --core?
Does this only happen when using the force:source:push command or does it also happen when using other commands?
Are you using the CLI to execute the commands in a terminal or are you using VS Code?
Do you have any SFDX_* environment variables set? (e.g., what is the output of env | grep SFDX?

@marsh-mellow
Copy link

marsh-mellow commented Aug 18, 2021

I get a similiar issue everyday for the past 2 years. This one should be reopened.

Retrying the operation usually works. Would it be possible the handle this error as it seems to be related to the reporting of status as the deployment continues as normal on the server.

Adding a retry on error should do the trick.

Failed on first try
image

Success when I try again 2 min later
image

@ivelinganev
Copy link

I have the same problem with my Ubuntu 20.04. Any suggestions are welcome, I need to fix the problem ASAP.
I am with [email protected]

@hansalves
Copy link

I'm having the same issue on sfdx-cli/7.112.1 linux-x64 node-v14.17.4

sfdx plugins --core gives

@oclif/plugin-autocomplete 0.3.0 (core)
@oclif/plugin-commands 1.3.0 (core)
@oclif/plugin-help 3.2.2 (core)
@oclif/plugin-not-found 1.2.4 (core)
@oclif/plugin-plugins 1.10.1 (core)
@oclif/plugin-update 1.4.0-3 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-plugin-lwc-test 0.1.7 (core)
@salesforce/sfdx-trust 3.6.0 (core)
alias 1.1.10 (core)
apex 0.2.3 (core)
auth 1.7.1 (core)
config 1.2.14 (core)
custom-metadata 1.0.12 (core)
data 0.6.0 (core)
generator 1.1.7 (core)
isvte-sfdx-plugin 1.1.12
limits 1.2.1 (core)
org 1.6.7 (core)
salesforce-alm 52.2.3 (core)
schema 1.0.8 (core)
sfdx-cli 7.112.1 (core)
source 1.0.6 (core)
telemetry 1.2.3 (core)
templates 52.1.0 (core)
user 1.4.0 (core)

and env | grep -i sfdx

SFDX_AUTOUPDATE_DISABLE=true
SFDX_IMPROVED_CODE_COVERAGE=true

@ivelinganev
Copy link

I have to share something. I tried the same deployment script connected to my phone 4g internet and had no issues. The strange thing is that with my Dell - ubuntu 20.04 and my home's internet I've got this error. With my Macbook Pro 2016 and my home's internet I have NO errors.
All the SFDX package is the same on the both laptops. I think this DNS problem is related with some laptop wire settings.

@marsh-mellow
Copy link

marsh-mellow commented Aug 25, 2021

I am using 2 different computers both with Windows 10 and move between 3 different internet services and still get the error. i suspect apple may already be implementing a retry but hard to know for sure.

I do always use Bash which may help point us to the underlying issue.

image

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

8 participants