mysqld 5.7.44 errors - NetBSD 9_stable (amd64)

[yancm%sdf.org@localhost]

Since some time in December 2023 (?) after an update from pkgsrc, I
started having problems starting mysqld
to support an internal Wordpress installation on my home server/firewall
that's been running fine for many years...

I've re-built/re-installed mysql server to no effect

I do not know much about mysql, so reaching out in case someone can
help... especially with the errno=22?

If I run mysqld manually as user mysql it starts and appears to run
correctly,
but I get the following (note especially the hard [ERROR]s):
$ mysqld &
$
2024-01-22T12:31:10.682717Z 0 [Warning] Changed limits: max_open_files:
1024 (requested 5000)
2024-01-22T12:31:10.858656Z 0 [Warning] TIMESTAMP with implicit DEFAULT
value is deprecated. Please use --explicit_defaults_for_timestamp server
option (see documentation for more details).
2024-01-22T12:31:10.858733Z 0 [Note] --secure-file-priv is set to NULL.
Operations related to importing and exporting data are disabled
2024-01-22T12:31:10.858791Z 0 [Note] mysqld (mysqld 5.7.44) starting as
process 19605 ...
2024-01-22T12:31:10.863544Z 0 [ERROR] Failed to create event (errno= 22).
2024-01-22T12:31:10.863564Z 0 [ERROR] Failed to start timer notify thread.
2024-01-22T12:31:10.863571Z 0 [ERROR] Failed to initialize timer component
(errno 22).
2024-01-22T12:31:10.865486Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC
atomic builtins
2024-01-22T12:31:10.865540Z 0 [Note] InnoDB: Uses event mutexes
2024-01-22T12:31:10.865577Z 0 [Note] InnoDB: GCC builtin
__atomic_thread_fence() is used for memory barrier
2024-01-22T12:31:10.865611Z 0 [Note] InnoDB: Compressed tables use zlib
1.2.13
2024-01-22T12:31:10.866025Z 0 [Note] InnoDB: Number of pools: 1
2024-01-22T12:31:10.866241Z 0 [Note] InnoDB: Using CPU crc32 instructions
2024-01-22T12:31:10.868396Z 0 [Note] InnoDB: Initializing buffer pool,
total size = 128M, instances = 1, chunk size = 128M
2024-01-22T12:31:10.882937Z 0 [Note] InnoDB: Completed initialization of
buffer pool
2024-01-22T12:31:10.906447Z 0 [Note] InnoDB: Highest supported file format
is Barracuda.
2024-01-22T12:31:10.924101Z 0 [ERROR] InnoDB: Page [page id: space=0, page
number=208] log sequence number 449698243 is in the future! Current system
log sequence number 449574542.
2024-01-22T12:31:10.924159Z 0 [ERROR] InnoDB: Your database may be corrupt
or you may have copied the InnoDB tablespace but not the InnoDB log files.
Please refer to
http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for
information about forcing recovery.
2024-01-22T12:31:10.924228Z 0 [ERROR] InnoDB: Page [page id: space=0, page
number=352] log sequence number 449698243 is in the future! Current system
log sequence number 449574542.
2024-01-22T12:31:10.924264Z 0 [ERROR] InnoDB: Your database may be corrupt
or you may have copied the InnoDB tablespace but not the InnoDB log files.
Please refer to
http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for
information about forcing recovery.
2024-01-22T12:31:10.924641Z 0 [ERROR] InnoDB: Page [page id: space=0, page
number=411] log sequence number 449708699 is in the future! Current system
log sequence number 449574542.
2024-01-22T12:31:10.924679Z 0 [ERROR] InnoDB: Your database may be corrupt
or you may have copied the InnoDB tablespace but not the InnoDB log files.
Please refer to
http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for
information about forcing recovery.
2024-01-22T12:31:10.933915Z 0 [Note] InnoDB: Creating shared tablespace
for temporary tables
2024-01-22T12:31:10.934063Z 0 [Note] InnoDB: Setting file './ibtmp1' size
to 12 MB. Physically writing the file full; Please wait ...
2024-01-22T12:31:11.243973Z 0 [Note] InnoDB: File './ibtmp1' size is now
12 MB.
2024-01-22T12:31:11.245012Z 0 [Note] InnoDB: 96 redo rollback segment(s)
found. 96 redo rollback segment(s) are active.
2024-01-22T12:31:11.245053Z 0 [Note] InnoDB: 32 non-redo rollback
segment(s) are active.
2024-01-22T12:31:11.245529Z 0 [Note] InnoDB: Waiting for purge to start
2024-01-22T12:31:11.303579Z 0 [Note] InnoDB: 5.7.44 started; log sequence
number 449574533
2024-01-22T12:31:11.303920Z 0 [Note] InnoDB: Loading buffer pool(s) from
/var/mysql/ib_buffer_pool
2024-01-22T12:31:11.304190Z 0 [Note] Plugin 'FEDERATED' is disabled.
2024-01-22T12:31:11.311472Z 0 [Note] Found ca.pem, server-cert.pem and
server-key.pem in data directory. Trying to enable SSL support using them.
2024-01-22T12:31:11.311538Z 0 [Note] Skipping generation of SSL
certificates as certificate files are present in data directory.
2024-01-22T12:31:11.314464Z 0 [Note] InnoDB: Buffer pool(s) load completed
at 240122  7:31:11
2024-01-22T12:31:11.315398Z 0 [Warning] CA certificate ca.pem is self signed.
2024-01-22T12:31:11.315502Z 0 [Note] Skipping generation of RSA key pair
as key files are present in data directory.
2024-01-22T12:31:11.315836Z 0 [Note] Server hostname (bind-address):
'127.0.0.1'; port: 3306
2024-01-22T12:31:11.315910Z 0 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
2024-01-22T12:31:11.316011Z 0 [Note] Server socket created on IP:
'127.0.0.1'.
2024-01-22T12:31:11.327440Z 0 [Warning] Optional native table
'performance_schema'.'processlist' has the wrong structure or is missing.
2024-01-22T12:31:11.327996Z 0 [Note] Event Scheduler: Loaded 0 events
2024-01-22T12:31:11.328165Z 0 [Note] mysqld: ready for connections.
Version: '5.7.44'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution

I've done some digging on the errors, I managed to clean up some of the
InnoDB errors using innodb_force_recovery = 3 ...
Based on the docs though I did not push to recovery values higher than 3

Pointers or assistance would be very welcome.