The recorder queue reached the maximum size of 30000; Events are no longer being recorded

Configuration
1

Hello,

search for help regarding my problem but most entries referred to October 31st and time change.
I have been experiencing this for some time, it is repeating every few days, I have to restart HA for the sensors to be recorded again.

I have deleted and added MariaDB.

My config regarding recorder is following:

recorder:
db_url: mysql://homeassistant:mypwd@core-mariadb/homeassistant?charset=utf8mb4
purge_keep_days: 14

MariaDB:
databases:

  • homeassistant
    logins:
  • username: homeassistant
    password: Matrawr
  • username: grafana
    password: Trawyutr
    rights:
  • username: user
    database: homeassistant
  • username: grafana
    password: pwd
    database: homeassistant
    privileges:
    • SELECT

MariaDB log:
[03:04:27] INFO: Lock tables using mariadb client…
[03:04:27] INFO: MariaDB tables locked.
[04:24:03] INFO: MariaDB tables unlocked.

HA log:
Logger: homeassistant.components.recorder

Source: components/recorder/init.py:464
Integration: Recorder (documentation, issues)
First occurred: 04:10:22 (1 occurrences)
Last logged: 04:10:22

The recorder queue reached the maximum size of 30000; Events are no longer being recorded

Grateful for any hints on solving this,

regards,
Maciek

2

It is generally good practice not to put your passwords on the internet.
And also when pasting config please use the code block formatting.

Regardless, which version of Home Assistant are you running?

3

Thanks for you comment, I have amended passwords before pasting them here.

And I am running version 2021.12.1

and

Host Operating System Home Assistant OS 7.0
Update Channel stable
Supervisor Version supervisor-2021.12.2

on Raspberry Pi 4B

4

Hmmm, not sure why that is happening.

There seems to be an existing thread for people with a similar issue so might be worth keeping an eye on that one.

5

Thanks, unfortunately no solution there…

6

Excactly same error here:

[04:03:00] INFO: Lock tables using mariadb client…
[04:03:00] INFO: MariaDB tables locked.
[04:33:51] INFO: MariaDB tables unlocked."
This is exactly around when all logging stops

Then the log spits out: The recorder queue reached the maximum size of 30000; Events are no longer being recorded

Restart core resolve the issue

7

Do you have automated backup in place? If so, this probably causing the issue…
During backup creation your database gets locked and all the events get queued…

8

I have this issue to. I want my data to be saved but im stripping recorder more and more just to be able to log my electric consumption and still run in to this issue at every backup.

9

Same issues here. Using MariaDB and around once a day I get this error. I can see no link to creating backups. Not sure if this is related, but my problems began after I configured the Energy module with data coming from Slimmelezer that takes data from my digital utility meter. My logs do not show anything else than this particular error.

I only just started using Home Assistant and have only a very few sensors, integrations and automations set up. So right now a little over my head to understand where to find a solution.

10

same issue here. I use external mysql service for recording. I also have energy data recording. Maybe it relates to this issue?

11

Having the same issue…

12

Starting having this issue as well, every 24 hours or so I have to restart HA after getting this message. Been running for awhile and not sure when it started.

13

Now seeing this issue also. Only started in the last few days on 2022.4.6 and 4.7.

14

Mine seems to be related to the Google Drive backup Addon. If I disable that, no issues, so trying to debug that now.

15

I am seeing the same issue. I will disable google backup and see what happens.

16

Hi,

this issue still exist for me after udpating to the lastest HA version. Can someone please help?

I have tried the following

dropped the whole database
changed the collation to utf8mb4
move the data disk from one to another

17

I also have this issue and are running the Google Drive Backup service which I will disable now and see if it helps.