Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Connection failures to RabbitMQ should not be treated as fatal #13

Closed
satta opened this issue Nov 22, 2018 · 1 comment
Closed

Connection failures to RabbitMQ should not be treated as fatal #13

satta opened this issue Nov 22, 2018 · 1 comment
Assignees
@satta
Labels
bug Something isn't working

Comments

@satta
Copy link
Member

satta commented Nov 22, 2018 

{"level":"fatal","msg":"dial tcp xxx.xxx.xx.xxx:5672: connect: connection refused","time":"2018-11-22T12:46:34Z"}
{"level":"fatal","msg":"dial tcp xxx.xxx.xx.xxx:5672: connect: connection refused","time":"2018-11-22T12:46:35Z"}
{"level":"fatal","msg":"dial tcp xxx.xxx.xx.xxx:5672: connect: connection refused","time":"2018-11-22T12:46:35Z"}
{"level":"fatal","msg":"dial tcp xxx.xxx.xx.xxx:5672: connect: connection refused","time":"2018-11-22T12:46:36Z"}
{"level":"fatal","msg":"dial tcp xxx.xxx.xx.xxx:5672: connect: connection refused","time":"2018-11-22T12:46:37Z"}
@satta satta changed the title Collection failures to RabbitMQ should not be treated as fatal Connection failures to RabbitMQ should not be treated as fatal Nov 22, 2018
@satta satta added the bug Something isn't working label Jul 18, 2019
@satta
Copy link
Member Author

satta commented Jul 23, 2019

This might actually have been fixed by #43. Let's keep an eye open whether we still see this happening.

@satta satta self-assigned this Jul 23, 2019
@satta satta closed this as completed Sep 23, 2019
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees

@satta satta

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@satta