First, a description of the issue, which may be simple in the end, but the route to get there is really starting to tick me off.
What happens:
-
every 2-3 days, I hear a loud buzzing coming from the server, which is the CPU throttling alarm for heat.
-
I log in and check, and sure enough it is the VM for home assistant.
-
I am able to see this in the logs for that VM process on my Unraid server. It flaggs the process for the VM, no lower level data provided.
-
I log into Home assistant. Look at “logs” in the web ui… nothing notable except that a few devices couldn’t connect.
-
I click on the supervisor, it won’t load.
-
I click on Node_red on the left hand menu, it usually won’t load while the CPU is pegged.
-
I force reboot the VM and all is good.
Here is where I get frustrated: I noVNC into the VM, and run core logs, and there is nothing there of value i can see, and try host logs… but none of the paging commands work. So it scrolls at light speed for about 10 seconds, and then i see the last 20 or so lines of useless shit. I tried to ssh in from putty but the connection is refused… so i am just at a loss here…
I am running on an Ubuntu VM:
System Health
|arch|x86_64|
| --- | --- |
|chassis|vm|
|dev|false|
|docker|true|
|docker_version|19.03.8|
|hassio|true|
|host_os|HassOS 4.11|
|installation_type|Home Assistant OS|
|os_name|Linux|
|os_version|5.4.50|
|python_version|3.7.7|
|supervisor|232|
|timezone|America/Chicago|
|version|0.112.4|
|virtualenv|false|
### Lovelace
|dashboards|1|
| --- | --- |
|mode|storage|
|resources|0|
|views|3|
This is all i can get from node-red, which is useless since you can’t open the supervisor once it is locked up to look at the logs WHILE IT"S happening…
[20:55:18] INFO: Starting Node-RED...
> addon-node-red@ start /opt
> node $NODE_OPTIONS node_modules/node-red/red.js "--settings" "/etc/node-red/config.js"
14 Aug 20:55:21 - [info]
Welcome to Node-RED
===================
14 Aug 20:55:21 - [info] Node-RED version: v1.1.0
14 Aug 20:55:21 - [info] Node.js version: v12.17.0
14 Aug 20:55:21 - [info] Linux 5.4.50 x64 LE
14 Aug 20:55:22 - [info] Loading palette nodes
14 Aug 20:55:27 - [info] Dashboard version 2.22.1 started at /endpoint/ui
/bin/sh: /opt/node_modules/node-red-node-pi-gpio/testgpio.py: not found
14 Aug 20:55:27 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
14 Aug 20:55:28 - [info] Settings file : /etc/node-red/config.js
14 Aug 20:55:28 - [info] Context store : 'default' [module=memory]
14 Aug 20:55:28 - [info] User directory : /config/node-red/
14 Aug 20:55:28 - [warn] Projects disabled : editorTheme.projects.enabled=false
14 Aug 20:55:28 - [info] Flows file : /config/node-red/flows.json
14 Aug 20:55:28 - [info] Server now running at http://127.0.0.1:46836/
14 Aug 20:55:28 - [info] Starting flows
14 Aug 20:55:28 - [info] Started flows
[20:55:28] INFO: Starting NGinx...
nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
14 Aug 20:55:29 - [error] [api-call-service:Trash out Off] Call-Service attempted without connection to server.
14 Aug 20:55:33 - [info] [server:Home Assistant] WebSocket Connecting http://supervisor/core
14 Aug 20:55:33 - [info] [server:Home Assistant] WebSocket Connected to http://supervisor/core
Any direction or ideas would be appreciated…