Skip to content
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.

Socket Errors from excon #28

Open
ddollar opened this issue Oct 18, 2012 · 7 comments
Open

Socket Errors from excon #28

ddollar opened this issue Oct 18, 2012 · 7 comments

Comments

@ddollar
Copy link
Contributor

ddollar commented Oct 18, 2012

(from heroku/legacy-cli#606)

This error should come up to heroku as something a bit nicer I think.

@geemus
Copy link
Contributor

geemus commented Oct 18, 2012

@ddollar - is reraising as Heroku::API::Errors::Error (or something like that) good enough? I think the latest excon should give a more coherent message for this particular one (EOF) but it would still be in the form of an Excon::Errors::Error.

@wuputah
Copy link
Contributor

wuputah commented Dec 12, 2012

Please also see heroku/legacy-cli#611 for a similar case.

@pabloivan57
Copy link

I'm having problems with Excon as well. Our app used to work correctly using a Sidekiq worker which purpose was to send emails using ActiveMailer. The mail add-on we use is SendGrid. Here are some important backtrace lines

2014-04-09T19:25:16.043768+00:00 app[web.1]: "Scaling sidekiq to 1"
2014-04-09T19:25:16.188542+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/excon-0.25.1/lib/excon/connection.rb:353:in `response'
2014-04-09T19:25:16.188542+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/excon-0.25.1/lib/excon/connection.rb:247:in `request'
2014-04-09T19:25:16.188542+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/excon-0.25.1/lib/excon/middlewares/expects.rb:6:in `response_call'
2014-04-09T19:25:16.188542+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/heroku-api-0.3.13/lib/heroku/api.rb:76:in `request'
2014-04-09T19:25:16.188542+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/autoscaler-0.2.1/lib/autoscaler/heroku_scaler.rb:38:in `workers='
2014-04-09T19:25:16.188542+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/heroku-api-0.3.13/lib/heroku/api/processes.rb:36:in `post_ps_scale'
2014-04-09T19:25:16.188312+00:00 app[web.1]: Expected(200) <=> Actual(403 Forbidden)
2014-04-09T19:25:16.188542+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/autoscaler-0.2.1/lib/autoscaler/sidekiq.rb:17:in `call'
2014-04-09T19:25:16.188542+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.10.1/lib/sidekiq/middleware/chain.rb:114:in `call'
2014-04-09T19:25:16.188542+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.10.1/lib/sidekiq/middleware/chain.rb:114:in `invoke'
2014-04-09T19:25:16.188921+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.10.1/lib/sidekiq/worker.rb:68:in `client_push'
2014-04-09T19:25:16.188921+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.10.1/lib/sidekiq/client.rb:113:in `process_single'
2014-04-09T19:25:16.188921+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.10.1/lib/sidekiq/extensions/generic_proxy.rb:17:in `method_missing'
2014-04-09T19:25:16.188921+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.17/lib/active_record/associations/collection_proxy.rb:91:in `each'
2014-04-09T19:25:16.188921+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.10.1/lib/sidekiq/client.rb:41:in `push'

Any suggestions of what can I try? It's really urgent for us

@geemus
Copy link
Contributor

geemus commented Apr 9, 2014

What does the code look like in the job that is calling this? Forbidden would be an access issue, ie trying to scale an app for which you do not have permission to do so.

@pabloivan57
Copy link

Pretty standard send mail code:

def bid_created(to_email, sender_id, work_order_id)
    load_notification_vars(sender_id, work_order_id)
    mail(:to => to_email, :subject => "#{@sender.name} Bid on the #{@work_order.title} Work Order", :reply_to => @sender.email)
end

@pabloivan57
Copy link

@geemus, what do you mean by trying to scale an app, where can I start looking into this issue?

@geemus
Copy link
Contributor

geemus commented Apr 9, 2014

@pabloivan57 ah. Well the error from that backtrace is one of sidekiq trying to scale itself to more workers I believe. So perhaps that is the issue at hand (rather than a mailer related one). Does that make more sense?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants