2022-09-03, 15:45
I had been running with a shared library instance for several years until running into a problem last week. I had mariadb running on docker / portainer inside of Open Media Vault. This worked great until recently when the container seems to have corrupted. I thought that it would be a good time to try to fully understand how to create containers rather than just following youtbube videos.
I created my docker container with this command:
docker run --name mariadb -v /srv/dev-disk-by-label-docker/appdata/mariadb:/var/lib/mysql -e MARIADB_USER=<redacted> --env MARIADB_PASSWORD=<redacted> -e MARIADB_ROOT_PASSWORD=<redacted> -p 3306:3306 -d mariadb:latest
Once I did that I could browse it using an sql browser so I know the port information is right. However, all of my kodi instances continue to crash as soon as I try to play a video.
2022-09-03 13:40:38+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.9.2+maria~ubu2204 started.
2022-09-03 13:40:38+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2022-09-03 13:40:38+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.9.2+maria~ubu2204 started.
2022-09-03 13:40:38+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
Warning: World-writable config file '/etc/mysql/my.cnf' is ignored
2022-09-03 13:40:39 0 [Note] mariadbd (server 10.9.2-MariaDB-1:10.9.2+maria~ubu2204) starting as process 1 ...
2022-09-03 13:40:39 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-09-03 13:40:39 0 [Note] InnoDB: Number of transaction pools: 1
2022-09-03 13:40:39 0 [Note] InnoDB: Using generic crc32 instructions
2022-09-03 13:40:39 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
2022-09-03 13:40:39 0 [Warning] mariadbd: io_uring_queue_init() failed with ENOSYS: check seccomp filters, and the kernel version (newer than 5.1 required)
2022-09-03 13:40:39 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF
2022-09-03 13:40:39 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2022-09-03 13:40:39 0 [Note] InnoDB: Completed initialization of buffer pool
2022-09-03 13:40:39 0 [Note] InnoDB: File system buffers for log disabled (block size=4096 bytes)
2022-09-03 13:40:39 0 [Note] InnoDB: 128 rollback segments are active.
2022-09-03 13:40:39 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2022-09-03 13:40:39 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2022-09-03 13:40:39 0 [Note] InnoDB: log sequence number 46667; transaction id 14
2022-09-03 13:40:39 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2022-09-03 13:40:39 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-09-03 13:40:39 0 [Note] InnoDB: Buffer pool(s) load completed at 220903 13:40:39
2022-09-03 13:40:39 0 [Note] Server socket created on IP: '0.0.0.0'.
2022-09-03 13:40:39 0 [Note] Server socket created on IP: '::'.
2022-09-03 13:40:39 0 [Note] mariadbd: ready for connections.
Version: '10.9.2-MariaDB-1:10.9.2+maria~ubu2204' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
2022-09-03 13:41:59 3 [Warning] IP address '192.168.1.207' could not be resolved: Name or service not known
This is the log for mariadb. I've done a lot of research on the error on the last line - some posts say that this is actually a harmless message, others disagree. Anyway, it seems that the way to get this to go away is to add skip-name-resolve to my.cnf. But where is that located? I tried it in /etc/mysql - no luck. Alternatively, others said that I could put a host entry into each kodi instance to make it go away.
Any help would be GREATLY appreciated.
I created my docker container with this command:
docker run --name mariadb -v /srv/dev-disk-by-label-docker/appdata/mariadb:/var/lib/mysql -e MARIADB_USER=<redacted> --env MARIADB_PASSWORD=<redacted> -e MARIADB_ROOT_PASSWORD=<redacted> -p 3306:3306 -d mariadb:latest
Once I did that I could browse it using an sql browser so I know the port information is right. However, all of my kodi instances continue to crash as soon as I try to play a video.
2022-09-03 13:40:38+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.9.2+maria~ubu2204 started.
2022-09-03 13:40:38+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2022-09-03 13:40:38+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.9.2+maria~ubu2204 started.
2022-09-03 13:40:38+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
Warning: World-writable config file '/etc/mysql/my.cnf' is ignored
2022-09-03 13:40:39 0 [Note] mariadbd (server 10.9.2-MariaDB-1:10.9.2+maria~ubu2204) starting as process 1 ...
2022-09-03 13:40:39 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-09-03 13:40:39 0 [Note] InnoDB: Number of transaction pools: 1
2022-09-03 13:40:39 0 [Note] InnoDB: Using generic crc32 instructions
2022-09-03 13:40:39 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
2022-09-03 13:40:39 0 [Warning] mariadbd: io_uring_queue_init() failed with ENOSYS: check seccomp filters, and the kernel version (newer than 5.1 required)
2022-09-03 13:40:39 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF
2022-09-03 13:40:39 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2022-09-03 13:40:39 0 [Note] InnoDB: Completed initialization of buffer pool
2022-09-03 13:40:39 0 [Note] InnoDB: File system buffers for log disabled (block size=4096 bytes)
2022-09-03 13:40:39 0 [Note] InnoDB: 128 rollback segments are active.
2022-09-03 13:40:39 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2022-09-03 13:40:39 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2022-09-03 13:40:39 0 [Note] InnoDB: log sequence number 46667; transaction id 14
2022-09-03 13:40:39 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2022-09-03 13:40:39 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-09-03 13:40:39 0 [Note] InnoDB: Buffer pool(s) load completed at 220903 13:40:39
2022-09-03 13:40:39 0 [Note] Server socket created on IP: '0.0.0.0'.
2022-09-03 13:40:39 0 [Note] Server socket created on IP: '::'.
2022-09-03 13:40:39 0 [Note] mariadbd: ready for connections.
Version: '10.9.2-MariaDB-1:10.9.2+maria~ubu2204' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
2022-09-03 13:41:59 3 [Warning] IP address '192.168.1.207' could not be resolved: Name or service not known
This is the log for mariadb. I've done a lot of research on the error on the last line - some posts say that this is actually a harmless message, others disagree. Anyway, it seems that the way to get this to go away is to add skip-name-resolve to my.cnf. But where is that located? I tried it in /etc/mysql - no luck. Alternatively, others said that I could put a host entry into each kodi instance to make it go away.
Any help would be GREATLY appreciated.