All of my gsutil commands cannot works and return socket.timeout: timed out
#498
Comments
|
This issue isn't specific to gsutil; we've seen a slightly-higher-than-usual number of socket timeouts to GCS in general over the past week or so. The GCS team is looking into it. For Google developers wanting more information, the issue tracker number is 72221304 (sorry to external users; the visibility for that issue is internal-only). Given that this isn't a gsutil bug, I'll go ahead and close this GitHub issue. |
This comment has been minimized.
This comment has been minimized.
|
I had the same problem, for me it was a firewall configuration issue. I had an egress deny on tcp 80,443, 8080, which explains the socket timeout. I changed this for my service account and now it works. Hope this helps |
|
INFO 0306 14:44:04.069279 retry_util.py] Retrying request, attempt #6... |
|
Same issue, how do I even troubleshoot this? I was just following this tutorial: https://cloud.google.com/vision/automl/docs/quickstart?refresh=1 |
|
BTW, I'm using the cloud shell, so supposedly no firewall issues should apply to me? |
|
@denfromufa you can use the top-level -D flag to see the command being run, which request is failing, etc. I can get this to happen as well -- I think this occurs because the "gsutil" executable on Cloud Shell instances points to the gcloud installation of gsutil, which assumes that if you're running on GCE, you're on an instance owned by your project. Normally, it will just use the GCE auth plugin to query the VM instance's metadata server and get credentials for your instance's default service account. However, since the instance is owned by the Cloud Shell project, it can't do that, and it fails when trying to fetch those credentials (I see a I confirmed this by creating a config file with my credentials at This is an issue with the Cloud SDK -- it should detect if users are running on the Cloud Shell, and if so, not pass the |
|
@houglum it works today without any changes |
|
Still fails for me today. I'd still guess that the problem comes from trying to obtain the initial access token, but I'd have to add some |
|
I'm facing the same issue from my compute engine. Yesterday the |
It's working now without any change. Don't know why. :( |
|
I had the same problem. It was ipv6. What I tried was: It got lost trying to resolve ipv6 name - Disabled ipv6 and all is well in the world. |
|
Been having this problem for the third day in a row. Disabling IPv6 did not help. I just cannot find out what is going on. The weird part is that some other things break too and it looks like it's not deterministic... like sometimes But All of this happens in Fedora 32 (kernel Linux 5.8.13-200.fc32.x86_64) and Ubuntu 20.04 (didn't remember to take note of the kernel, but it was the latest available). Cloud SDK versions: Feel free to ping me if someone needs more information. |
|
Well... apparently the problems with Docker and Cloud SDK were unrelated, because all of a sudden |
|
Nice debugging @surak. |
|
Still having this issue, it's been from weeks. It works and it does not in casual way. |
|
I solve this issue by connecting with my phone. However, you can fix this by turn off "WAN Blocking" option. |
|
Encountered this issue again, today. Nice to see solid support from Google over 4 years and even closing the issue for us! |
my version:
I have a poxy(socks5) on my linux .And I can run
gcloud initand connect successfully.But my all gsutil commands cannot works and have no request timeout,like these:How to solve it?
The text was updated successfully, but these errors were encountered: