Mobile versionCode: Select all
(base) raphy@raohy:~/.talos/openmetadata/mysql$ kubectl logs mysql-5cc7d75b8c-4cdbz
2025-11-07 11:35:41+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 9.5.0-1.el9 started.
2025-11-07 11:35:41+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2025-11-07 11:35:41+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 9.5.0-1.el9 started.
'/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'
2025-11-07T11:35:42.487493Z 0 [System] [MY-015015] [Server] MySQL Server - start.
2025-11-07T11:35:42.846264Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 9.5.0) starting as process 1
2025-11-07T11:35:42.846353Z 0 [System] [MY-015590] [Server] MySQL Server has access to 12 logical CPUs.
2025-11-07T11:35:42.846393Z 0 [System] [MY-015590] [Server] MySQL Server has access to 49306845184 bytes of physical memory.
2025-11-07T11:35:42.860421Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2025-11-07T11:35:43.081428Z 1 [ERROR] [MY-013090] [InnoDB] Unsupported redo log format (v0). The redo log was created before MySQL 5.7.9
2025-11-07T11:35:43.081504Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error.
2025-11-07T11:35:43.457054Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2025-11-07T11:35:43.457393Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2025-11-07T11:35:43.457461Z 0 [ERROR] [MY-010119] [Server] Aborting
2025-11-07T11:35:43.460580Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 9.5.0) MySQL Community Server - GPL.
2025-11-07T11:35:43.460643Z 0 [System] [MY-015016] [Server] MySQL Server - end.
(base) raphy@raohy:~/.talos/openmetadata/mysql$ nano mysql-deployment.yaml :
Code: Select all
# https://phoenixnap.com/kb/kubernetes-mysql
apiVersion: apps/v1
kind: Deployment
metadata:
name: mysql
spec:
selector:
matchLabels:
app: mysql
strategy:
type: Recreate
template:
metadata:
labels:
app: mysql
spec:
containers:
- image: mysql:9 # Understanding the Unsupported Redo Log Format Error:
# If you are upgrading from a version lower than 5.7.9, you must first upgrade to 5.7.9 or later before proceeding to MySQL 8.0.
name: mysql
env:
- name: MYSQL_ROOT_PASSWORD
valueFrom:
secretKeyRef:
name: mysql-secret
key: password
ports:
- containerPort: 3306
name: mysql
volumeMounts:
- name: mysql-persistent-storage
mountPath: /var/lib/mysql
volumes:
- name: mysql-persistent-storage
persistentVolumeClaim:
claimName: mysql-pv-claim
---
apiVersion: v1
kind: Service
metadata:
name: mysql
spec:
ports:
- port: 3306
selector:
app: mysql
Code: Select all
[InnoDB] Unsupported redo log format (v0). The redo log was created before MySQL 5.7.9
Wie vorgeschlagen habe ich versucht, die erste Version 5.7.44 von MySQL bereitzustellen:
Code: Select all
image: mysql:5.7.44
Code: Select all
(base) raphy@raohy:~/.talos/openmetadata/mysql$ kubectl get pods
NAME READY STATUS RESTARTS AGE
mysql-c97575f6-4gbll 0/1 CrashLoopBackOff 1 (2s ago) 8s
(base) raphy@raohy:~/.talos/openmetadata/mysql$ kubectl logs mysql-c97575f6-4gbll
2025-11-07 12:03:34+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.44-1.el7 started.
2025-11-07 12:03:34+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2025-11-07 12:03:34+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.44-1.el7 started.
'/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'
2025-11-07T12:03:35.339085Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2025-11-07T12:03:35.342003Z 0 [Note] mysqld (mysqld 5.7.44) starting as process 1 ...
2025-11-07T12:03:35.347139Z 0 [Note] InnoDB: PUNCH HOLE support available
2025-11-07T12:03:35.347184Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2025-11-07T12:03:35.347197Z 0 [Note] InnoDB: Uses event mutexes
2025-11-07T12:03:35.347201Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2025-11-07T12:03:35.347205Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2025-11-07T12:03:35.347209Z 0 [Note] InnoDB: Using Linux native AIO
2025-11-07T12:03:35.347610Z 0 [Note] InnoDB: Number of pools: 1
2025-11-07T12:03:35.347782Z 0 [Note] InnoDB: Using CPU crc32 instructions
2025-11-07T12:03:35.352246Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2025-11-07T12:03:35.365040Z 0 [Note] InnoDB: Completed initialization of buffer pool
2025-11-07T12:03:35.368813Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2025-11-07T12:03:35.381069Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4800!
2025-11-07 12:03:35 0x7fc96f5b7880 InnoDB: Assertion failure in thread 140503133419648 in file ut0ut.cc line 921
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
12:03:35 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68199 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
mysqld(my_print_stacktrace+0x3b)[0xf11c0b]
mysqld(handle_fatal_signal+0x486)[0x79f7d6]
/lib64/libpthread.so.0(+0xf8c0)[0x7fc96f1a08c0]
/lib64/libc.so.6(gsignal+0x37)[0x7fc96d4b3387]
/lib64/libc.so.6(abort+0x148)[0x7fc96d4b4a78]
mysqld[0x76f748]
mysqld(_ZN2ib5fatalD1Ev+0xfd)[0x10e97cd]
mysqld[0x11a14c2]
mysqld[0x11a1a0b]
mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x208)[0x11ad238]
mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xe4)[0x115b594]
mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x42d)[0x112a96d]
mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x15d)[0x10c892d]
mysqld[0x1090758]
mysqld(_Z34innobase_start_or_create_for_mysqlv+0x3996)[0x1094ea6]
mysqld[0xf5a89f]
mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x51)[0x7f2671]
mysqld[0xcf2c85]
mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0xcf8fb0]
mysqld[0x797cc4]
mysqld(_Z11mysqld_mainiPPc+0xa85)[0x79b4e5]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7fc96d49f555]
mysqld[0x78f154]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
