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.

Sign up for GitHub

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

Jump to bottom

Custody doesn't detect Mongo connection failure for services #59

Open
andyhqtran opened this issue Jun 19, 2018 · 4 comments
Open

Custody doesn't detect Mongo connection failure for services #59

andyhqtran opened this issue Jun 19, 2018 · 4 comments
Labels
bug Something isn't working

Comments

@andyhqtran
Copy link

No description provided.

@andyhqtran
Copy link
Author

Mongo failed but it's still showing that it's running.
image

@wearhere
Copy link
Contributor

wearhere commented Jun 21, 2018 •
edited
Loading

I suspect that this means that the service didn't actually crash when the DB connection failed, but maybe it should, it certainly won't be usable without a connection.

@wearhere
Copy link
Contributor

#60 would help with this too by making it possible to restart the server more quickly.

@wearhere wearhere added the bug Something isn't working label Jun 27, 2018
@andyhqtran
Copy link
Author

This happens during startup, 2 of the services (Compose & Mail) shows that theres any error. The rest doesn't.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wearhere @andyhqtran