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

Non-descriptive error message when can't connect to Conductor #33

Open
jistr opened this issue Jan 23, 2013 · 1 comment
Open

Non-descriptive error message when can't connect to Conductor #33

jistr opened this issue Jan 23, 2013 · 1 comment
Labels

Comments

@jistr
Copy link
Contributor

jistr commented Jan 23, 2013

This might also be a problem with error logging. It looks like it's trying to log the error but it cannot from some reason.

$ bundle exec bin/aeolus provider_account list
E, [2013-01-23T10:58:54.841618 #10601] ERROR -- : Could not log "request.active_resource" event. NoMethodError: undefined method `code' for nil:NilClass
Error:  Connection refused - connect(2)
For further debugging information, see /tmp/aeolus-cli-trace-10601.log
@TylerRick
Copy link

I'm getting the exact same error message when my app tries to connect via active_resource. (Nothing to do with thor-cli though.)

I don't know how to get the backtrace for the NoMethodError error that gets rescued when ActiveResource attempts to log the request, but the error that occurs immediately after it the attempted HTTP request was Errno::ECONNREFUSED: Connection refused - connect(2), so the logging error must occur as a result of that unhandled/unexpected SystemCallError.

It was probably trying to log the HTTP status code returned by the request, but since the request failed, response.code would have been nil.code...

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

No branches or pull requests

2 participants