search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
74k stars 31.05k forks source link

2024.11.3 Core - logs not loading #131431

Open TH3xR34P3R opened 3 days ago

TH3xR34P3R commented 3 days ago

The problem

As of 2024.11.3 core update my logs are not showing in the dashobard nor loading and the only other issue was that File editor addon was not able to be loaded creating a repair notice (I have had to temporarily remove it and disable it via the repair notice until its resolved).

I have checked the issue in chrome, firefox and the companion app and its the same issue on all devices/browsers.

Currently this is only issue that is in this build for me, everything else is working as it should otherwise.

What version of Home Assistant Core has the issue?

2024.11.3

What was the last working version of Home Assistant Core?

2024.11.2

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?

Logger: homeassistant.components.websocket_api.http.connection
Source: components/recorder/core.py:357
integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 10:46:32 AM (30 occurrences)
Last logged: 3:41:04 PM

[140613156223392] Error handling message: Unknown error (unknown_error) Robert Koganov from 192.168.2.2 (Mozilla/5.0 (Linux; Android 14; SM-S918B Build/UP1A.231005.007; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/131.0.6778.39 Mobile Safari/537.36 Home Assistant/2024.10.3-14058 (Android 14; SM-S918B))
[140612603843712] Error handling message: Unknown error (unknown_error) Robert Koganov from 192.168.2.2 (Mozilla/5.0 (Linux; Android 14; SM-S918B Build/UP1A.231005.007; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/131.0.6778.39 Mobile Safari/537.36 Home Assistant/2024.10.3-14058 (Android 14; SM-S918B))
[140612459929392] Error handling message: Unknown error (unknown_error) Robert Koganov from 192.168.2.2 (Mozilla/5.0 (Linux; Android 14; SM-S918B Build/UP1A.231005.007; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/131.0.6778.39 Mobile Safari/537.36 Home Assistant/2024.10.3-14058 (Android 14; SM-S918B))
[140612460164240] Error handling message: Unknown error (unknown_error) Robert Koganov from 192.168.2.2 (Mozilla/5.0 (Linux; Android 14; SM-S918B Build/UP1A.231005.007; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/131.0.6778.39 Mobile Safari/537.36 Home Assistant/2024.10.3-14058 (Android 14; SM-S918B))
[140612449220736] Error handling message: Unknown error (unknown_error) Robert Koganov from 192.168.1.100 (Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:132.0) Gecko/20100101 Firefox/132.0)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 28, in _handle_async_response
    await func(hass, connection, msg)
  File "/usr/src/homeassistant/homeassistant/components/history/websocket_api.py", line 524, in ws_stream
    last_event_time = await _async_send_historical_states(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/history/websocket_api.py", line 282, in _async_send_historical_states
    last_time_ts, last_time_dt, payload = await instance.async_add_executor_job(
                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/recorder/core.py", line 357, in async_add_executor_job
    return self.hass.loop.run_in_executor(self._db_executor, target, *args)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 863, in run_in_executor
    executor.submit(func, *args), loop=self)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 170, in submit
    raise RuntimeError('cannot schedule new futures after shutdown')
RuntimeError: cannot schedule new futures after shutdown

as well as:

Logger: aiohttp.server
Source: /usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py:448
First occurred: 10:46:33 AM (464 occurrences)
Last logged: 3:41:06 PM

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 477, in _handle_request
    resp = await request_handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_app.py", line 567, in _handle
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 83, in forwarded_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 86, in ban_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 32, in headers_middleware
    response = await handler(request)
               ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle
    result = await handler(request, **request.match_info)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/history/__init__.py", line 121, in get
    await get_instance(hass).async_add_executor_job(
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/recorder/core.py", line 357, in async_add_executor_job
    return self.hass.loop.run_in_executor(self._db_executor, target, *args)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 863, in run_in_executor
    executor.submit(func, *args), loop=self)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 170, in submit
    raise RuntimeError('cannot schedule new futures after shutdown')
RuntimeError: cannot schedule new futures after shutdown

Additional information

No response

mib1185 commented 2 days ago

please restart HA in safe mode and check if the issue still occur, thx :+1:

TH3xR34P3R commented 2 days ago

please restart HA in safe mode and check if the issue still occur, thx 👍

Restarted in safe mode as requested and the logbook is still not loading:

image

here is the main log message that I see in relation to this when in safe mode:

Logger: homeassistant.components.websocket_api.http.connection Source: components/recorder/core.py:357 integration: Home Assistant WebSocket API (documentation, issues) First occurred: 2:20:25 PM (4 occurrences) Last logged: 2:20:44 PM

[140458195053312] Error handling message: Unknown error (unknown_error) Robert Koganov from 192.168.1.100 (Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:132.0) Gecko/20100101 Firefox/132.0) [140458152362480] Error handling message: Unknown error (unknown_error) Robert Koganov from 192.168.1.100 (Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:132.0) Gecko/20100101 Firefox/132.0) Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 28, in _handle_async_response await func(hass, connection, msg) File "/usr/src/homeassistant/homeassistant/components/history/websocket_api.py", line 524, in ws_stream last_event_time = await _async_send_historical_states( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/history/websocket_api.py", line 282, in _async_send_historical_states last_time_ts, last_time_dt, payload = await instance.async_add_executor_job( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/recorder/core.py", line 357, in async_add_executor_job return self.hass.loop.run_in_executor(self._db_executor, target, args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/asyncio/base_events.py", line 863, in run_in_executor executor.submit(func, args), loop=self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 170, in submit raise RuntimeError('cannot schedule new futures after shutdown') RuntimeError: cannot schedule new futures after shutdown

All others are just referenceing the disabled addons and hacs that is set to not load in safe mode as I can see.

as well as this one:

Logger: homeassistant.components.recorder.util Source: components/recorder/util.py:202 integration: Recorder (documentation, issues) First occurred: 2:20:16 PM (3 occurrences) Last logged: 2:20:17 PM

Error executing query: (sqlite3.DatabaseError) database disk image is malformed (Background on this error at: https://sqlalche.me/e/20/4xp6)

That last log message tells me that the logger database needs to be rebuilt as such I would need the commands for that or wait for a hotfix update that runs this action for me to test.

home-assistant[bot] commented 2 days ago

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (recorder) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `recorder` 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 recorder` 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)

recorder documentation recorder source (message by IssueLinks)

TH3xR34P3R commented 1 day ago

Just to add to this thread:

image

I have tried this in both normal and safe mode and there is no change to my instance.