Skip to content
This repository has been archived by the owner on Jul 13, 2023. It is now read-only.

Stop logging ConnectionRefused error #408

Closed
bbangert opened this issue Mar 12, 2016 · 2 comments
Closed

Stop logging ConnectionRefused error #408

bbangert opened this issue Mar 12, 2016 · 2 comments
Milestone
PUSHSVC-0: quality

Comments

@bbangert
Copy link
Member

If a node disappears but the IP later is valid (but is not our system) we end up logging it. This is the error we log:

"Could not route message: ConnectionRefusedError('Connection refused',)"
@bbangert bbangert added this to the PUSHSVC-0: quality milestone Mar 12, 2016
@bbangert
Copy link
Member Author

Should note, we do capture this in endpoint, and log it as an error. There's no good reason to log these errors.

@bbangert bbangert changed the title Capture ConnectionRefused error Stop loggoing ConnectionRefused error Mar 12, 2016
@bbangert bbangert changed the title Stop loggoing ConnectionRefused error Stop logging ConnectionRefused error Mar 12, 2016
@bbangert bbangert added the ready label Mar 14, 2016
@bbangert bbangert mentioned this issue Mar 18, 2016
Closed
@bbangert
Copy link
Member Author

Obsoleted by #419 .

@bbangert bbangert removed the ready label Mar 18, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
PUSHSVC-0: quality
Development

No branches or pull requests
1 participant
@bbangert