-
Notifications
You must be signed in to change notification settings - Fork 290
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
gem --list hangs - need a way to set a timeout
#452
Comments
|
Interesting. Are you using a proxy or anything like that or is this native gem to rubygems.org? |
|
We aren't using a proxy. The machine sits behind a regular NAT instance inside an AWS VPC and the lsof output above shows that it established a direct connection to the gem server (I.e. there was successful 2-way traffic) |
|
@amosshapira as far as I know, there's no way to set a timeout on the It's worth noting that even the puppet local gem provider doesn't support this: I'm going to close this as I don't think it's possible, and seems like a rare enough edge case. |
|
Thanks for looking at this. Since we intend to move away from Puppet to immutable servers, hopefully this will be less of an issue. |
We've been bitten for a second time now by Puppet hanging on the
gem list --remote ^sensu-plugin$call from inside the Puppet module, here is whatpstreeshows:As far as I can tell, the problem is in the
sensu_gempackage provider at https://github.com/sensu/sensu-puppet/blob/master/lib/puppet/provider/package/sensu_gem.rb#L19, this call needs some way to specify a timeout and fail.In case this helps, here is
lsofoutput on the gem process:The text was updated successfully, but these errors were encountered: