-
-
Notifications
You must be signed in to change notification settings - Fork 28.6k
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
"socket.send() raised exception." appear randomly in logs #26446
Comments
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
@stainlessray @Herjar @aletiffi @glassbase @darkkatarsis @martikainen87 Would you be so kind as to check if this issue still persists and update topic before close? |
I had to throw away that instance and move on. The issue consumed it. I moved to a Docker install after that. I continued to try and troubleshoot this for a week or so. Then moved on. |
I'm running in Docker and I had this issue in that environment, last couple of days I haven't seen it. updated from 102.2 to 102.3 and some HACS integrations was updated as well. So it seems to be solved for me at least! |
Hmmm this is very strange. I'm currently on 0.102.1 and I haven't seen this exception long time. Two days ago I turned on DEBUG logs to track one problem with my config and I see that socket.send() exception also appeared. Logs:
|
On 103.3 , HASSOS 3.7. I see the same 2019-12-21 20:01:54 WARNING (MainThread) [asyncio] socket.send() raised exception. |
On 103.5, Hassio, I see: 2020-01-27 19:19:03 WARNING (MainThread) [asyncio] socket.send() raised exception. |
109.0 i've got the same!
|
111.4 and this has just started happening to me. Raspberry Pi 4 2020-06-29 22:21:00 WARNING (MainThread) [asyncio] socket.send() raised exception. |
Hi guys, version Home Assistant 0.115.6 and having same logs. Do we need to worry about? 2020-10-04 01:21:19 WARNING (MainThread) [asyncio] socket.send() raised exception. Thanks in advance! |
Same on 0.117.2 |
I have the same problem with 0.117.4, likely started somewhere with 0.116.x This is an annoying bug, crashes my systems, a couple times per day Source: /usr/local/lib/python3.8/asyncio/selector_events.py:903 socket.send() raised exception |
Also seeing this issue as well in the past week; as well as a plethora of other problems as well. I can see my Google Cast (Home) devices, but I can no longer see states (everything shows Unavailable; but volume control works); Spotify integrations on the fritz; I have no idea where to start. There are errors showing up that HASS cannot connect to various streams; etc. Small handful of my Zigbee devices are throwing errors: "Unable to find reference entitiy: " - yet they are controllable. Some of my automations are triggering for no reason; and throwing errors. Does this usually indicate a bad installation; and that I should probably start over (saving my configs)? I am also having lights triggering when they aren't supposed to. Looking at the logbook shows that it was triggered by 'Home Assistant Cloud' each time something triggers on its own. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
You guys ever found out where it was coming from? See them now too |
Same here, I have over 10,000 during the last 24h. It started a few hours after upgrading to |
maybe its 2023.5.4 related? |
@pergolafabio did you upgrade as well? did it start after that? |
Well, updated indeed to 2023.5.4 |
Yes, I have upgraded to Localtuya 5.2.0 in parallel with an upgrade to HA core-2023.5.4. The strange thing is that I have restarted HA a few times an hour ago, and I see no asyncio errors anymore. |
Yeah, for me it comes back after about 1 or 2 hours after restart HA, but it's probably a localtuya issue, see here... |
|
Disconnect -> Connect -> Aaaaa! |
Home Assistant release with the issue:
0.98.3
Last working Home Assistant release (if known):
unknown
Operating environment (Hass.io/Docker/Windows/etc.):
Hassbian on RPI3B+
Component/platform:
https://www.home-assistant.io/components/websocket_api/
Description of problem:
I see a lot of warnings in logs that socket.send() raised exception (44 times in last 12h). Baloob said that warnings need to be fixed but I don't see any report for this warning so I'm creating this one. People which have same spam by this exception please add emoji to this post.
socket.send() raised exception.
9:33 AM components/websocket_api/http.py (WARNING) - message first occured at September 4, 2019, 9:35 PM and shows up 44 times
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
I've set logger to debug for websocket_api with the hope that it will help to obtain more information but I'm not sure if it will be usefull (part of log attached below).
The text was updated successfully, but these errors were encountered: