-
Notifications
You must be signed in to change notification settings - Fork 335
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
Sporadic "resource deadlock avoided" errors for GCE credentials #450
Comments
What version of gsutil are you running? And are you able to get a stack trace for the related error if you run gsutil with the top-level |
This is gsutil 4.25. Stack trace looks like the following:
|
Some additional background: there are typically multiple copies of gsutil running simultaneously when this error occurs. |
Ah, I see. That can lead to all sorts of issues. They're all trying to use the same state directory, and are probably stepping all over each other's files used to track state. If you're going to run multiple invocations of gsutil at the same time, set the
|
In the last few days I've been getting this error sporadically when trying to copy files from GCS onto local storage on GCE nodes:
It is unclear to me whether this is related to the metadata connection mentioned above, the locking bug fixed in oauth2client a couple years ago, or something else entirely.
The text was updated successfully, but these errors were encountered: