Could i get a Dev to look at my logs

[cloudbr34k84]

The problem

After updating to Home Assistant version 2024.10, my server, which runs on a NUC Intel(R) Core(TM) i5-5250U CPU @ 1.60GHz, 12gb ram has been consistently running very loud and reaching high temperatures (80-100°C), even when in safe mode. Prior to this update, my server was running quietly and at normal temperatures. I have not made any hardware or significant configuration changes aside from the Home Assistant update.

It would be good if a dev could take a look at my profile log and callgrind logs. My HA log is too big to upload... profile.1727992624897317 (1).zip

What version of Home Assistant Core has the issue?

2024.10.0

What was the last working version of Home Assistant Core?

2024.9.0

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[chilicheech]

A similar thing is happening to me. I use the docker container install. Since the upgrade the computer is running hot and the container keeps crashing every 10 minutes or so with this error:

[22:55:13] INFO: Home Assistant Core finish process exit code 256
[22:55:13] INFO: Home Assistant Core finish process received signal 9
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

[cloudbr34k84]

A similar thing is happening to me. I use the docker container install. Since the upgrade the computer is running hot and the container keeps crashing every 10 minutes or so with this error:

[22:55:13] INFO: Home Assistant Core finish process exit code 256
[22:55:13] INFO: Home Assistant Core finish process received signal 9
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Are you running ALexa, as the latest Alexa update has broken HA.

[chilicheech]

Ah! you are right. The issue was with the Alexa Media Player integration. Downgrading to version 4.13.2 resolved the issue. Thanks for the pointer.

[home-assistant[bot]]

Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration (profiler) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `profiler` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign profiler` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

profiler documentation profiler source _{^{(message by IssueLinks)}}

[bdraco]

Something is generating a massive amount of tracebacks with a template in it

[bdraco]

Please turn on debug logging and post a log

logger:
  default: debug

I expect your log will be full of exceptions somewhere

[cloudbr34k84]

Hey @bdraco thanks for helping me out here. here are the logs from when i restarted HA? Should i be going through all my templates as well?

home-assistant.log.zip

[cloudbr34k84]

@bdraco just an update on my end im running safe mode, and disabled all my automations i have also enabled the below in my logger.

logger:
  default: warning
  logs:
    homeassistant.core: debug
    homeassistant.helpers.event: debug
    homeassistant.helpers.entity: debug
    homeassistant.components.automation: debug
    homeassistant.components.script: debug
    homeassistant.components.template: debug
    homeassistant.components.recorder: debug
    homeassistant.components.history: debug
    homeassistant.components.zha: debug
    homeassistant.components.mqtt: debug
    homeassistant.components.light: debug
    homeassistant.components.switch: debug
    homeassistant.components.climate: debug
    homeassistant.components.spotcast: debug
    homeassistant.components.systemmonitor: debug
    homeassistant.components.supervisor: debug

1 critical error i saw shows a warning related to an asynchronous task in Home Assistant. Specifically, it indicates that a task involving a WebSocket forward operation in the Hass.io ingress took longer than expected (0.319 seconds).

```2024-10-11 14:07:03.278 WARNING (MainThread) [asyncio] Executing <Task pending name='Task-1817' coro=<_websocket_forward() running at /usr/src/homeassistant/homeassistant/components/hassio/ingress.py:295> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/local/lib/python3.12/asyncio/futures.py:387, Task.task_wakeup()] created at /usr/local/lib/python3.12/asyncio/base_events.py:449> cb=[_wait.<locals>._on_completion() at /usr/local/lib/python3.12/asyncio/tasks.py:534] created at /usr/src/homeassistant/homeassistant/util/async_.py:45> took 0.319 seconds

[cloudbr34k84]

@bdraco I setup an automation to alert me of Critical Errors, and i noticed as soon as i got this notification, I saw disconnection message pop up?? Executing <TimerHandle when=92485.82848051899 _run_async_call_action(<HomeAssistant RUNNING>, <Job None Has...ant RUNNING>)>) at /usr/src/homeassistant/homeassistant/helpers/event.py:1557 created at /usr/src/homeassistant/homeassistant/helpers/event.py:1604> took 0.306 seconds

In fact when i look at the past crital messages i received, its the same Executing <TimerHandle when=64573.150756614996 _run_async_call_action(<HomeAssistant RUNNING>, <Job None Has...ant RUNNING>)>) at /usr/src/homeassistant/homeassistant/helpers/event.py:1557 created at /usr/src/homeassistant/homeassistant/helpers/event.py:1604> took 0.183 seconds. 8 hours ago

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.