-
Notifications
You must be signed in to change notification settings - Fork 9
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
Error EIO: [Errno 110] Connection timed out #10
Comments
We moved the telemetry server to a different location today; I would expect maybe a few failures, but it should be working again now? I agree that "entire cluster health error" is maybe not advisable, and that it ought to be disableable regardless of past errors (or else the error message should be cleaned up). Both of those, however, are Ceph issues, not with this repo (which is only the server-side scripting). |
apologies, anyway, for waking you. |
Good morning! So should I close the issue here and reopen in ceph/ceph? Mmmmh, there is no issue tab and no hint in the Readme on how/where to open issues... |
ceph issues can be filed at tracker.ceph.com |
Just got above error again. |
Sorry things failed. Did you ever file an issue at tracker.ceph.com? If so, has it gotten any attention? |
Hi,
I activated a while ago the telemetry on my three node ceph cluster and just got out of bed at 1 am because of a lot of SMS messages being sent to my mobile...
No idea if this is intended that the whole cluster has an ERR health status now just because sending telemetry fails.
I think it is better to turn telemetry off for a while...
Upsi, can't turn it off...
The text was updated successfully, but these errors were encountered: