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

Error when deploying to Sagemaker starting from release 0.3.0 #3212

Closed
miko7879 opened this issue Mar 5, 2024 · 7 comments
Closed

Error when deploying to Sagemaker starting from release 0.3.0 #3212

miko7879 opened this issue Mar 5, 2024 · 7 comments

Comments

@miko7879
Copy link

miko7879 commented Mar 5, 2024

Since release 0.3.0 we have been unable to deploy vLLM containers to Sagemaker. It has to do with the get_ip() function call in utils.py. In release 0.3.0 we got an OS error, and with 0.3.3 we are getting the following: socket.gaierror: [Errno -2] Name or service not known, when making the following call: s.connect(("dns.google", 80)). Could you please add something to make the get_ip() function fall back to what was there in release 0.2.7 if all else fails?

For reference, here is the function call in 0.2.7: https://github.com/vllm-project/vllm/blob/v0.2.7/vllm/utils.py#L60

In 0.3.0 it was changed to the following, and stopped working on Sagemaker: https://github.com/vllm-project/vllm/blob/v0.3.0/vllm/utils.py#L164

It is now as follows: https://github.com/vllm-project/vllm/blob/v0.3.3/vllm/utils.py#L172

@miko7879 miko7879 changed the title Error when deploying to Sagemaker Error when deploying to Sagemaker starting from release 0.3.0 Mar 5, 2024
@simon-mo
Copy link
Collaborator

simon-mo commented Mar 5, 2024

This might be fixed by #3176

@miko7879
Copy link
Author

miko7879 commented Mar 5, 2024

I don't believe that #3176 will resolve this because it has been failing with release tag 0.3.0, which uses the same line as in #3176

@miko7879
Copy link
Author

miko7879 commented Mar 5, 2024

I believe this will be resolved by #2961

@a1164714
Copy link

a1164714 commented Mar 12, 2024

I got the same error.

@DefTruth
Copy link
Contributor

same error, even the 8.8.8.8 is unreachable in my env.

@miko7879
Copy link
Author

@a1164714 @DefTruth I'm glad I'm not the only one haha. Could you please thumbs up my comment on the release tracker to try and get the fix pushed in to 0.3.4?

#3155 (comment)

@miko7879
Copy link
Author

miko7879 commented Apr 3, 2024

Confirmed that this issue is fixed starting 0.4.0.

@miko7879 miko7879 closed this as completed Apr 3, 2024
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

4 participants