-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
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.
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
MariaDB: Updating sql sensor took longer than the scheduled update interval 0:00:30 #90597
Comments
Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) sensor documentation |
Have updated python to 3.11.2... awaiting recurrence (typically within 7-10 days) |
I think am getting the same problem.
|
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. |
The problem
Seeing repeated issues on this subject even after reboot. Not associated with change to DST.
Running on dedicated computer that did not have this issue before 2023.3.x
What version of Home Assistant Core has the issue?
core-2023.3.6
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Recorder
Link to integration documentation on our website
https://www.home-assistant.io/integrations/sensor
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
OS: Centos 7
Python: 3.11.0
MariaDB: 10.6.12-1.el7.centos
mysqlclient: 2.1.1
Connection URL: mysql://USER:PASSWORD@localhost/homeassistant?charset=utf8mb4
Stopping Hass takes long time (than usual). Stopping MariaDB shows hanging threads from Hass causing it to fail to shutdown, requiring
Kill -9 PID
Thread 38 (user : 'HASS_ADMIN_ACCT') did not exit
The text was updated successfully, but these errors were encountered: