supervisor: Repeating Error in the Supervisor Logs trying to send information to Sentry.io without my permission
Describe the issue you are experiencing
I am getting an Error repeatedly in the Supervisor Logs
22-10-26 01:52:42 WARNING (raven-sentry.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f9074b3d0>: Failed to establish a new connection: [Errno 111] Connection refused')': /api/5370612/envelope/
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Steps to reproduce the issue
I have rebooted and Restarted Supervisor (ha su restart)
Anything in the Supervisor logs that might be useful for us?
22-10-26 01:52:42 WARNING (raven-sentry.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f9074b3d0>: Failed to establish a new connection: [Errno 111] Connection refused')': /api/5370612/envelope/
System Health information
System Information
| version | core-2022.10.5 |
|---|---|
| installation_type | Home Assistant OS |
| dev | false |
| hassio | true |
| docker | true |
| user | root |
| virtualenv | false |
| python_version | 3.10.5 |
| os_name | Linux |
| os_version | 5.15.61-v8 |
| arch | aarch64 |
| timezone | America/New_York |
| config_dir | /config |
Home Assistant Community Store
| GitHub API | ok |
|---|---|
| GitHub Content | ok |
| GitHub Web | ok |
| GitHub API Calls Remaining | 4723 |
| Installed Version | 1.28.3 |
| Stage | running |
| Available Repositories | 1140 |
| Downloaded Repositories | 20 |
Home Assistant Supervisor
| host_os | Home Assistant OS 9.3 |
|---|---|
| update_channel | beta |
| supervisor_version | supervisor-2022.10.1 |
| agent_version | 1.4.1 |
| docker_version | 20.10.18 |
| disk_total | 228.5 GB |
| disk_used | 11.3 GB |
| healthy | true |
| supported | true |
| board | rpi4-64 |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | Samba share (10.0.0), Node-RED (13.4.0), SSH & Web Terminal (12.0.2), MariaDB (2.5.1), Studio Code Server (5.4.0), Glances (0.16.0), Samba Backup (5.2.0), Log Viewer (0.14.0), ArgonOne Active Cooling (28d), ESPHome (2022.10.1) |
Dashboards
| dashboards | 3 |
|---|---|
| resources | 10 |
| views | 8 |
| mode | storage |
Recorder
| oldest_recorder_run | October 23, 2022 at 5:00 AM |
|---|---|
| current_recorder_run | October 26, 2022 at 1:50 AM |
| estimated_db_size | 173.02 MiB |
| database_engine | mysql |
| database_version | 10.6.8 |
Supervisor diagnostics
config_entry-hassio-b20a568cb4d1e3c68d96d3ee7f3f12f1.json.txt
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 15 (5 by maintainers)
Supervisor container also uses the Analytics Settings from Home Assistant??? Because it appears you are using sentry_sdk in supervisor as well … the errors I am seeing are in the Supervisor Log. So if supervisor is sending information and it does not honor the HA Analytics Settings… then you ARE sending information with out my permission .
The error messages above are making the Supervisor log unusable as well…
I just wanted to say a big THANK YOU to everyone who contributed to this issue.
Like the other users who commented, I felt confused and uncomfortable seeing those outbound Sentry.io connections.
It felt very unlike the Home Assistant we know and love ❤️
I really appreciate @mdegat01 (and @pvizeli, @jweston2112, @Tamsy) for listening, clarifying, and expending their valuable time to engineer a solution. 🎉 :shipit:
Thank you.
We do not send any data without permission. Seems they are changing the library and doing somethings but at least they send nothing to us. I will open an issue on sentry that they fix there library and not make a request for whatever if we anyway don’t send data then
Supervisor 2022.11.1 has resolved this issue for me
Since it is logged at warning level if it is making the logs useless what you can do for now is enter this in the cli:
This will set supervisor’s log level to
errorso you won’t see these. Obviously this will cause you to miss out on otherinfoandwarninglevel logs but it sounds like that is already happening given all the noise. And after this you will see the more critical things aterrorand above.That’s not a solution by any means, just a workaround to get your log usable again. I’m going to work on a real fix since it seems it isn’t safe to load sentry at all anymore if diagnostics are off, even if we are filtering out all the events.
Fwiw given the pattern of logging you are describing I’m pretty convinced this is a new connectivity check rather then empty events being sent. Errors and exceptions don’t generally occur in a regular repeating pattern or with such frequency else you would be seeing a lot of other issues.
This is an opensource project and everyone is welcome. There is no free support, it’s a work of all - using it don’t give you any creds to blame someone else. Second, we looked into the library and it doing a kinda system check since we used this library, which is I guess now 3years. I don’t see that this thread is 3years old, right? All is opensource from this code to the library. Instead to talking bullshit, you can read the code and doing a correct analytic of the issue and not doing fake news.
Calls to the mothership shouldn’t happen without user consent in the first place.
There is another issue report about the latter here.