8000 Fronted fails to load after some time of normal operation (5-120 minutes) · Issue #50248 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Fronted fails to load after some time of normal operation (5-120 minutes) #50248

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.

Sign up for GitHub

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

Jump to bottom
Closed
3 tasks done
nibbler79 opened this issue May 7, 2021 · 9 comments
Closed
3 tasks done

Fronted fails to load after some time of normal operation (5-120 minutes) #50248

nibbler79 opened this issue May 7, 2021 · 9 comments

Comments

@nibbler79
Copy link
nibbler79 commented May 7, 2021 •
edited
Loading

Checklist

  • I have updated to the latest available Home Assistant version.
  • I have cleared the cache of my browser.
  • I have tried a different browser to see if it is related to my browser.

Describe the issue you are experiencing

After some uptime of HA the frontend is not loading anymore.
Backend Services are ok, Data is collected and Automations seem to run as expected.
Logs dont show any issues with aoihttp (even with debug enabled).
Chrome Waterfall Chart shows that download is stuck at the core.js file (see screenshot)
Using Wireshark you see the request but 0 Bytes being returned and Connection held alive with tcp keep alives.
No difference in http or https, not helpfull to remove any of the integrations, or any frontend extension. (Only using slider and scheduler custom components)

I am out of ideas, and as a nabucasa subscriber already a bit frustrated....

Describe the behavior you expected

Normal Frontend operation

Steps to reproduce the issue

Unknown - I can offer a debug session on the VM.

What version of Home Assistant Core has the issue?

core-2021.5.0

What was the last working version of Home Assistant Core?

issue is happening since at least last update

In which browser are you experiencing the issue with?

Version 90.0.4430.93 (Offizieller Build) (64-Bit)

Which operating system are you using to run this browser?

windows 10

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

None

Additional information

I run hass ova on proxmox - also moved it to esxi, same problem;
fresh install and recover of configs only -> same issues start

if you have any input how to troubleshoot this better (I am no coder) let me know....
@bramkragten
Copy link
Member

This is more a backend than a frontend issue, I'm going to move this.

Can you check your memory and CPU usage?

@bramkragten bramkragten transferred this issue from home-assistant/frontend May 7, 2021
@nibbler79
Copy link
Author

Ok, you mean since its not delivering the JS to the frontend :)
On the Hypervisor I see CPU/MEM/Network is low - 5.5% / 1,8G of 4,5G / 2kBit
If I try to load any other page (e.g. a ressource that is not valid I get a proper 404, very quickly)

@nibbler79
Copy link
Author
nibbler79 commented May 11, 2021 •
edited
Loading

Dears,
Can anyone please pick this topic up, and let me know what I can contribute to fix the problem?
I cannot really use my installation since weeks, and tried to figure it out myself, but unfortunately, debug options are unclear, or logging is too poor to pinpoint the issue.

2021-05-11 09_53_58-Window
2021-05-11 09_55_23-Window

@nibbler79
Copy link
Author

Reboot fixes the problem for a short time.
2021-05-11 09_57_30-Window

@nibbler79
Copy link
Author

System Health

version core-2021.5.1
installation_type Home Assistant Supervised
dev false
hassio true
docker true
virtualenv false
python_version 3.8.9
os_name Linux
os_version 4.19.0-16-amd64
arch x86_64
timezone Europe/Vienna
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor supervisor_api
host_os Debian GNU/Linux 10 (buster)
update_channel stable
supervisor_version supervisor-2021.04.3
docker_version 20.10.6
disk_total 124.5 GB
disk_used 4.5 GB
healthy true
supported true
ok
version_api ok
installed_addons Mosquitto broker (5.1.1), Visual Studio Code (3.3.1)
Lovelace
dashboards 1
resources 0
mode auto-gen

@nibbler79
Copy link
Author

I got a installation that is hass ova on proxmox as well - the same behaviour; This now is debian buster supervised;
Wanted to rule out the OVA
I did not restore a snapshot to this one, but installed all addons from scratch, and only took yaml with me.

@bramkragten
Copy link
Member

Is it also happening on an empty setup, without your integrations? Do you have any custom integrations? Start with disabling those, then you could try to pinpoint what integration it is that causes trouble.

@nibbler79
Copy link
Author

I think it might be related to the modbus integration. disabled that one, will check if stability returns

@nibbler79
Copy link
Author

Issue was solved by disabling modbus module, and remodeling pull of sd230 powermeter data via NodeRed Integration.
It seems that the issue #33754 is related. I had problems starting from about that time. My Sensors updated, but often with timouts, and as it seems also with complete hangup on the frontend.

@github-actions github-actions bot locked and limited conversation to collaborators Jun 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bramkragten @nibbler79
0