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

Consular should quit if it fails to start up #24

Open
JayH5 opened this issue Aug 26, 2015 · 0 comments
Open

Consular should quit if it fails to start up #24

JayH5 opened this issue Aug 26, 2015 · 0 comments

Comments

@JayH5
Copy link
Contributor

JayH5 commented Aug 26, 2015

Due to a Puppet misconfiguration, we recently ran Consular like this:

consular --host= --sync-interval=300 --purge --registration-id=prd-unicore-controller01 --consul=http://:8500 --marathon=http://:8080

Which simply fails to connect to Marathon:

Log opened.
ConsularSite starting on 7001
Starting factory <consular.main.ConsularSite instance at 0x7f5b76741758>
Unhandled error in Deferred:
Unhandled Error
    Traceback (most recent call last):
    Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused.

Consular event callback registered.
Not handling event type: subscribe_event

And then... nothing.

Consular should quit and not appear to things to be happily running.

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

No branches or pull requests

1 participant