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

Error EIO: [Errno 110] Connection timed out #10

Open
stumbaumr opened this issue Feb 21, 2020 · 6 comments
Open

Error EIO: [Errno 110] Connection timed out #10

stumbaumr opened this issue Feb 21, 2020 · 6 comments

Comments

@stumbaumr
Copy link

stumbaumr commented Feb 21, 2020

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...

root@proxmox01:~# ceph health detail
HEALTH_ERR Module 'telemetry' has failed: HTTPSConnectionPool(host='telemetry.ceph.com', port=443): Max retries exceeded with url: /report (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f9949274550>: Failed to establish a new connection: [Errno 110] Connection timed out',))

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...

root@proxmox01:~# ceph telemetry off
Error EIO: Module 'telemetry' has experienced an error and cannot handle commands: HTTPSConnectionPool(host='telemetry.ceph.com', port=443): Max retries exceeded with url: /report (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f9949274550>: Failed to establish a new connection: [Errno 110] Connection timed out',))
root@proxmox01:~#
@dmick
Copy link
Member

dmick commented Feb 21, 2020

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).

@dmick
Copy link
Member

dmick commented Feb 21, 2020

apologies, anyway, for waking you.

@stumbaumr
Copy link
Author

stumbaumr commented Feb 21, 2020

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...

@dmick
Copy link
Member

dmick commented Feb 21, 2020

ceph issues can be filed at tracker.ceph.com

@stumbaumr
Copy link
Author

Just got above error again.
That is it for a while of telemetry data from me.

@dmick
Copy link
Member

dmick commented Jul 29, 2020

Sorry things failed. Did you ever file an issue at tracker.ceph.com? If so, has it gotten any attention?

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

2 participants