Closed Werewolfke closed 2 months ago
Impact123
commented
3 months ago PVE also includes cache and buffers in this stat. At least on linux VMs. See here: https://www.google.com/search?q=wrong+memory+usage+site%3Aproxmox.com If you want to show PVE statistics please show them in the actual GUI, not a random app.
Werewolfke
commented
2 months ago The random app is a proxmox monitoring app. I could not get into pve at that time. I will look into it and see what I can do, but I know I had to increase ram from 4Gb to 6 because it crashed otherwise, so I didn't think it were to be caching. If it is 100% caching then this issue can be closed.
sairon
commented
2 months ago You can check the amount of available memory directly in Home Assistant Settings -> System -> Hardware. If the system crashes, check Host logs (or Core logs) then but if it were an OOM event it would have been most likely correlated with ~100% memory usage in Proxmox statistics, which I don't see in the graphs you provided. For comparison here's hourly average of my Proxmox VM running a "production" deployment of HAOS (where the available memory in the VM stays around ~2GB still):
All in all I don't see anything wrong here.
Impact123
commented
2 months ago You can check the used/free memory in more detail with the glances addon or by running free -h via SSH. I recommend you visit the discord server if you need help troubleshooting.
Describe the issue you are experiencing
The vm hassio has 6Gb of ram, and was using almost all of it. Looking in homeassistant itself, it says it was using only 0.8Gb, rebooting homeassistant didn't help, just a little bit, a small dip, yet it was still above 5Gb of usage
I had to do a full reboot of the virtual machine for it to clear. Uptime of the full vm is around a week, home assistant itself probably has rebooted since then, since it updates automatically and reboots after.
Maybe something in the host-logs show something? (I rebooted around 21h, so weird that nothing shows between 19h20 and then... Or even after the reboot... Screenshot shows it gradually climbing... Since the boot of the vm.
Core 2024.4.3 Supervisor 2024.04.1 Operating System 12.2 Frontend 20240404.2
What operating system image do you use?
generic-x86-64 (Generic UEFI capable x86-64 systems)
What version of Home Assistant Operating System is installed?
12.2
Did you upgrade the Operating System.
Yes
Steps to reproduce the issue
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System information
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4664 Installed Version | 1.34.0 Stage | running Available Repositories | 1402 Downloaded Repositories | 30Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 12.2 -- | -- update_channel | beta supervisor_version | supervisor-2024.04.1 agent_version | 1.6.0 docker_version | 25.0.5 disk_total | 30.8 GB disk_used | 13.2 GB healthy | true supported | true board | ova supervisor_api | ok version_api | ok installed_addons | Advanced SSH & Web Terminal (17.2.0), Studio Code Server (5.15.0), Music Assistant BETA (2.0.0b136), Firefox (1.1.0)Dashboards
dashboards | 9 -- | -- resources | 15 views | 16 mode | storageRecorder
oldest_recorder_run | April 5, 2024 at 17:02 -- | -- current_recorder_run | April 15, 2024 at 21:07 estimated_db_size | 371.70 MiB database_engine | sqlite database_version | 3.44.2Additional information