in configuration.yaml and HA restarted pretty rapidly.
With it back in it’s taking an age to restart again, getting stuck on starting Recorder.
Once HA restarted, MariaDB log shows:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun mariadb (no readiness notification)
services-up: info: copying legacy longrun mariadb-lock (no readiness notification)
[12:40:36] INFO: Using existing mariadb initial system
[12:40:36] INFO: Starting MariaDB
221002 12:40:36 mysqld_safe Logging to '/data/databases/mariadb.err'.
221002 12:40:36 mysqld_safe Starting mariadbd daemon with databases from /data/databases
221002 12:40:36 mysqld_safe Starting mariadbd daemon with databases from /data/databases
2022-10-02 12:40:36 0 [Note] /usr/bin/mariadbd (server 10.6.8-MariaDB) starting as process 241 ...
2022-10-02 12:40:36 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2022-10-02 12:40:36 0 [Note] InnoDB: Number of pools: 1
2022-10-02 12:40:36 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2022-10-02 12:40:36 0 [Note] mariadbd: O_TMPFILE is not supported on /var/tmp (disabling future attempts)
2022-10-02 12:40:36 0 [Note] InnoDB: Using Linux native AIO
2022-10-02 12:40:36 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
2022-10-02 12:40:36 0 [Note] InnoDB: Completed initialization of buffer pool
2022-10-02 12:40:36 0 [Note] InnoDB: 128 rollback segments are active.
2022-10-02 12:40:36 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-10-02 12:40:36 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-10-02 12:40:36 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2022-10-02 12:40:36 0 [Note] InnoDB: 10.6.8 started; log sequence number 290481921229; transaction id 15230434
2022-10-02 12:40:36 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-10-02 12:40:36 0 [Note] InnoDB: Loading buffer pool(s) from /data/databases/ib_buffer_pool
2022-10-02 12:40:36 0 [Note] Server socket created on IP: '0.0.0.0'.
2022-10-02 12:40:36 0 [Note] Server socket created on IP: '::'.
2022-10-02 12:40:36 0 [Note] InnoDB: Buffer pool(s) load completed at 221002 12:40:36
2022-10-02 12:40:36 0 [Note] /usr/bin/mariadbd: ready for connections.
Version: '10.6.8-MariaDB' socket: '/run/mysqld/mysqld.sock' port: 3306 MariaDB Server
[12:40:37] INFO: Check data integrity and fix corruptions
mysql.column_stats OK
mysql.columns_priv OK
mysql.db OK
mysql.event OK
mysql.func OK
mysql.global_priv OK
mysql.gtid_slave_pos OK
mysql.help_category OK
mysql.help_keyword OK
mysql.help_relation OK
mysql.help_topic OK
mysql.index_stats OK
mysql.innodb_index_stats OK
mysql.innodb_table_stats OK
mysql.plugin OK
mysql.proc OK
mysql.procs_priv OK
mysql.proxies_priv OK
mysql.roles_mapping OK
mysql.servers OK
mysql.table_stats OK
mysql.tables_priv OK
mysql.time_zone OK
mysql.time_zone_leap_second OK
mysql.time_zone_name OK
mysql.time_zone_transition OK
mysql.time_zone_transition_type OK
mysql.transaction_registry OK
homeassistant.event_data OK
homeassistant.events OK
homeassistant.recorder_runs OK
homeassistant.schema_changes OK
homeassistant.state_attributes OK
homeassistant.states OK
homeassistant.statistics OK
homeassistant.statistics_meta OK
homeassistant.statistics_runs OK
homeassistant.statistics_short_term OK
sys.sys_config OK
[12:40:37] INFO: Ensuring internal database upgrades are performed
[12:40:37] INFO: Ensure databases exists
[12:40:37] INFO: Create database homeassistant
[12:40:37] INFO: Ensure users exists and are updated
[12:40:37] INFO: Update user homeassistant
[12:40:37] INFO: Init/Update rights
[12:40:38] INFO: Granting all privileges to homeassistant on homeassistant
[12:40:38] INFO: Successfully send service information to Home Assistant.
s6-rc: info: service legacy-services successfully started
[12:52:48] INFO: Lock tables using mariadb client...
[12:52:48] INFO: MariaDB tables locked.
2022-10-02 12:55:56 19 [Warning] Aborted connection 19 to db: 'homeassistant' user: 'homeassistant' host: '172.30.32.1' (Got an error reading communication packets)
2022-10-02 12:55:56 17 [Warning] Aborted connection 17 to db: 'homeassistant' user: 'homeassistant' host: '172.30.32.1' (Got an error reading communication packets)
2022-10-02 12:55:56 18 [Warning] Aborted connection 18 to db: 'homeassistant' user: 'homeassistant' host: '172.30.32.1' (Got an error reading communication packets)
2022-10-02 12:55:56 20 [Warning] Aborted connection 20 to db: 'homeassistant' user: 'homeassistant' host: '172.30.32.1' (Got timeout reading communication packets)
2022-10-02 13:06:21 22 [Warning] Aborted connection 22 to db: 'homeassistant' user: 'homeassistant' host: '172.30.32.1' (Got timeout reading communication packets)
Further investigation shows that the ‘crash’ of history/logbook recording occurs when the CPU usage goes above 90%, and this occurs when nightly backups are scheduled.
My Frigate add-on consumes about 60% of CPU capacity but should recording history stop, requiring a restart?