V1.1.3: log flooded again
See original GitHub issueToday I noticed that, about one hour after the update to HassOS8.0, the log got flooded again with websocket errors. This happens as long I cast music:
[547859019088] Client unable to keep up with pending messages. Stayed over 512 for 5 seconds
18:50:29 – (ERROR) Home Assistant WebSocket API - message first occurred at 16:31:15 and shows up 1650 times
[547859019088] Client exceeded max pending messages [2]: 2048
18:50:25 – (ERROR) Home Assistant WebSocket API - message first occurred at 16:43:49 and shows up 15320 times
I rebooted and the loggings are gone for now. I will monitor if they come back. Don’t understand what goes wrong. But for some reason the MA network load can’t be handled when it happens
Issue Analytics
- State:
- Created a year ago
- Comments:43 (43 by maintainers)
Top Results From Across the Web
Log flood detection - Papertrail
Log rate spikes are common and often go unnoticed. They could be an indication that something went terribly wrong or that a high-traffic...
Read more >Drew Kerman's Content - Page 68 - Kerbal Space Program Forums
[1.3] kOS Scriptable Autopilot System v1.1.3.0 ... image is the directory location of the boot file and at the bottom is from the...
Read more >Command v2.0 ReadMe - Avid
Added changes between 1.1.2 and 1.1.3 ... Command v1.1.4 or earlier to v2.0. ... The logging feature in Command has been fine tuned...
Read more >Piper PA24 250 Comanche 1963 (https://forums.x-plane.org/index ...
v1.1.4 change log (idk whether the upload is successful eventually due to the wifi failure ... -better panel flood light (thanks to Flyingtak1...
Read more >| The National Flood Insurance Program | FloodSmart
Learn more about coverage limits and what is or isn't covered. Flood Maps Icon. Flood Maps. No matter where you live or work,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
OK, That would be really nice because I was out of options 😃
Well, my theory is that you have a component on your setup causing too many state changes. I don’t think (and hope) there’s a relation to MA other than it might cause just that additional cpu usage to expose it.
I’ll let you know once I find out how to better debug this one