tasmo
December 2, 2021, 6:47am
1
Hi,
I am running HASS 6.6 core 2021.11.5 on a raspberry pi 4 with 1gb of ram. Sometimes the frontend stops working (always happens at night time), when trying to load in browser by ip address https://192.168.0.150:8123/ will throw ERR_CONNECTION_REFUSED and hass mobile app doesn’t load either. (I also have a duckdns domain but for debugging purposes I am working directly with the local network IP)
A reboot at this point, fixes the issue, everything goes back to normal but it’s annoying because it happens every couple of days apart although sometimes goes a full week with no issues. I would like to track down the problem and try to fix it because the system otherwise runs nicely.
While the frontend is dead, the system responds to ping just fine and SSH works.
Running htop, shows about 50% of physical memory used and minimal CPU load.
these are the contents of /config/homeassistant.log, the system became unresponsive sometime after 2021-12-01 19:33:06
2021-12-01 12:24:41 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration scheduler which has not been tested by Home Assistant. This component might cause stability >
2021-12-01 12:24:41 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability probl>
2021-12-01 12:25:17 WARNING (MainThread) [homeassistant.components.generic_thermostat.climate] The climate mode is OFF, but the switch device is ON. Turning off device switch.thermostat
2021-12-01 12:31:00 ERROR (MainThread) [frontend.js.latest.202111090] https://myduckdns.duckdns.org:8123/lovelace/default_view:0:0 Uncaught
2021-12-01 13:24:17 ERROR (MainThread) [frontend.js.latest.202111090] https://myduckdns.duckdns.org:8123/lovelace/default_view:0:0 Uncaught
2021-12-01 13:25:35 ERROR (MainThread) [frontend.js.latest.202111090] https://myduckdns.duckdns.org:8123/lovelace/default_view:0:0 Uncaught
2021-12-01 19:10:16 ERROR (MainThread) [frontend.js.latest.202111090] https://myduckdns.duckdns.org:8123/lovelace/default_view:0:0 Uncaught
2021-12-01 19:10:54 ERROR (MainThread) [frontend.js.latest.202111090] https://myduckdns.duckdns.org:8123/lovelace/default_view:0:0 Uncaught
2021-12-01 19:26:06 WARNING (MainThread) [homeassistant.components.automation.fan] Fan: Already running
2021-12-01 19:26:12 WARNING (MainThread) [homeassistant.components.automation.fan] Fan: Already running
2021-12-01 19:26:17 WARNING (MainThread) [homeassistant.components.automation.fan] Fan: Already running
2021-12-01 19:26:21 WARNING (MainThread) [homeassistant.components.automation.fan] Fan: Already running
2021-12-01 19:33:06 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [548166926496] Client unable to keep up with pending messages. Stayed over 512 for 5 seconds
2021-12-01 20:00:21 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [548154095312] Client unable to keep up with pending messages. Stayed over 512 for 5 seconds
2021-12-01 20:48:06 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [548126263568] Client unable to keep up with pending messages. Stayed over 512 for 5 seconds
2021-12-02 00:53:21 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/core_mosquitto/stats request
2021-12-02 00:53:21 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/core_duckdns/stats request
2021-12-02 00:53:21 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_nodered/stats request
2021-12-02 00:53:21 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_wireguard/stats request
2021-12-02 00:53:21 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_influxdb/stats request
2021-12-02 00:53:21 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_ssh/stats request
2021-12-02 00:53:21 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_grafana/stats request
2021-12-02 00:53:21 WARNING (MainThread) [homeassistant.components.hassio] Can't read Supervisor data:
Any idea of what might be the problem here? Or maybe what else I could check?
Thanks!
koying
(Chris B)
December 2, 2021, 7:54am
2
Those seems to indicate you have a problem with some automations running too often / eating too much resource.
It might or might not be the origin of HA becoming unresponsive…
tasmo
December 2, 2021, 8:01am
3
That fan automation has just been added and I was actually sending some manual overrides for that relay at 19:26. System was fully responsive at that time and these problems I’ve been having go back about 2 months ever since I’ve setup this instance.
For the 3 ERRORS at 19:33, 20:00 and 20:48 what is the source of those messages or what can I do to investigate this further?
Is there something else I could check right now when the frontend is not loading? Something that would point to the problem?
Not a direct solution to your problem, but this might be of interest:
opened 06:17AM - 22 Sep 20 UTC
closed 03:55PM - 28 Apr 21 UTC
integration: websocket_api
<!-- READ THIS FIRST:
- If you need additional help with this template, pleas… e refer to https://www.home-assistant.io/help/reporting_issues/
- Make sure you are running the latest version of Home Assistant before reporting an issue: https://github.com/home-assistant/core/releases
- Do not report issues for integrations if you are using custom components or integrations.
- Provide as many details as possible. Paste logs, configuration samples and code into the backticks.
DO NOT DELETE ANY TEXT from this template! Otherwise, your issue may be closed without comment.
-->
## The problem
ERROR: "Client unable to keep up with pending messages. Stayed over 512 for 5 seconds" appears at the system log constantly
## Environment
subject | info|
-- | --
arch | armv7
chassis |
dev | false
docker | true
docker_version | 19.03.12
hassio | true
host_os | Raspbian GNU/Linux 10 (buster)
installation_type | Home Assistant Supervised
os_name | Linux
os_version | 5.4.51-v7+
python_version | 3.8.5
supervisor | 245
timezone | Europe/Kiev
version | 0.115.2
virtualenv | false
- Home Assistant Core release with the issue: 0.115.2
- Last working Home Assistant Core release (if known): don't know
- Operating environment (OS/Container/Supervised/Core): Raspbian GNU/Linux 10 (buster)
- Integration causing this issue: don't know
- Link to integration documentation on our website: don't know
## Problem-relevant `configuration.yaml`
```yaml
homeassistant:
name: "aaa"
latitude: !secret latitude_coord
longitude: !secret longitude_coord
elevation: 179
unit_system: metric
time_zone: Europe/Kiev
customize: !include includes/customize.yaml
external_url: !secret external_url
internal_url: !secret internal_url
packages: !include_dir_merge_named includes/packages
whitelist_external_dirs:
- /config
config:
logger:
default: info
frontend:
themes: !include_dir_merge_named themes
map:
mobile_app:
sun:
system_health:
updater:
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
lovelace:
mode: yaml
resources: !include includes/resources.yaml
history:
hacs:
token: !secret HACS_github
appdaemon: true
python_script: true
theme: true
google_assistant:
project_id: !secret google_assistant_project_id
exposed_domains:
- switch
- light
- climate
- mediaplayer
- input_boolean
- scene
- script
- sensor
tts:
- platform: google_translate
mqtt:
broker: core-mosquitto
discovery: true
discovery_prefix: homeassistant
username: !secret mqtt_username
password: !secret mqtt_password
smartir:
timer: !include includes/timer.yaml
input_boolean: !include includes/input_boolean.yaml
input_number: !include includes/input_number.yaml
input_select: !include includes/input_select.yaml
group: !include includes/groups.yaml
scene: !include includes/scenes.yaml
recorder: !include includes/recorder.yaml
climate: !include includes/climate.yaml
zone: !include includes/zone.yaml
person: !include includes/person.yaml
telegram_bot: !include includes/telegram_bot.yaml
notify: !include includes/notify.yaml
remote: !include includes/remote.yaml
sensor: !include_dir_merge_list includes/sensor
automation: !include_dir_merge_list includes/automation
binary_sensor: !include_dir_merge_list includes/bin_sensor
script: !include_dir_merge_named includes/scripts
switch: !include_dir_merge_list includes/switches
```
## Traceback/Error logs
```txt
Logger: homeassistant.components.websocket_api.http.connection.1844975792
Source: components/websocket_api/http.py:138
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 00:37:19 (1 occurrences)
Last logged: 00:37:19
Client unable to keep up with pending messages. Stayed over 512 for 5 seconds
```
## Additional information
At least it shows that you are not alone here, and maybe you will find a hint to a solution for your case?
1 Like
klogg
(Klogg)
January 3, 2022, 9:46am
5
Yeah, seems to still be an issue for many (including me) but it has been closed without much explanation why (as is often the case…)