#1 Le 31/10/2023, à 10:52
- pti-jean
[Résolu] Pb avec MySql (mysql -u root -p) suite à une maj...
Bonjour,
J'ai un problème avec MySql:
$ mysql -u root -p
Enter password:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)J'ai un point de restauration où cette commande fonctionne, et suite à une mise à jour elle ne fonctionne plus.
Quand cela ne fonctionne plus... Si je fais:
$ sudo systemctl status mysql.service
× mysql.service - MySQL Community Server
Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2023-10-31 09:35:43 CET; 1min 54s ago
Process: 2561 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
Process: 2569 ExecStart=/usr/sbin/mysqld (code=exited, status=2)
Main PID: 2569 (code=exited, status=2)
Status: "Server startup in progress"
CPU: 635ms
oct. 31 09:35:42 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
oct. 31 09:35:42 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
oct. 31 09:35:42 Kubutnu systemd[1]: Failed to start MySQL Community Server.
oct. 31 09:35:43 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 14.
oct. 31 09:35:43 Kubutnu systemd[1]: Stopped MySQL Community Server.
oct. 31 09:35:43 Kubutnu systemd[1]: mysql.service: Start request repeated too quickly.
oct. 31 09:35:43 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
oct. 31 09:35:43 Kubutnu systemd[1]: Failed to start MySQL Community Server.$ sudo systemctl restart mysql.service
Job for mysql.service failed because the control process exited with error code.
See "systemctl status mysql.service" and "journalctl -xeu mysql.service" for details.$ journalctl -xeu mysql.service
oct. 31 09:35:07 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 1.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:35:07 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:35:07 Kubutnu systemd[1]: mysql.service: Consumed 4.622s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:35:07 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:35:08 Kubutnu mysqld[1328]: 2023-10-31T08:35:08.179688Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 1328
oct. 31 09:35:08 Kubutnu mysqld[1328]: 2023-10-31T08:35:08.245202Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:35:13 Kubutnu mysqld[1328]: 2023-10-31T08:35:13.053444Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 139943034590784
oct. 31 09:35:13 Kubutnu mysqld[1328]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:35:13 Kubutnu mysqld[1328]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:35:13 Kubutnu mysqld[1328]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:35:13 Kubutnu mysqld[1328]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:35:13 Kubutnu mysqld[1328]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:35:13 Kubutnu mysqld[1328]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:35:13 Kubutnu mysqld[1328]: InnoDB: about forcing recovery.
oct. 31 09:35:13 Kubutnu mysqld[1328]: 2023-10-31T08:35:13Z UTC - mysqld got signal 6 ;
oct. 31 09:35:13 Kubutnu mysqld[1328]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:35:13 Kubutnu mysqld[1328]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:35:13 Kubutnu mysqld[1328]: Thread pointer: 0x0
oct. 31 09:35:13 Kubutnu mysqld[1328]: Attempting backtrace. You can use the following information to find out
oct. 31 09:35:13 Kubutnu mysqld[1328]: where mysqld died. If you see no messages after this, something went
oct. 31 09:35:13 Kubutnu mysqld[1328]: terribly wrong...
oct. 31 09:35:13 Kubutnu mysqld[1328]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:35:13 Kubutnu mysqld[1328]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x560724fe6751]
oct. 31 09:35:13 Kubutnu mysqld[1328]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x56072460464c]
oct. 31 09:35:13 Kubutnu mysqld[1328]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x56072460477e]
oct. 31 09:35:13 Kubutnu mysqld[1328]: /usr/sbin/mysqld(my_abort()+0xe) [0x560724fdbe3e]
oct. 31 09:35:13 Kubutnu mysqld[1328]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x56072518ddc3]
oct. 31 09:35:13 Kubutnu mysqld[1328]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x56072529fda8]
oct. 31 09:35:13 Kubutnu mysqld[1328]: /usr/sbin/mysqld(+0x16e73ca) [0x5607250ee3ca]
oct. 31 09:35:13 Kubutnu mysqld[1328]: /usr/sbin/mysqld(+0x16da379) [0x5607250e1379]
oct. 31 09:35:13 Kubutnu mysqld[1328]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7f471bd8f253]
oct. 31 09:35:13 Kubutnu mysqld[1328]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7f471ba16ac3]
oct. 31 09:35:13 Kubutnu mysqld[1328]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7f471baa8a40]
oct. 31 09:35:13 Kubutnu mysqld[1328]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:35:13 Kubutnu mysqld[1328]: information that should help you find out what is causing the crash.
oct. 31 09:35:13 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:35:13 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:35:13 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:35:13 Kubutnu systemd[1]: mysql.service: Consumed 1.490s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:35:13 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 2.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:35:13 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:35:13 Kubutnu systemd[1]: mysql.service: Consumed 1.490s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:35:13 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:35:14 Kubutnu mysqld[1759]: 2023-10-31T08:35:14.037496Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 1759
oct. 31 09:35:14 Kubutnu mysqld[1759]: 2023-10-31T08:35:14.050311Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:35:14 Kubutnu mysqld[1759]: 2023-10-31T08:35:14.770464Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 140711752672832
oct. 31 09:35:14 Kubutnu mysqld[1759]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:35:14 Kubutnu mysqld[1759]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:35:14 Kubutnu mysqld[1759]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:35:14 Kubutnu mysqld[1759]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:35:14 Kubutnu mysqld[1759]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:35:14 Kubutnu mysqld[1759]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:35:14 Kubutnu mysqld[1759]: InnoDB: about forcing recovery.
oct. 31 09:35:14 Kubutnu mysqld[1759]: 2023-10-31T08:35:14Z UTC - mysqld got signal 6 ;
oct. 31 09:35:14 Kubutnu mysqld[1759]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:35:14 Kubutnu mysqld[1759]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:35:14 Kubutnu mysqld[1759]: Thread pointer: 0x0
oct. 31 09:35:14 Kubutnu mysqld[1759]: Attempting backtrace. You can use the following information to find out
oct. 31 09:35:14 Kubutnu mysqld[1759]: where mysqld died. If you see no messages after this, something went
oct. 31 09:35:14 Kubutnu mysqld[1759]: terribly wrong...
oct. 31 09:35:14 Kubutnu mysqld[1759]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:35:14 Kubutnu mysqld[1759]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x55dec903f751]
oct. 31 09:35:14 Kubutnu mysqld[1759]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x55dec865d64c]
oct. 31 09:35:14 Kubutnu mysqld[1759]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x55dec865d77e]
oct. 31 09:35:14 Kubutnu mysqld[1759]: /usr/sbin/mysqld(my_abort()+0xe) [0x55dec9034e3e]
oct. 31 09:35:14 Kubutnu mysqld[1759]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x55dec91e6dc3]
oct. 31 09:35:14 Kubutnu mysqld[1759]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x55dec92f8da8]
oct. 31 09:35:14 Kubutnu mysqld[1759]: /usr/sbin/mysqld(+0x16e73ca) [0x55dec91473ca]
oct. 31 09:35:14 Kubutnu mysqld[1759]: /usr/sbin/mysqld(+0x16da379) [0x55dec913a379]
oct. 31 09:35:14 Kubutnu mysqld[1759]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7ffa18031253]
oct. 31 09:35:14 Kubutnu mysqld[1759]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7ffa17cb8ac3]
oct. 31 09:35:14 Kubutnu mysqld[1759]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7ffa17d4aa40]
oct. 31 09:35:14 Kubutnu mysqld[1759]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:35:14 Kubutnu mysqld[1759]: information that should help you find out what is causing the crash.
oct. 31 09:35:14 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:35:14 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:35:14 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:35:15 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 3.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:35:15 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:35:15 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.journalctl -xeu mysql.service
oct. 31 09:35:15 Kubutnu mysqld[1967]: 2023-10-31T08:35:15.936404Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 1967
oct. 31 09:35:15 Kubutnu mysqld[1967]: 2023-10-31T08:35:15.969975Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:35:17 Kubutnu mysqld[1967]: 2023-10-31T08:35:17.312212Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 139685452076608
oct. 31 09:35:17 Kubutnu mysqld[1967]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:35:17 Kubutnu mysqld[1967]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:35:17 Kubutnu mysqld[1967]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:35:17 Kubutnu mysqld[1967]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:35:17 Kubutnu mysqld[1967]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:35:17 Kubutnu mysqld[1967]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:35:17 Kubutnu mysqld[1967]: InnoDB: about forcing recovery.
oct. 31 09:35:17 Kubutnu mysqld[1967]: 2023-10-31T08:35:17Z UTC - mysqld got signal 6 ;
oct. 31 09:35:17 Kubutnu mysqld[1967]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:35:17 Kubutnu mysqld[1967]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:35:17 Kubutnu mysqld[1967]: Thread pointer: 0x0
oct. 31 09:35:17 Kubutnu mysqld[1967]: Attempting backtrace. You can use the following information to find out
oct. 31 09:35:17 Kubutnu mysqld[1967]: where mysqld died. If you see no messages after this, something went
oct. 31 09:35:17 Kubutnu mysqld[1967]: terribly wrong...
oct. 31 09:35:17 Kubutnu mysqld[1967]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:35:17 Kubutnu mysqld[1967]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x55e3cd525751]
oct. 31 09:35:17 Kubutnu mysqld[1967]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x55e3ccb4364c]
oct. 31 09:35:17 Kubutnu mysqld[1967]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x55e3ccb4377e]
oct. 31 09:35:17 Kubutnu mysqld[1967]: /usr/sbin/mysqld(my_abort()+0xe) [0x55e3cd51ae3e]
oct. 31 09:35:17 Kubutnu mysqld[1967]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x55e3cd6ccdc3]
oct. 31 09:35:17 Kubutnu mysqld[1967]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x55e3cd7deda8]
oct. 31 09:35:17 Kubutnu mysqld[1967]: /usr/sbin/mysqld(+0x16e73ca) [0x55e3cd62d3ca]
oct. 31 09:35:17 Kubutnu mysqld[1967]: /usr/sbin/mysqld(+0x16da379) [0x55e3cd620379]
oct. 31 09:35:17 Kubutnu mysqld[1967]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7f0b1eb89253]
oct. 31 09:35:17 Kubutnu mysqld[1967]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7f0b1e810ac3]
oct. 31 09:35:17 Kubutnu mysqld[1967]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7f0b1e8a2a40]
oct. 31 09:35:17 Kubutnu mysqld[1967]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:35:17 Kubutnu mysqld[1967]: information that should help you find out what is causing the crash.
oct. 31 09:35:17 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:35:17 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:35:17 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:35:17 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 4.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:35:17 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:35:17 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:35:18 Kubutnu mysqld[2047]: 2023-10-31T08:35:18.360892Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 2047
oct. 31 09:35:18 Kubutnu mysqld[2047]: 2023-10-31T08:35:18.385799Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:35:21 Kubutnu mysqld[2047]: 2023-10-31T08:35:21.405723Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 140444440888896
oct. 31 09:35:21 Kubutnu mysqld[2047]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:35:21 Kubutnu mysqld[2047]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:35:21 Kubutnu mysqld[2047]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:35:21 Kubutnu mysqld[2047]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:35:21 Kubutnu mysqld[2047]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:35:21 Kubutnu mysqld[2047]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:35:21 Kubutnu mysqld[2047]: InnoDB: about forcing recovery.
oct. 31 09:35:21 Kubutnu mysqld[2047]: 2023-10-31T08:35:21Z UTC - mysqld got signal 6 ;
oct. 31 09:35:21 Kubutnu mysqld[2047]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:35:21 Kubutnu mysqld[2047]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:35:21 Kubutnu mysqld[2047]: Thread pointer: 0x0
oct. 31 09:35:21 Kubutnu mysqld[2047]: Attempting backtrace. You can use the following information to find out
oct. 31 09:35:21 Kubutnu mysqld[2047]: where mysqld died. If you see no messages after this, something went
oct. 31 09:35:21 Kubutnu mysqld[2047]: terribly wrong...
oct. 31 09:35:21 Kubutnu mysqld[2047]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:35:21 Kubutnu mysqld[2047]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x55e4f3fab751]
oct. 31 09:35:21 Kubutnu mysqld[2047]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x55e4f35c964c]
oct. 31 09:35:21 Kubutnu mysqld[2047]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x55e4f35c977e]
oct. 31 09:35:21 Kubutnu mysqld[2047]: /usr/sbin/mysqld(my_abort()+0xe) [0x55e4f3fa0e3e]
oct. 31 09:35:21 Kubutnu mysqld[2047]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x55e4f4152dc3]
oct. 31 09:35:21 Kubutnu mysqld[2047]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x55e4f4264da8]
oct. 31 09:35:21 Kubutnu mysqld[2047]: /usr/sbin/mysqld(+0x16e73ca) [0x55e4f40b33ca]
oct. 31 09:35:21 Kubutnu mysqld[2047]: /usr/sbin/mysqld(+0x16da379) [0x55e4f40a6379]
oct. 31 09:35:21 Kubutnu mysqld[2047]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7fbbd5fac253]
oct. 31 09:35:21 Kubutnu mysqld[2047]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7fbbd5c33ac3]
oct. 31 09:35:21 Kubutnu mysqld[2047]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7fbbd5cc5a40]
oct. 31 09:35:21 Kubutnu mysqld[2047]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:35:21 Kubutnu mysqld[2047]: information that should help you find out what is causing the crash.
oct. 31 09:35:21 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:35:21 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:35:21 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:35:21 Kubutnu systemd[1]: mysql.service: Consumed 1.971s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:35:21 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:35:21 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:35:21 Kubutnu systemd[1]: mysql.service: Consumed 1.971s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:35:21 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:35:23 Kubutnu mysqld[2162]: 2023-10-31T08:35:23.106332Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 2162
oct. 31 09:35:23 Kubutnu mysqld[2162]: 2023-10-31T08:35:23.388837Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:35:25 Kubutnu mysqld[2162]: 2023-10-31T08:35:25.462590Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 140636299912768
oct. 31 09:35:25 Kubutnu mysqld[2162]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:35:25 Kubutnu mysqld[2162]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:35:25 Kubutnu mysqld[2162]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:35:25 Kubutnu mysqld[2162]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:35:25 Kubutnu mysqld[2162]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:35:25 Kubutnu mysqld[2162]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:35:25 Kubutnu mysqld[2162]: InnoDB: about forcing recovery.
oct. 31 09:35:25 Kubutnu mysqld[2162]: 2023-10-31T08:35:25Z UTC - mysqld got signal 6 ;
oct. 31 09:35:25 Kubutnu mysqld[2162]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:35:25 Kubutnu mysqld[2162]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:35:25 Kubutnu mysqld[2162]: Thread pointer: 0x0
oct. 31 09:35:25 Kubutnu mysqld[2162]: Attempting backtrace. You can use the following information to find out
oct. 31 09:35:25 Kubutnu mysqld[2162]: where mysqld died. If you see no messages after this, something went
oct. 31 09:35:25 Kubutnu mysqld[2162]: terribly wrong...
oct. 31 09:35:25 Kubutnu mysqld[2162]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:35:25 Kubutnu mysqld[2162]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x55c38c8ec751]
oct. 31 09:35:25 Kubutnu mysqld[2162]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x55c38bf0a64c]
oct. 31 09:35:25 Kubutnu mysqld[2162]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x55c38bf0a77e]
oct. 31 09:35:25 Kubutnu mysqld[2162]: /usr/sbin/mysqld(my_abort()+0xe) [0x55c38c8e1e3e]
oct. 31 09:35:25 Kubutnu mysqld[2162]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x55c38ca93dc3]
oct. 31 09:35:25 Kubutnu mysqld[2162]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x55c38cba5da8]
oct. 31 09:35:25 Kubutnu mysqld[2162]: /usr/sbin/mysqld(+0x16e73ca) [0x55c38c9f43ca]
oct. 31 09:35:25 Kubutnu mysqld[2162]: /usr/sbin/mysqld(+0x16da379) [0x55c38c9e7379]
oct. 31 09:35:25 Kubutnu mysqld[2162]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7fe881ab2253]
oct. 31 09:35:25 Kubutnu mysqld[2162]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7fe881739ac3]
oct. 31 09:35:25 Kubutnu mysqld[2162]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7fe8817cba40]
oct. 31 09:35:25 Kubutnu mysqld[2162]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:35:25 Kubutnu mysqld[2162]: information that should help you find out what is causing the crash.
oct. 31 09:35:25 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:35:25 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:35:25 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:35:25 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 6.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:35:25 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:35:25 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:35:26 Kubutnu mysqld[2319]: 2023-10-31T08:35:26.795883Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 2319
oct. 31 09:35:26 Kubutnu mysqld[2319]: 2023-10-31T08:35:26.849443Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:35:28 Kubutnu mysqld[2319]: 2023-10-31T08:35:28.590614Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 140442875405888
oct. 31 09:35:28 Kubutnu mysqld[2319]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:35:28 Kubutnu mysqld[2319]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:35:28 Kubutnu mysqld[2319]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:35:28 Kubutnu mysqld[2319]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:35:28 Kubutnu mysqld[2319]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:35:28 Kubutnu mysqld[2319]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:35:28 Kubutnu mysqld[2319]: InnoDB: about forcing recovery.
oct. 31 09:35:28 Kubutnu mysqld[2319]: 2023-10-31T08:35:28Z UTC - mysqld got signal 6 ;
oct. 31 09:35:28 Kubutnu mysqld[2319]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:35:28 Kubutnu mysqld[2319]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:35:28 Kubutnu mysqld[2319]: Thread pointer: 0x0
oct. 31 09:35:28 Kubutnu mysqld[2319]: Attempting backtrace. You can use the following information to find out
oct. 31 09:35:28 Kubutnu mysqld[2319]: where mysqld died. If you see no messages after this, something went
oct. 31 09:35:28 Kubutnu mysqld[2319]: terribly wrong...
oct. 31 09:35:28 Kubutnu mysqld[2319]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:35:28 Kubutnu mysqld[2319]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x56063af44751]
oct. 31 09:35:28 Kubutnu mysqld[2319]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x56063a56264c]
oct. 31 09:35:28 Kubutnu mysqld[2319]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x56063a56277e]
oct. 31 09:35:28 Kubutnu mysqld[2319]: /usr/sbin/mysqld(my_abort()+0xe) [0x56063af39e3e]
oct. 31 09:35:28 Kubutnu mysqld[2319]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x56063b0ebdc3]
oct. 31 09:35:28 Kubutnu mysqld[2319]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x56063b1fdda8]
oct. 31 09:35:28 Kubutnu mysqld[2319]: /usr/sbin/mysqld(+0x16e73ca) [0x56063b04c3ca]
oct. 31 09:35:28 Kubutnu mysqld[2319]: /usr/sbin/mysqld(+0x16da379) [0x56063b03f379]
oct. 31 09:35:28 Kubutnu mysqld[2319]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7fbb7ccab253]
oct. 31 09:35:28 Kubutnu mysqld[2319]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7fbb7c932ac3]
oct. 31 09:35:28 Kubutnu mysqld[2319]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7fbb7c9c4a40]
oct. 31 09:35:28 Kubutnu mysqld[2319]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:35:28 Kubutnu mysqld[2319]: information that should help you find out what is causing the crash.
oct. 31 09:35:28 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:35:28 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:35:28 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:35:29 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 7.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:35:29 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:35:29 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:35:29 Kubutnu mysqld[2354]: 2023-10-31T08:35:29.829719Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 2354
oct. 31 09:35:29 Kubutnu mysqld[2354]: 2023-10-31T08:35:29.854414Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:35:31 Kubutnu mysqld[2354]: 2023-10-31T08:35:31.179766Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 140115300238912
oct. 31 09:35:31 Kubutnu mysqld[2354]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:35:31 Kubutnu mysqld[2354]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:35:31 Kubutnu mysqld[2354]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:35:31 Kubutnu mysqld[2354]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:35:31 Kubutnu mysqld[2354]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:35:31 Kubutnu mysqld[2354]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:35:31 Kubutnu mysqld[2354]: InnoDB: about forcing recovery.
oct. 31 09:35:31 Kubutnu mysqld[2354]: 2023-10-31T08:35:31Z UTC - mysqld got signal 6 ;
oct. 31 09:35:31 Kubutnu mysqld[2354]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:35:31 Kubutnu mysqld[2354]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:35:31 Kubutnu mysqld[2354]: Thread pointer: 0x0
oct. 31 09:35:31 Kubutnu mysqld[2354]: Attempting backtrace. You can use the following information to find out
oct. 31 09:35:31 Kubutnu mysqld[2354]: where mysqld died. If you see no messages after this, something went
oct. 31 09:35:31 Kubutnu mysqld[2354]: terribly wrong...
oct. 31 09:35:31 Kubutnu mysqld[2354]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:35:31 Kubutnu mysqld[2354]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x55c98a77a751]
oct. 31 09:35:31 Kubutnu mysqld[2354]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x55c989d9864c]
oct. 31 09:35:31 Kubutnu mysqld[2354]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x55c989d9877e]
oct. 31 09:35:31 Kubutnu mysqld[2354]: /usr/sbin/mysqld(my_abort()+0xe) [0x55c98a76fe3e]
oct. 31 09:35:31 Kubutnu mysqld[2354]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x55c98a921dc3]
oct. 31 09:35:31 Kubutnu mysqld[2354]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x55c98aa33da8]
oct. 31 09:35:31 Kubutnu mysqld[2354]: /usr/sbin/mysqld(+0x16e73ca) [0x55c98a8823ca]
oct. 31 09:35:31 Kubutnu mysqld[2354]: /usr/sbin/mysqld(+0x16da379) [0x55c98a875379]
oct. 31 09:35:31 Kubutnu mysqld[2354]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7f6f37ae7253]
oct. 31 09:35:31 Kubutnu mysqld[2354]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7f6f3776eac3]
oct. 31 09:35:31 Kubutnu mysqld[2354]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7f6f37800a40]
oct. 31 09:35:31 Kubutnu mysqld[2354]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:35:31 Kubutnu mysqld[2354]: information that should help you find out what is causing the crash.
oct. 31 09:35:31 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:35:31 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:35:31 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:35:31 Kubutnu systemd[1]: mysql.service: Consumed 1.056s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:35:31 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 8.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:35:31 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:35:31 Kubutnu systemd[1]: mysql.service: Consumed 1.056s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:35:31 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:35:32 Kubutnu mysqld[2390]: 2023-10-31T08:35:32.220041Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 2390
oct. 31 09:35:32 Kubutnu mysqld[2390]: 2023-10-31T08:35:32.261361Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:35:34 Kubutnu mysqld[2390]: 2023-10-31T08:35:34.509805Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 139842373539392
oct. 31 09:35:34 Kubutnu mysqld[2390]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:35:34 Kubutnu mysqld[2390]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:35:34 Kubutnu mysqld[2390]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:35:34 Kubutnu mysqld[2390]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:35:34 Kubutnu mysqld[2390]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:35:34 Kubutnu mysqld[2390]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:35:34 Kubutnu mysqld[2390]: InnoDB: about forcing recovery.
oct. 31 09:35:34 Kubutnu mysqld[2390]: 2023-10-31T08:35:34Z UTC - mysqld got signal 6 ;
oct. 31 09:35:34 Kubutnu mysqld[2390]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:35:34 Kubutnu mysqld[2390]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:35:34 Kubutnu mysqld[2390]: Thread pointer: 0x0
oct. 31 09:35:34 Kubutnu mysqld[2390]: Attempting backtrace. You can use the following information to find out
oct. 31 09:35:34 Kubutnu mysqld[2390]: where mysqld died. If you see no messages after this, something went
oct. 31 09:35:34 Kubutnu mysqld[2390]: terribly wrong...
oct. 31 09:35:34 Kubutnu mysqld[2390]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:35:34 Kubutnu mysqld[2390]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x55894a02a751]
oct. 31 09:35:34 Kubutnu mysqld[2390]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x55894964864c]
oct. 31 09:35:34 Kubutnu mysqld[2390]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x55894964877e]
oct. 31 09:35:34 Kubutnu mysqld[2390]: /usr/sbin/mysqld(my_abort()+0xe) [0x55894a01fe3e]
oct. 31 09:35:34 Kubutnu mysqld[2390]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x55894a1d1dc3]
oct. 31 09:35:34 Kubutnu mysqld[2390]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x55894a2e3da8]
oct. 31 09:35:34 Kubutnu mysqld[2390]: /usr/sbin/mysqld(+0x16e73ca) [0x55894a1323ca]
oct. 31 09:35:34 Kubutnu mysqld[2390]: /usr/sbin/mysqld(+0x16da379) [0x55894a125379]
oct. 31 09:35:34 Kubutnu mysqld[2390]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7f2fad80b253]
oct. 31 09:35:34 Kubutnu mysqld[2390]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7f2fad492ac3]
oct. 31 09:35:34 Kubutnu mysqld[2390]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7f2fad524a40]
oct. 31 09:35:34 Kubutnu mysqld[2390]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:35:34 Kubutnu mysqld[2390]: information that should help you find out what is causing the crash.
oct. 31 09:35:34 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:35:34 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:35:34 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:35:34 Kubutnu systemd[1]: mysql.service: Consumed 2.721s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:35:34 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 9.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:35:34 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:35:34 Kubutnu systemd[1]: mysql.service: Consumed 2.721s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:35:34 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:35:35 Kubutnu mysqld[2420]: 2023-10-31T08:35:35.480398Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 2420
oct. 31 09:35:35 Kubutnu mysqld[2420]: 2023-10-31T08:35:35.492174Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:35:36 Kubutnu mysqld[2420]: 2023-10-31T08:35:36.850881Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 140236607440448
oct. 31 09:35:36 Kubutnu mysqld[2420]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:35:36 Kubutnu mysqld[2420]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:35:36 Kubutnu mysqld[2420]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:35:36 Kubutnu mysqld[2420]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:35:36 Kubutnu mysqld[2420]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:35:36 Kubutnu mysqld[2420]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:35:36 Kubutnu mysqld[2420]: InnoDB: about forcing recovery.
oct. 31 09:35:36 Kubutnu mysqld[2420]: 2023-10-31T08:35:36Z UTC - mysqld got signal 6 ;
oct. 31 09:35:36 Kubutnu mysqld[2420]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:35:36 Kubutnu mysqld[2420]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:35:36 Kubutnu mysqld[2420]: Thread pointer: 0x0
oct. 31 09:35:36 Kubutnu mysqld[2420]: Attempting backtrace. You can use the following information to find out
oct. 31 09:35:36 Kubutnu mysqld[2420]: where mysqld died. If you see no messages after this, something went
oct. 31 09:35:36 Kubutnu mysqld[2420]: terribly wrong...
oct. 31 09:35:36 Kubutnu mysqld[2420]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:35:36 Kubutnu mysqld[2420]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x55a56f2e9751]
oct. 31 09:35:36 Kubutnu mysqld[2420]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x55a56e90764c]
oct. 31 09:35:36 Kubutnu mysqld[2420]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x55a56e90777e]
oct. 31 09:35:36 Kubutnu mysqld[2420]: /usr/sbin/mysqld(my_abort()+0xe) [0x55a56f2dee3e]
oct. 31 09:35:36 Kubutnu mysqld[2420]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x55a56f490dc3]
oct. 31 09:35:36 Kubutnu mysqld[2420]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x55a56f5a2da8]
oct. 31 09:35:36 Kubutnu mysqld[2420]: /usr/sbin/mysqld(+0x16e73ca) [0x55a56f3f13ca]
oct. 31 09:35:36 Kubutnu mysqld[2420]: /usr/sbin/mysqld(+0x16da379) [0x55a56f3e4379]
oct. 31 09:35:36 Kubutnu mysqld[2420]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7f8b72240253]
oct. 31 09:35:36 Kubutnu mysqld[2420]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7f8b71ec7ac3]
oct. 31 09:35:36 Kubutnu mysqld[2420]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7f8b71f59a40]
oct. 31 09:35:36 Kubutnu mysqld[2420]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:35:36 Kubutnu mysqld[2420]: information that should help you find out what is causing the crash.
oct. 31 09:35:37 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:35:37 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:35:37 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:35:37 Kubutnu systemd[1]: mysql.service: Consumed 1.144s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:35:37 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 10.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:35:37 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:35:37 Kubutnu systemd[1]: mysql.service: Consumed 1.144s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:35:37 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:35:37 Kubutnu mysqld[2454]: 2023-10-31T08:35:37.798613Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 2454
oct. 31 09:35:37 Kubutnu mysqld[2454]: 2023-10-31T08:35:37.809969Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:35:38 Kubutnu mysqld[2454]: 2023-10-31T08:35:38.278116Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 139655376512576
oct. 31 09:35:38 Kubutnu mysqld[2454]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:35:38 Kubutnu mysqld[2454]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:35:38 Kubutnu mysqld[2454]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:35:38 Kubutnu mysqld[2454]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:35:38 Kubutnu mysqld[2454]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:35:38 Kubutnu mysqld[2454]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:35:38 Kubutnu mysqld[2454]: InnoDB: about forcing recovery.
oct. 31 09:35:38 Kubutnu mysqld[2454]: 2023-10-31T08:35:38Z UTC - mysqld got signal 6 ;
oct. 31 09:35:38 Kubutnu mysqld[2454]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:35:38 Kubutnu mysqld[2454]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:35:38 Kubutnu mysqld[2454]: Thread pointer: 0x0
oct. 31 09:35:38 Kubutnu mysqld[2454]: Attempting backtrace. You can use the following information to find out
oct. 31 09:35:38 Kubutnu mysqld[2454]: where mysqld died. If you see no messages after this, something went
oct. 31 09:35:38 Kubutnu mysqld[2454]: terribly wrong...
oct. 31 09:35:38 Kubutnu mysqld[2454]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:35:38 Kubutnu mysqld[2454]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x5590d566b751]
oct. 31 09:35:38 Kubutnu mysqld[2454]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x5590d4c8964c]
oct. 31 09:35:38 Kubutnu mysqld[2454]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x5590d4c8977e]
oct. 31 09:35:38 Kubutnu mysqld[2454]: /usr/sbin/mysqld(my_abort()+0xe) [0x5590d5660e3e]
oct. 31 09:35:38 Kubutnu mysqld[2454]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x5590d5812dc3]
oct. 31 09:35:38 Kubutnu mysqld[2454]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x5590d5924da8]
oct. 31 09:35:38 Kubutnu mysqld[2454]: /usr/sbin/mysqld(+0x16e73ca) [0x5590d57733ca]
oct. 31 09:35:38 Kubutnu mysqld[2454]: /usr/sbin/mysqld(+0x16da379) [0x5590d5766379]
oct. 31 09:35:38 Kubutnu mysqld[2454]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7f041e13e253]
oct. 31 09:35:38 Kubutnu mysqld[2454]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7f041ddc5ac3]
oct. 31 09:35:38 Kubutnu mysqld[2454]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7f041de57a40]
oct. 31 09:35:38 Kubutnu mysqld[2454]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:35:38 Kubutnu mysqld[2454]: information that should help you find out what is causing the crash.
oct. 31 09:35:38 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:35:38 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:35:38 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:35:38 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 11.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:35:38 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:35:38 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:35:39 Kubutnu mysqld[2488]: 2023-10-31T08:35:39.039013Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 2488
oct. 31 09:35:39 Kubutnu mysqld[2488]: 2023-10-31T08:35:39.055652Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:35:39 Kubutnu mysqld[2488]: 2023-10-31T08:35:39.570833Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 139639062537792
oct. 31 09:35:39 Kubutnu mysqld[2488]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:35:39 Kubutnu mysqld[2488]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:35:39 Kubutnu mysqld[2488]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:35:39 Kubutnu mysqld[2488]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:35:39 Kubutnu mysqld[2488]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:35:39 Kubutnu mysqld[2488]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:35:39 Kubutnu mysqld[2488]: InnoDB: about forcing recovery.
oct. 31 09:35:39 Kubutnu mysqld[2488]: 2023-10-31T08:35:39Z UTC - mysqld got signal 6 ;
oct. 31 09:35:39 Kubutnu mysqld[2488]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:35:39 Kubutnu mysqld[2488]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:35:39 Kubutnu mysqld[2488]: Thread pointer: 0x0
oct. 31 09:35:39 Kubutnu mysqld[2488]: Attempting backtrace. You can use the following information to find out
oct. 31 09:35:39 Kubutnu mysqld[2488]: where mysqld died. If you see no messages after this, something went
oct. 31 09:35:39 Kubutnu mysqld[2488]: terribly wrong...
oct. 31 09:35:39 Kubutnu mysqld[2488]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:35:39 Kubutnu mysqld[2488]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x5620e00f5751]
oct. 31 09:35:39 Kubutnu mysqld[2488]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x5620df71364c]
oct. 31 09:35:39 Kubutnu mysqld[2488]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x5620df71377e]
oct. 31 09:35:39 Kubutnu mysqld[2488]: /usr/sbin/mysqld(my_abort()+0xe) [0x5620e00eae3e]
oct. 31 09:35:39 Kubutnu mysqld[2488]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x5620e029cdc3]
oct. 31 09:35:39 Kubutnu mysqld[2488]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x5620e03aeda8]
oct. 31 09:35:39 Kubutnu mysqld[2488]: /usr/sbin/mysqld(+0x16e73ca) [0x5620e01fd3ca]
oct. 31 09:35:39 Kubutnu mysqld[2488]: /usr/sbin/mysqld(+0x16da379) [0x5620e01f0379]
oct. 31 09:35:39 Kubutnu mysqld[2488]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7f0051b06253]
oct. 31 09:35:39 Kubutnu mysqld[2488]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7f005178dac3]
oct. 31 09:35:39 Kubutnu mysqld[2488]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7f005181fa40]
oct. 31 09:35:39 Kubutnu mysqld[2488]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:35:39 Kubutnu mysqld[2488]: information that should help you find out what is causing the crash.
oct. 31 09:35:39 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:35:39 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:35:39 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:35:39 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 12.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:35:39 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:35:39 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:35:40 Kubutnu mysqld[2532]: 2023-10-31T08:35:40.245041Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 2532
oct. 31 09:35:40 Kubutnu mysqld[2532]: 2023-10-31T08:35:40.255581Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:35:41 Kubutnu mysqld[2532]: 2023-10-31T08:35:41.541690Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 140104718874176
oct. 31 09:35:41 Kubutnu mysqld[2532]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:35:41 Kubutnu mysqld[2532]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:35:41 Kubutnu mysqld[2532]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:35:41 Kubutnu mysqld[2532]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:35:41 Kubutnu mysqld[2532]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:35:41 Kubutnu mysqld[2532]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:35:41 Kubutnu mysqld[2532]: InnoDB: about forcing recovery.
oct. 31 09:35:41 Kubutnu mysqld[2532]: 2023-10-31T08:35:41Z UTC - mysqld got signal 6 ;
oct. 31 09:35:41 Kubutnu mysqld[2532]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:35:41 Kubutnu mysqld[2532]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:35:41 Kubutnu mysqld[2532]: Thread pointer: 0x0
oct. 31 09:35:41 Kubutnu mysqld[2532]: Attempting backtrace. You can use the following information to find out
oct. 31 09:35:41 Kubutnu mysqld[2532]: where mysqld died. If you see no messages after this, something went
oct. 31 09:35:41 Kubutnu mysqld[2532]: terribly wrong...
oct. 31 09:35:41 Kubutnu mysqld[2532]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:35:41 Kubutnu mysqld[2532]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x5628893de751]
oct. 31 09:35:41 Kubutnu mysqld[2532]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x5628889fc64c]
oct. 31 09:35:41 Kubutnu mysqld[2532]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x5628889fc77e]
oct. 31 09:35:41 Kubutnu mysqld[2532]: /usr/sbin/mysqld(my_abort()+0xe) [0x5628893d3e3e]
oct. 31 09:35:41 Kubutnu mysqld[2532]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x562889585dc3]
oct. 31 09:35:41 Kubutnu mysqld[2532]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x562889697da8]
oct. 31 09:35:41 Kubutnu mysqld[2532]: /usr/sbin/mysqld(+0x16e73ca) [0x5628894e63ca]
oct. 31 09:35:41 Kubutnu mysqld[2532]: /usr/sbin/mysqld(+0x16da379) [0x5628894d9379]
oct. 31 09:35:41 Kubutnu mysqld[2532]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7f6cc1420253]
oct. 31 09:35:41 Kubutnu mysqld[2532]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7f6cc10a7ac3]
oct. 31 09:35:41 Kubutnu mysqld[2532]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7f6cc1139a40]
oct. 31 09:35:41 Kubutnu mysqld[2532]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:35:41 Kubutnu mysqld[2532]: information that should help you find out what is causing the crash.
oct. 31 09:35:41 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:35:41 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:35:41 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:35:41 Kubutnu systemd[1]: mysql.service: Consumed 2.364s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:35:41 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 13.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:35:41 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:35:41 Kubutnu systemd[1]: mysql.service: Consumed 2.364s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:35:41 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:35:42 Kubutnu mysqld[2569]: 2023-10-31T08:35:42.178544Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 2569
oct. 31 09:35:42 Kubutnu mysqld[2569]: 2023-10-31T08:35:42.188608Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:35:42 Kubutnu mysqld[2569]: 2023-10-31T08:35:42.598414Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 140496809780800
oct. 31 09:35:42 Kubutnu mysqld[2569]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:35:42 Kubutnu mysqld[2569]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:35:42 Kubutnu mysqld[2569]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:35:42 Kubutnu mysqld[2569]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:35:42 Kubutnu mysqld[2569]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:35:42 Kubutnu mysqld[2569]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:35:42 Kubutnu mysqld[2569]: InnoDB: about forcing recovery.
oct. 31 09:35:42 Kubutnu mysqld[2569]: 2023-10-31T08:35:42Z UTC - mysqld got signal 6 ;
oct. 31 09:35:42 Kubutnu mysqld[2569]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:35:42 Kubutnu mysqld[2569]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:35:42 Kubutnu mysqld[2569]: Thread pointer: 0x0
oct. 31 09:35:42 Kubutnu mysqld[2569]: Attempting backtrace. You can use the following information to find out
oct. 31 09:35:42 Kubutnu mysqld[2569]: where mysqld died. If you see no messages after this, something went
oct. 31 09:35:42 Kubutnu mysqld[2569]: terribly wrong...
oct. 31 09:35:42 Kubutnu mysqld[2569]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:35:42 Kubutnu mysqld[2569]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x559f1b97b751]
oct. 31 09:35:42 Kubutnu mysqld[2569]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x559f1af9964c]
oct. 31 09:35:42 Kubutnu mysqld[2569]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x559f1af9977e]
oct. 31 09:35:42 Kubutnu mysqld[2569]: /usr/sbin/mysqld(my_abort()+0xe) [0x559f1b970e3e]
oct. 31 09:35:42 Kubutnu mysqld[2569]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x559f1bb22dc3]
oct. 31 09:35:42 Kubutnu mysqld[2569]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x559f1bc34da8]
oct. 31 09:35:42 Kubutnu mysqld[2569]: /usr/sbin/mysqld(+0x16e73ca) [0x559f1ba833ca]
oct. 31 09:35:42 Kubutnu mysqld[2569]: /usr/sbin/mysqld(+0x16da379) [0x559f1ba76379]
oct. 31 09:35:42 Kubutnu mysqld[2569]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7fc80cec6253]
oct. 31 09:35:42 Kubutnu mysqld[2569]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7fc80cb4dac3]
oct. 31 09:35:42 Kubutnu mysqld[2569]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7fc80cbdfa40]
oct. 31 09:35:42 Kubutnu mysqld[2569]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:35:42 Kubutnu mysqld[2569]: information that should help you find out what is causing the crash.
oct. 31 09:35:42 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:35:42 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:35:42 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:35:43 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 14.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:35:43 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:35:43 Kubutnu systemd[1]: mysql.service: Start request repeated too quickly.
oct. 31 09:35:43 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:35:43 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:38:15 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:38:15 Kubutnu mysqld[2784]: 2023-10-31T08:38:15.692649Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 2784
oct. 31 09:38:15 Kubutnu mysqld[2784]: 2023-10-31T08:38:15.703972Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:38:23 Kubutnu mysqld[2784]: 2023-10-31T08:38:23.870407Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 139890834531904
oct. 31 09:38:23 Kubutnu mysqld[2784]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:38:23 Kubutnu mysqld[2784]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:38:23 Kubutnu mysqld[2784]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:38:23 Kubutnu mysqld[2784]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:38:23 Kubutnu mysqld[2784]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:38:23 Kubutnu mysqld[2784]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:38:23 Kubutnu mysqld[2784]: InnoDB: about forcing recovery.
oct. 31 09:38:23 Kubutnu mysqld[2784]: 2023-10-31T08:38:23Z UTC - mysqld got signal 6 ;
oct. 31 09:38:23 Kubutnu mysqld[2784]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:38:23 Kubutnu mysqld[2784]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:38:23 Kubutnu mysqld[2784]: Thread pointer: 0x0
oct. 31 09:38:23 Kubutnu mysqld[2784]: Attempting backtrace. You can use the following information to find out
oct. 31 09:38:23 Kubutnu mysqld[2784]: where mysqld died. If you see no messages after this, something went
oct. 31 09:38:23 Kubutnu mysqld[2784]: terribly wrong...
oct. 31 09:38:23 Kubutnu mysqld[2784]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:38:23 Kubutnu mysqld[2784]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x556cca44b751]
oct. 31 09:38:23 Kubutnu mysqld[2784]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x556cc9a6964c]
oct. 31 09:38:23 Kubutnu mysqld[2784]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x556cc9a6977e]
oct. 31 09:38:23 Kubutnu mysqld[2784]: /usr/sbin/mysqld(my_abort()+0xe) [0x556cca440e3e]
oct. 31 09:38:23 Kubutnu mysqld[2784]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x556cca5f2dc3]
oct. 31 09:38:23 Kubutnu mysqld[2784]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x556cca704da8]
oct. 31 09:38:23 Kubutnu mysqld[2784]: /usr/sbin/mysqld(+0x16e73ca) [0x556cca5533ca]
oct. 31 09:38:23 Kubutnu mysqld[2784]: /usr/sbin/mysqld(+0x16da379) [0x556cca546379]
oct. 31 09:38:23 Kubutnu mysqld[2784]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7f3af619f253]
oct. 31 09:38:23 Kubutnu mysqld[2784]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7f3af5e26ac3]
oct. 31 09:38:23 Kubutnu mysqld[2784]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7f3af5eb8a40]
oct. 31 09:38:23 Kubutnu mysqld[2784]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:38:23 Kubutnu mysqld[2784]: information that should help you find out what is causing the crash.
oct. 31 09:38:23 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:38:23 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:38:23 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:38:23 Kubutnu systemd[1]: mysql.service: Consumed 16.352s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:38:24 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 1.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:38:24 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:38:24 Kubutnu systemd[1]: mysql.service: Consumed 16.352s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:38:24 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:38:24 Kubutnu mysqld[2817]: 2023-10-31T08:38:24.550045Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 2817
oct. 31 09:38:24 Kubutnu mysqld[2817]: 2023-10-31T08:38:24.559860Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:38:24 Kubutnu mysqld[2817]: 2023-10-31T08:38:24.789615Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 140290783376960
oct. 31 09:38:24 Kubutnu mysqld[2817]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:38:24 Kubutnu mysqld[2817]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:38:24 Kubutnu mysqld[2817]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:38:24 Kubutnu mysqld[2817]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:38:24 Kubutnu mysqld[2817]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:38:24 Kubutnu mysqld[2817]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:38:24 Kubutnu mysqld[2817]: InnoDB: about forcing recovery.
oct. 31 09:38:24 Kubutnu mysqld[2817]: 2023-10-31T08:38:24Z UTC - mysqld got signal 6 ;
oct. 31 09:38:24 Kubutnu mysqld[2817]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:38:24 Kubutnu mysqld[2817]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:38:24 Kubutnu mysqld[2817]: Thread pointer: 0x0
oct. 31 09:38:24 Kubutnu mysqld[2817]: Attempting backtrace. You can use the following information to find out
oct. 31 09:38:24 Kubutnu mysqld[2817]: where mysqld died. If you see no messages after this, something went
oct. 31 09:38:24 Kubutnu mysqld[2817]: terribly wrong...
oct. 31 09:38:24 Kubutnu mysqld[2817]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:38:24 Kubutnu mysqld[2817]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x562755bb0751]
oct. 31 09:38:24 Kubutnu mysqld[2817]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x5627551ce64c]
oct. 31 09:38:24 Kubutnu mysqld[2817]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x5627551ce77e]
oct. 31 09:38:24 Kubutnu mysqld[2817]: /usr/sbin/mysqld(my_abort()+0xe) [0x562755ba5e3e]
oct. 31 09:38:24 Kubutnu mysqld[2817]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x562755d57dc3]
oct. 31 09:38:24 Kubutnu mysqld[2817]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x562755e69da8]
oct. 31 09:38:24 Kubutnu mysqld[2817]: /usr/sbin/mysqld(+0x16e73ca) [0x562755cb83ca]
oct. 31 09:38:24 Kubutnu mysqld[2817]: /usr/sbin/mysqld(+0x16da379) [0x562755cab379]
oct. 31 09:38:24 Kubutnu mysqld[2817]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7f98134b3253]
oct. 31 09:38:24 Kubutnu mysqld[2817]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7f981313aac3]
oct. 31 09:38:24 Kubutnu mysqld[2817]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7f98131cca40]
oct. 31 09:38:24 Kubutnu mysqld[2817]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:38:24 Kubutnu mysqld[2817]: information that should help you find out what is causing the crash.
oct. 31 09:38:24 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:38:24 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:38:24 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:38:25 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 2.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:38:25 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:38:25 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:38:25 Kubutnu mysqld[2847]: 2023-10-31T08:38:25.947867Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 2847
oct. 31 09:38:25 Kubutnu mysqld[2847]: 2023-10-31T08:38:25.958180Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:38:27 Kubutnu mysqld[2847]: 2023-10-31T08:38:27.875517Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 140333519459904
oct. 31 09:38:27 Kubutnu mysqld[2847]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:38:27 Kubutnu mysqld[2847]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:38:27 Kubutnu mysqld[2847]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:38:27 Kubutnu mysqld[2847]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:38:27 Kubutnu mysqld[2847]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:38:27 Kubutnu mysqld[2847]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:38:27 Kubutnu mysqld[2847]: InnoDB: about forcing recovery.
oct. 31 09:38:27 Kubutnu mysqld[2847]: 2023-10-31T08:38:27Z UTC - mysqld got signal 6 ;
oct. 31 09:38:27 Kubutnu mysqld[2847]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:38:27 Kubutnu mysqld[2847]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:38:27 Kubutnu mysqld[2847]: Thread pointer: 0x0
oct. 31 09:38:27 Kubutnu mysqld[2847]: Attempting backtrace. You can use the following information to find out
oct. 31 09:38:27 Kubutnu mysqld[2847]: where mysqld died. If you see no messages after this, something went
oct. 31 09:38:27 Kubutnu mysqld[2847]: terribly wrong...
oct. 31 09:38:27 Kubutnu mysqld[2847]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:38:27 Kubutnu mysqld[2847]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x5653377c2751]
oct. 31 09:38:27 Kubutnu mysqld[2847]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x565336de064c]
oct. 31 09:38:27 Kubutnu mysqld[2847]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x565336de077e]
oct. 31 09:38:27 Kubutnu mysqld[2847]: /usr/sbin/mysqld(my_abort()+0xe) [0x5653377b7e3e]
oct. 31 09:38:27 Kubutnu mysqld[2847]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x565337969dc3]
oct. 31 09:38:27 Kubutnu mysqld[2847]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x565337a7bda8]
oct. 31 09:38:27 Kubutnu mysqld[2847]: /usr/sbin/mysqld(+0x16e73ca) [0x5653378ca3ca]
oct. 31 09:38:27 Kubutnu mysqld[2847]: /usr/sbin/mysqld(+0x16da379) [0x5653378bd379]
oct. 31 09:38:27 Kubutnu mysqld[2847]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7fa2028c1253]
oct. 31 09:38:27 Kubutnu mysqld[2847]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7fa202548ac3]
oct. 31 09:38:27 Kubutnu mysqld[2847]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7fa2025daa40]
oct. 31 09:38:27 Kubutnu mysqld[2847]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:38:27 Kubutnu mysqld[2847]: information that should help you find out what is causing the crash.
oct. 31 09:38:27 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:38:27 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:38:27 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:38:27 Kubutnu systemd[1]: mysql.service: Consumed 3.781s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:38:28 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 3.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:38:28 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:38:28 Kubutnu systemd[1]: mysql.service: Consumed 3.781s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:38:28 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:38:28 Kubutnu mysqld[2875]: 2023-10-31T08:38:28.952218Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 2875
oct. 31 09:38:28 Kubutnu mysqld[2875]: 2023-10-31T08:38:28.962477Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:38:30 Kubutnu mysqld[2875]: 2023-10-31T08:38:30.870635Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 139639846807104
oct. 31 09:38:30 Kubutnu mysqld[2875]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:38:30 Kubutnu mysqld[2875]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:38:30 Kubutnu mysqld[2875]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:38:30 Kubutnu mysqld[2875]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:38:30 Kubutnu mysqld[2875]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:38:30 Kubutnu mysqld[2875]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:38:30 Kubutnu mysqld[2875]: InnoDB: about forcing recovery.
oct. 31 09:38:30 Kubutnu mysqld[2875]: 2023-10-31T08:38:30Z UTC - mysqld got signal 6 ;
oct. 31 09:38:30 Kubutnu mysqld[2875]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:38:30 Kubutnu mysqld[2875]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:38:30 Kubutnu mysqld[2875]: Thread pointer: 0x0
oct. 31 09:38:30 Kubutnu mysqld[2875]: Attempting backtrace. You can use the following information to find out
oct. 31 09:38:30 Kubutnu mysqld[2875]: where mysqld died. If you see no messages after this, something went
oct. 31 09:38:30 Kubutnu mysqld[2875]: terribly wrong...
oct. 31 09:38:30 Kubutnu mysqld[2875]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:38:30 Kubutnu mysqld[2875]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x5617773c0751]
oct. 31 09:38:30 Kubutnu mysqld[2875]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x5617769de64c]
oct. 31 09:38:30 Kubutnu mysqld[2875]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x5617769de77e]
oct. 31 09:38:30 Kubutnu mysqld[2875]: /usr/sbin/mysqld(my_abort()+0xe) [0x5617773b5e3e]
oct. 31 09:38:30 Kubutnu mysqld[2875]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x561777567dc3]
oct. 31 09:38:30 Kubutnu mysqld[2875]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x561777679da8]
oct. 31 09:38:30 Kubutnu mysqld[2875]: /usr/sbin/mysqld(+0x16e73ca) [0x5617774c83ca]
oct. 31 09:38:30 Kubutnu mysqld[2875]: /usr/sbin/mysqld(+0x16da379) [0x5617774bb379]
oct. 31 09:38:30 Kubutnu mysqld[2875]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7f0084736253]
oct. 31 09:38:30 Kubutnu mysqld[2875]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7f00843bdac3]
oct. 31 09:38:30 Kubutnu mysqld[2875]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7f008444fa40]
oct. 31 09:38:30 Kubutnu mysqld[2875]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:38:30 Kubutnu mysqld[2875]: information that should help you find out what is causing the crash.
oct. 31 09:38:30 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:38:30 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:38:30 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:38:30 Kubutnu systemd[1]: mysql.service: Consumed 3.820s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:38:31 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 4.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:38:31 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:38:31 Kubutnu systemd[1]: mysql.service: Consumed 3.820s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:38:31 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:38:31 Kubutnu mysqld[2905]: 2023-10-31T08:38:31.418722Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 2905
oct. 31 09:38:31 Kubutnu mysqld[2905]: 2023-10-31T08:38:31.431542Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:38:31 Kubutnu mysqld[2905]: 2023-10-31T08:38:31.866309Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 139650401629760
oct. 31 09:38:31 Kubutnu mysqld[2905]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:38:31 Kubutnu mysqld[2905]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:38:31 Kubutnu mysqld[2905]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:38:31 Kubutnu mysqld[2905]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:38:31 Kubutnu mysqld[2905]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:38:31 Kubutnu mysqld[2905]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:38:31 Kubutnu mysqld[2905]: InnoDB: about forcing recovery.
oct. 31 09:38:31 Kubutnu mysqld[2905]: 2023-10-31T08:38:31Z UTC - mysqld got signal 6 ;
oct. 31 09:38:31 Kubutnu mysqld[2905]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:38:31 Kubutnu mysqld[2905]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:38:31 Kubutnu mysqld[2905]: Thread pointer: 0x0
oct. 31 09:38:31 Kubutnu mysqld[2905]: Attempting backtrace. You can use the following information to find out
oct. 31 09:38:31 Kubutnu mysqld[2905]: where mysqld died. If you see no messages after this, something went
oct. 31 09:38:31 Kubutnu mysqld[2905]: terribly wrong...
oct. 31 09:38:31 Kubutnu mysqld[2905]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:38:31 Kubutnu mysqld[2905]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x562a26182751]
oct. 31 09:38:31 Kubutnu mysqld[2905]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x562a257a064c]
oct. 31 09:38:31 Kubutnu mysqld[2905]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x562a257a077e]
oct. 31 09:38:31 Kubutnu mysqld[2905]: /usr/sbin/mysqld(my_abort()+0xe) [0x562a26177e3e]
oct. 31 09:38:31 Kubutnu mysqld[2905]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x562a26329dc3]
oct. 31 09:38:31 Kubutnu mysqld[2905]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x562a2643bda8]
oct. 31 09:38:31 Kubutnu mysqld[2905]: /usr/sbin/mysqld(+0x16e73ca) [0x562a2628a3ca]
oct. 31 09:38:31 Kubutnu mysqld[2905]: /usr/sbin/mysqld(+0x16da379) [0x562a2627d379]
oct. 31 09:38:31 Kubutnu mysqld[2905]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7f02f58d3253]
oct. 31 09:38:31 Kubutnu mysqld[2905]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7f02f555aac3]
oct. 31 09:38:31 Kubutnu mysqld[2905]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7f02f55eca40]
oct. 31 09:38:31 Kubutnu mysqld[2905]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:38:31 Kubutnu mysqld[2905]: information that should help you find out what is causing the crash.
oct. 31 09:38:31 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:38:31 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:38:31 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:38:32 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:38:32 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:38:32 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:38:32 Kubutnu mysqld[2933]: 2023-10-31T08:38:32.389359Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 2933
oct. 31 09:38:32 Kubutnu mysqld[2933]: 2023-10-31T08:38:32.398980Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:38:32 Kubutnu mysqld[2933]: 2023-10-31T08:38:32.672733Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 140146143348288
oct. 31 09:38:32 Kubutnu mysqld[2933]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:38:32 Kubutnu mysqld[2933]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:38:32 Kubutnu mysqld[2933]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:38:32 Kubutnu mysqld[2933]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:38:32 Kubutnu mysqld[2933]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:38:32 Kubutnu mysqld[2933]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:38:32 Kubutnu mysqld[2933]: InnoDB: about forcing recovery.
oct. 31 09:38:32 Kubutnu mysqld[2933]: 2023-10-31T08:38:32Z UTC - mysqld got signal 6 ;
oct. 31 09:38:32 Kubutnu mysqld[2933]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:38:32 Kubutnu mysqld[2933]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:38:32 Kubutnu mysqld[2933]: Thread pointer: 0x0
oct. 31 09:38:32 Kubutnu mysqld[2933]: Attempting backtrace. You can use the following information to find out
oct. 31 09:38:32 Kubutnu mysqld[2933]: where mysqld died. If you see no messages after this, something went
oct. 31 09:38:32 Kubutnu mysqld[2933]: terribly wrong...
oct. 31 09:38:32 Kubutnu mysqld[2933]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:38:32 Kubutnu mysqld[2933]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x55bb75877751]
oct. 31 09:38:32 Kubutnu mysqld[2933]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x55bb74e9564c]
oct. 31 09:38:32 Kubutnu mysqld[2933]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x55bb74e9577e]
oct. 31 09:38:32 Kubutnu mysqld[2933]: /usr/sbin/mysqld(my_abort()+0xe) [0x55bb7586ce3e]
oct. 31 09:38:32 Kubutnu mysqld[2933]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x55bb75a1edc3]
oct. 31 09:38:32 Kubutnu mysqld[2933]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x55bb75b30da8]
oct. 31 09:38:32 Kubutnu mysqld[2933]: /usr/sbin/mysqld(+0x16e73ca) [0x55bb7597f3ca]
oct. 31 09:38:32 Kubutnu mysqld[2933]: /usr/sbin/mysqld(+0x16da379) [0x55bb75972379]
oct. 31 09:38:32 Kubutnu mysqld[2933]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7f76620f8253]
oct. 31 09:38:32 Kubutnu mysqld[2933]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7f7661d7fac3]
oct. 31 09:38:32 Kubutnu mysqld[2933]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7f7661e11a40]
oct. 31 09:38:32 Kubutnu mysqld[2933]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:38:32 Kubutnu mysqld[2933]: information that should help you find out what is causing the crash.
oct. 31 09:38:32 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:38:32 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:38:32 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:38:32 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 6.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:38:32 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:38:32 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:38:33 Kubutnu mysqld[2961]: 2023-10-31T08:38:33.229829Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 2961
oct. 31 09:38:33 Kubutnu mysqld[2961]: 2023-10-31T08:38:33.240287Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:38:33 Kubutnu mysqld[2961]: 2023-10-31T08:38:33.863004Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 139754670646848
oct. 31 09:38:33 Kubutnu mysqld[2961]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:38:33 Kubutnu mysqld[2961]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:38:33 Kubutnu mysqld[2961]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:38:33 Kubutnu mysqld[2961]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:38:33 Kubutnu mysqld[2961]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:38:33 Kubutnu mysqld[2961]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:38:33 Kubutnu mysqld[2961]: InnoDB: about forcing recovery.
oct. 31 09:38:33 Kubutnu mysqld[2961]: 2023-10-31T08:38:33Z UTC - mysqld got signal 6 ;
oct. 31 09:38:33 Kubutnu mysqld[2961]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:38:33 Kubutnu mysqld[2961]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:38:33 Kubutnu mysqld[2961]: Thread pointer: 0x0
oct. 31 09:38:33 Kubutnu mysqld[2961]: Attempting backtrace. You can use the following information to find out
oct. 31 09:38:33 Kubutnu mysqld[2961]: where mysqld died. If you see no messages after this, something went
oct. 31 09:38:33 Kubutnu mysqld[2961]: terribly wrong...
oct. 31 09:38:33 Kubutnu mysqld[2961]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:38:33 Kubutnu mysqld[2961]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x55568afd3751]
oct. 31 09:38:33 Kubutnu mysqld[2961]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x55568a5f164c]
oct. 31 09:38:33 Kubutnu mysqld[2961]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x55568a5f177e]
oct. 31 09:38:33 Kubutnu mysqld[2961]: /usr/sbin/mysqld(my_abort()+0xe) [0x55568afc8e3e]
oct. 31 09:38:33 Kubutnu mysqld[2961]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x55568b17adc3]
oct. 31 09:38:33 Kubutnu mysqld[2961]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x55568b28cda8]
oct. 31 09:38:33 Kubutnu mysqld[2961]: /usr/sbin/mysqld(+0x16e73ca) [0x55568b0db3ca]
oct. 31 09:38:33 Kubutnu mysqld[2961]: /usr/sbin/mysqld(+0x16da379) [0x55568b0ce379]
oct. 31 09:38:33 Kubutnu mysqld[2961]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7f1b4235e253]
oct. 31 09:38:33 Kubutnu mysqld[2961]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7f1b41fe5ac3]
oct. 31 09:38:33 Kubutnu mysqld[2961]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7f1b42077a40]
oct. 31 09:38:33 Kubutnu mysqld[2961]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:38:33 Kubutnu mysqld[2961]: information that should help you find out what is causing the crash.
oct. 31 09:38:33 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:38:33 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:38:33 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:38:33 Kubutnu systemd[1]: mysql.service: Consumed 1.038s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:38:34 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 7.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:38:34 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:38:34 Kubutnu systemd[1]: mysql.service: Consumed 1.038s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:38:34 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:38:34 Kubutnu mysqld[2989]: 2023-10-31T08:38:34.367823Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 2989
oct. 31 09:38:34 Kubutnu mysqld[2989]: 2023-10-31T08:38:34.382347Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:38:34 Kubutnu mysqld[2989]: 2023-10-31T08:38:34.652799Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 139887713936960
oct. 31 09:38:34 Kubutnu mysqld[2989]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:38:34 Kubutnu mysqld[2989]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:38:34 Kubutnu mysqld[2989]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:38:34 Kubutnu mysqld[2989]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:38:34 Kubutnu mysqld[2989]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:38:34 Kubutnu mysqld[2989]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:38:34 Kubutnu mysqld[2989]: InnoDB: about forcing recovery.
oct. 31 09:38:34 Kubutnu mysqld[2989]: 2023-10-31T08:38:34Z UTC - mysqld got signal 6 ;
oct. 31 09:38:34 Kubutnu mysqld[2989]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:38:34 Kubutnu mysqld[2989]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:38:34 Kubutnu mysqld[2989]: Thread pointer: 0x0
oct. 31 09:38:34 Kubutnu mysqld[2989]: Attempting backtrace. You can use the following information to find out
oct. 31 09:38:34 Kubutnu mysqld[2989]: where mysqld died. If you see no messages after this, something went
oct. 31 09:38:34 Kubutnu mysqld[2989]: terribly wrong...
oct. 31 09:38:34 Kubutnu mysqld[2989]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:38:34 Kubutnu mysqld[2989]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x55e22d359751]
oct. 31 09:38:34 Kubutnu mysqld[2989]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x55e22c97764c]
oct. 31 09:38:34 Kubutnu mysqld[2989]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x55e22c97777e]
oct. 31 09:38:34 Kubutnu mysqld[2989]: /usr/sbin/mysqld(my_abort()+0xe) [0x55e22d34ee3e]
oct. 31 09:38:34 Kubutnu mysqld[2989]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x55e22d500dc3]
oct. 31 09:38:34 Kubutnu mysqld[2989]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x55e22d612da8]
oct. 31 09:38:34 Kubutnu mysqld[2989]: /usr/sbin/mysqld(+0x16e73ca) [0x55e22d4613ca]
oct. 31 09:38:34 Kubutnu mysqld[2989]: /usr/sbin/mysqld(+0x16da379) [0x55e22d454379]
oct. 31 09:38:34 Kubutnu mysqld[2989]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7f3a3bf96253]
oct. 31 09:38:34 Kubutnu mysqld[2989]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7f3a3bc1dac3]
oct. 31 09:38:34 Kubutnu mysqld[2989]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7f3a3bcafa40]
oct. 31 09:38:34 Kubutnu mysqld[2989]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:38:34 Kubutnu mysqld[2989]: information that should help you find out what is causing the crash.
oct. 31 09:38:34 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:38:34 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:38:34 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:38:34 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 8.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:38:34 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:38:34 Kubutnu systemd[1]: mysql.service: Start request repeated too quickly.
oct. 31 09:38:34 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:38:34 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:46:45 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:46:47 Kubutnu mysqld[4009]: 2023-10-31T08:46:47.085960Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 4009
oct. 31 09:46:47 Kubutnu mysqld[4009]: 2023-10-31T08:46:47.110184Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:46:47 Kubutnu mysqld[4009]: 2023-10-31T08:46:47.711214Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 139953032443456
oct. 31 09:46:47 Kubutnu mysqld[4009]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:46:47 Kubutnu mysqld[4009]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:46:47 Kubutnu mysqld[4009]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:46:47 Kubutnu mysqld[4009]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:46:47 Kubutnu mysqld[4009]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:46:47 Kubutnu mysqld[4009]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:46:47 Kubutnu mysqld[4009]: InnoDB: about forcing recovery.
oct. 31 09:46:47 Kubutnu mysqld[4009]: 2023-10-31T08:46:47Z UTC - mysqld got signal 6 ;
oct. 31 09:46:47 Kubutnu mysqld[4009]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:46:47 Kubutnu mysqld[4009]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:46:47 Kubutnu mysqld[4009]: Thread pointer: 0x0
oct. 31 09:46:47 Kubutnu mysqld[4009]: Attempting backtrace. You can use the following information to find out
oct. 31 09:46:47 Kubutnu mysqld[4009]: where mysqld died. If you see no messages after this, something went
oct. 31 09:46:47 Kubutnu mysqld[4009]: terribly wrong...
oct. 31 09:46:47 Kubutnu mysqld[4009]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:46:47 Kubutnu mysqld[4009]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x558632b7a751]
oct. 31 09:46:47 Kubutnu mysqld[4009]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x55863219864c]
oct. 31 09:46:47 Kubutnu mysqld[4009]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x55863219877e]
oct. 31 09:46:47 Kubutnu mysqld[4009]: /usr/sbin/mysqld(my_abort()+0xe) [0x558632b6fe3e]
oct. 31 09:46:47 Kubutnu mysqld[4009]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x558632d21dc3]
oct. 31 09:46:47 Kubutnu mysqld[4009]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x558632e33da8]
oct. 31 09:46:47 Kubutnu mysqld[4009]: /usr/sbin/mysqld(+0x16e73ca) [0x558632c823ca]
oct. 31 09:46:47 Kubutnu mysqld[4009]: /usr/sbin/mysqld(+0x16da379) [0x558632c75379]
oct. 31 09:46:47 Kubutnu mysqld[4009]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7f496fc30253]
oct. 31 09:46:47 Kubutnu mysqld[4009]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7f496f8b7ac3]
oct. 31 09:46:47 Kubutnu mysqld[4009]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7f496f949a40]
oct. 31 09:46:47 Kubutnu mysqld[4009]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:46:47 Kubutnu mysqld[4009]: information that should help you find out what is causing the crash.
oct. 31 09:46:47 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:46:47 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:46:47 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:46:47 Kubutnu systemd[1]: mysql.service: Consumed 1.863s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:46:48 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 1.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:46:48 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:46:48 Kubutnu systemd[1]: mysql.service: Consumed 1.863s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:46:48 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:46:48 Kubutnu mysqld[4039]: 2023-10-31T08:46:48.935967Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 4039
oct. 31 09:46:48 Kubutnu mysqld[4039]: 2023-10-31T08:46:48.950526Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:46:49 Kubutnu mysqld[4039]: 2023-10-31T08:46:49.141455Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 140454728496704
oct. 31 09:46:49 Kubutnu mysqld[4039]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:46:49 Kubutnu mysqld[4039]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:46:49 Kubutnu mysqld[4039]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:46:49 Kubutnu mysqld[4039]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:46:49 Kubutnu mysqld[4039]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:46:49 Kubutnu mysqld[4039]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:46:49 Kubutnu mysqld[4039]: InnoDB: about forcing recovery.
oct. 31 09:46:49 Kubutnu mysqld[4039]: 2023-10-31T08:46:49Z UTC - mysqld got signal 6 ;
oct. 31 09:46:49 Kubutnu mysqld[4039]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:46:49 Kubutnu mysqld[4039]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:46:49 Kubutnu mysqld[4039]: Thread pointer: 0x0
oct. 31 09:46:49 Kubutnu mysqld[4039]: Attempting backtrace. You can use the following information to find out
oct. 31 09:46:49 Kubutnu mysqld[4039]: where mysqld died. If you see no messages after this, something went
oct. 31 09:46:49 Kubutnu mysqld[4039]: terribly wrong...
oct. 31 09:46:49 Kubutnu mysqld[4039]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:46:49 Kubutnu mysqld[4039]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x560fca14e751]
oct. 31 09:46:49 Kubutnu mysqld[4039]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x560fc976c64c]
oct. 31 09:46:49 Kubutnu mysqld[4039]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x560fc976c77e]
oct. 31 09:46:49 Kubutnu mysqld[4039]: /usr/sbin/mysqld(my_abort()+0xe) [0x560fca143e3e]
oct. 31 09:46:49 Kubutnu mysqld[4039]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x560fca2f5dc3]
oct. 31 09:46:49 Kubutnu mysqld[4039]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x560fca407da8]
oct. 31 09:46:49 Kubutnu mysqld[4039]: /usr/sbin/mysqld(+0x16e73ca) [0x560fca2563ca]
oct. 31 09:46:49 Kubutnu mysqld[4039]: /usr/sbin/mysqld(+0x16da379) [0x560fca249379]
oct. 31 09:46:49 Kubutnu mysqld[4039]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7fbe40bdb253]
oct. 31 09:46:49 Kubutnu mysqld[4039]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7fbe40862ac3]
oct. 31 09:46:49 Kubutnu mysqld[4039]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7fbe408f4a40]
oct. 31 09:46:49 Kubutnu mysqld[4039]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:46:49 Kubutnu mysqld[4039]: information that should help you find out what is causing the crash.
oct. 31 09:46:49 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:46:49 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:46:49 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:46:49 Kubutnu systemd[1]: mysql.service: Consumed 1.063s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:46:49 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 2.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:46:49 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:46:49 Kubutnu systemd[1]: mysql.service: Consumed 1.063s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:46:49 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:46:49 Kubutnu mysqld[4067]: 2023-10-31T08:46:49.910284Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 4067
oct. 31 09:46:49 Kubutnu mysqld[4067]: 2023-10-31T08:46:49.920731Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:46:50 Kubutnu mysqld[4067]: 2023-10-31T08:46:50.098379Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 139730302993984
oct. 31 09:46:50 Kubutnu mysqld[4067]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:46:50 Kubutnu mysqld[4067]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:46:50 Kubutnu mysqld[4067]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:46:50 Kubutnu mysqld[4067]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:46:50 Kubutnu mysqld[4067]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:46:50 Kubutnu mysqld[4067]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:46:50 Kubutnu mysqld[4067]: InnoDB: about forcing recovery.
oct. 31 09:46:50 Kubutnu mysqld[4067]: 2023-10-31T08:46:50Z UTC - mysqld got signal 6 ;
oct. 31 09:46:50 Kubutnu mysqld[4067]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:46:50 Kubutnu mysqld[4067]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:46:50 Kubutnu mysqld[4067]: Thread pointer: 0x0
oct. 31 09:46:50 Kubutnu mysqld[4067]: Attempting backtrace. You can use the following information to find out
oct. 31 09:46:50 Kubutnu mysqld[4067]: where mysqld died. If you see no messages after this, something went
oct. 31 09:46:50 Kubutnu mysqld[4067]: terribly wrong...
oct. 31 09:46:50 Kubutnu mysqld[4067]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:46:50 Kubutnu mysqld[4067]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x55c29e4b2751]
oct. 31 09:46:50 Kubutnu mysqld[4067]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x55c29dad064c]
oct. 31 09:46:50 Kubutnu mysqld[4067]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x55c29dad077e]
oct. 31 09:46:50 Kubutnu mysqld[4067]: /usr/sbin/mysqld(my_abort()+0xe) [0x55c29e4a7e3e]
oct. 31 09:46:50 Kubutnu mysqld[4067]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x55c29e659dc3]
oct. 31 09:46:50 Kubutnu mysqld[4067]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x55c29e76bda8]
oct. 31 09:46:50 Kubutnu mysqld[4067]: /usr/sbin/mysqld(+0x16e73ca) [0x55c29e5ba3ca]
oct. 31 09:46:50 Kubutnu mysqld[4067]: /usr/sbin/mysqld(+0x16da379) [0x55c29e5ad379]
oct. 31 09:46:50 Kubutnu mysqld[4067]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7f159411b253]
oct. 31 09:46:50 Kubutnu mysqld[4067]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7f1593da2ac3]
oct. 31 09:46:50 Kubutnu mysqld[4067]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7f1593e34a40]
oct. 31 09:46:50 Kubutnu mysqld[4067]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:46:50 Kubutnu mysqld[4067]: information that should help you find out what is causing the crash.
oct. 31 09:46:50 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:46:50 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:46:50 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:46:50 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 3.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:46:50 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:46:50 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:46:50 Kubutnu mysqld[4095]: 2023-10-31T08:46:50.913445Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 4095
oct. 31 09:46:50 Kubutnu mysqld[4095]: 2023-10-31T08:46:50.924156Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:46:51 Kubutnu mysqld[4095]: 2023-10-31T08:46:51.107872Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 140416321111616
oct. 31 09:46:51 Kubutnu mysqld[4095]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:46:51 Kubutnu mysqld[4095]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:46:51 Kubutnu mysqld[4095]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:46:51 Kubutnu mysqld[4095]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:46:51 Kubutnu mysqld[4095]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:46:51 Kubutnu mysqld[4095]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:46:51 Kubutnu mysqld[4095]: InnoDB: about forcing recovery.
oct. 31 09:46:51 Kubutnu mysqld[4095]: 2023-10-31T08:46:51Z UTC - mysqld got signal 6 ;
oct. 31 09:46:51 Kubutnu mysqld[4095]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:46:51 Kubutnu mysqld[4095]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:46:51 Kubutnu mysqld[4095]: Thread pointer: 0x0
oct. 31 09:46:51 Kubutnu mysqld[4095]: Attempting backtrace. You can use the following information to find out
oct. 31 09:46:51 Kubutnu mysqld[4095]: where mysqld died. If you see no messages after this, something went
oct. 31 09:46:51 Kubutnu mysqld[4095]: terribly wrong...
oct. 31 09:46:51 Kubutnu mysqld[4095]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:46:51 Kubutnu mysqld[4095]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x55e280a16751]
oct. 31 09:46:51 Kubutnu mysqld[4095]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x55e28003464c]
oct. 31 09:46:51 Kubutnu mysqld[4095]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x55e28003477e]
oct. 31 09:46:51 Kubutnu mysqld[4095]: /usr/sbin/mysqld(my_abort()+0xe) [0x55e280a0be3e]
oct. 31 09:46:51 Kubutnu mysqld[4095]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x55e280bbddc3]
oct. 31 09:46:51 Kubutnu mysqld[4095]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x55e280ccfda8]
oct. 31 09:46:51 Kubutnu mysqld[4095]: /usr/sbin/mysqld(+0x16e73ca) [0x55e280b1e3ca]
oct. 31 09:46:51 Kubutnu mysqld[4095]: /usr/sbin/mysqld(+0x16da379) [0x55e280b11379]
oct. 31 09:46:51 Kubutnu mysqld[4095]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7fb549e90253]
oct. 31 09:46:51 Kubutnu mysqld[4095]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7fb549b17ac3]
oct. 31 09:46:51 Kubutnu mysqld[4095]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7fb549ba9a40]
oct. 31 09:46:51 Kubutnu mysqld[4095]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:46:51 Kubutnu mysqld[4095]: information that should help you find out what is causing the crash.
oct. 31 09:46:51 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:46:51 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:46:51 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:46:51 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 4.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:46:51 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:46:51 Kubutnu systemd[1]: Starting MySQL Community Server...
░░ Subject: L'unité (unit) mysql.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a commencé à démarrer.
oct. 31 09:46:51 Kubutnu mysqld[4123]: 2023-10-31T08:46:51.912329Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-0ubuntu0.22.04.1) starting as process 4123
oct. 31 09:46:51 Kubutnu mysqld[4123]: 2023-10-31T08:46:51.926423Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
oct. 31 09:46:53 Kubutnu mysqld[4123]: 2023-10-31T08:46:53.698577Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7905:err == DB_SUCCESS thread 140238124160576
oct. 31 09:46:53 Kubutnu mysqld[4123]: InnoDB: We intentionally generate a memory trap.
oct. 31 09:46:53 Kubutnu mysqld[4123]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
oct. 31 09:46:53 Kubutnu mysqld[4123]: InnoDB: If you get repeated assertion failures or crashes, even
oct. 31 09:46:53 Kubutnu mysqld[4123]: InnoDB: immediately after the mysqld startup, there may be
oct. 31 09:46:53 Kubutnu mysqld[4123]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:46:53 Kubutnu mysqld[4123]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
oct. 31 09:46:53 Kubutnu mysqld[4123]: InnoDB: about forcing recovery.
oct. 31 09:46:53 Kubutnu mysqld[4123]: 2023-10-31T08:46:53Z UTC - mysqld got signal 6 ;
oct. 31 09:46:53 Kubutnu mysqld[4123]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
oct. 31 09:46:53 Kubutnu mysqld[4123]: BuildID[sha1]=6da44471e64652692eaa270c171582a6e8ed7791
oct. 31 09:46:53 Kubutnu mysqld[4123]: Thread pointer: 0x0
oct. 31 09:46:53 Kubutnu mysqld[4123]: Attempting backtrace. You can use the following information to find out
oct. 31 09:46:53 Kubutnu mysqld[4123]: where mysqld died. If you see no messages after this, something went
oct. 31 09:46:53 Kubutnu mysqld[4123]: terribly wrong...
oct. 31 09:46:53 Kubutnu mysqld[4123]: stack_bottom = 0 thread_stack 0x100000
oct. 31 09:46:53 Kubutnu mysqld[4123]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x564fc6c91751]
oct. 31 09:46:53 Kubutnu mysqld[4123]: /usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x564fc62af64c]
oct. 31 09:46:53 Kubutnu mysqld[4123]: /usr/sbin/mysqld(my_server_abort()+0x7e) [0x564fc62af77e]
oct. 31 09:46:53 Kubutnu mysqld[4123]: /usr/sbin/mysqld(my_abort()+0xe) [0x564fc6c86e3e]
oct. 31 09:46:53 Kubutnu mysqld[4123]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x564fc6e38dc3]
oct. 31 09:46:53 Kubutnu mysqld[4123]: /usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x218) [0x564fc6f4ada8]
oct. 31 09:46:53 Kubutnu mysqld[4123]: /usr/sbin/mysqld(+0x16e73ca) [0x564fc6d993ca]
oct. 31 09:46:53 Kubutnu mysqld[4123]: /usr/sbin/mysqld(+0x16da379) [0x564fc6d8c379]
oct. 31 09:46:53 Kubutnu mysqld[4123]: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7f8bd092d253]
oct. 31 09:46:53 Kubutnu mysqld[4123]: /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7f8bd05b4ac3]
oct. 31 09:46:53 Kubutnu mysqld[4123]: /lib/x86_64-linux-gnu/libc.so.6(+0x126a40) [0x7f8bd0646a40]
oct. 31 09:46:53 Kubutnu mysqld[4123]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
oct. 31 09:46:53 Kubutnu mysqld[4123]: information that should help you find out what is causing the crash.
oct. 31 09:46:53 Kubutnu systemd[1]: mysql.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit mysql.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
oct. 31 09:46:53 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:46:53 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.
oct. 31 09:46:53 Kubutnu systemd[1]: mysql.service: Consumed 3.675s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:46:54 Kubutnu systemd[1]: mysql.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Le redémarrage automatique de l'unité (unit) mysql.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
oct. 31 09:46:54 Kubutnu systemd[1]: Stopped MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a terminé son arrêt
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a terminé son arrêt.
oct. 31 09:46:54 Kubutnu systemd[1]: mysql.service: Consumed 3.675s CPU time.
░░ Subject: Ressources consommées durant l'éxécution de l'unité (unit)
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service s'est arrêtée et a consommé les ressources indiquées.
oct. 31 09:46:54 Kubutnu systemd[1]: mysql.service: Start request repeated too quickly.
oct. 31 09:46:54 Kubutnu systemd[1]: mysql.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mysql.service has entered the 'failed' state with result 'exit-code'.
oct. 31 09:46:54 Kubutnu systemd[1]: Failed to start MySQL Community Server.
░░ Subject: L'unité (unit) mysql.service a échoué
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ L'unité (unit) mysql.service a échoué, avec le résultat failed.Une idée du problème ?
JM
Dernière modification par pti-jean (Le 31/10/2023, à 16:56)
Hors ligne
#2 Le 31/10/2023, à 11:11
- bruno
Re : [Résolu] Pb avec MySql (mysql -u root -p) suite à une maj...
Bonjour,
Il y a longtemps que mysql n'utilise plus l’authentification par mot de passe pour son compte root. Et ce n'est vraiment pas une bonne idée de modifier ce comportement.Voir le point 3.4 de la doc en lien.
Là le problème c'est que le service ne démarra pas à cause de tables innodb corrompues. C'est indiqué explicitement dans les logs :
oct. 31 09:46:53 Kubutnu mysqld[4123]: InnoDB: corruption in the InnoDB tablespace. Please refer to
oct. 31 09:46:53 Kubutnu mysqld[4123]: InnoDB: [url]http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html[/url]Il faut essayer ce qui est indiqué dans l'URL indiqué dans les logs. Sinon il faudra supprimer manuellement les fichiers sous /var/lib/mysql et restaurer les base à partir de leur sauvegardes logiques (dumps).
Dernière modification par bruno (Le 31/10/2023, à 13:39)
Attention, les bouteilles vendues par Nestlé Waters sont contaminées au monoxyde de dihydrogène.
Hors ligne
#3 Le 31/10/2023, à 12:12
- pti-jean
Re : [Résolu] Pb avec MySql (mysql -u root -p) suite à une maj...
Salut bruno,
J'ai essayé de modifier innodb_force_recovery, mais le problème c'est que sur ma distribution, j'ai pas de fichier "/etc/my.cnf", à la place j'ai trouvé un fichier "/etc/mysql/my.cnf"... J'espère que c'est le bon endroit pour le faire ??
Da plus dans ce fichier (/etc/mysql/my.cnf), il n'y a pas de session "[mysqld]", ni d'instruction "innodb_force_recovery", j'ai tout rajouter à la main à la fin du fichier... j'espère que c'est ce qu'il fallait faire !?
J'ai monté les niveaux de innodb_force_recovery jusqu'à 5, mais MySql ne démarre toujours pas...
La question est, ai-je fait les bonnes modifications dans le bon fichier ??
JM
Dernière modification par pti-jean (Le 31/10/2023, à 12:15)
Hors ligne
#4 Le 31/10/2023, à 12:31
- pti-jean
Re : [Résolu] Pb avec MySql (mysql -u root -p) suite à une maj...
Je me pose vraiment la question, de savoir si le fichier "/etc/mysql/my.cnf" est le bon fichier à modifier... car je suis monté jusqu'à 6 (innodb_force_recovery) et cela ne démarre toujours pas ??
J'ai trouvé cette doc:
https://sysadminstory.wordpress.com/201 … odb-mysql/
mais pour le moment cela ne fonctionne pas!
JM
Hors ligne
#5 Le 31/10/2023, à 13:41
- bruno
Re : [Résolu] Pb avec MySql (mysql -u root -p) suite à une maj...
La directive est en principe à mettre sous la section [mysqld] dans le fichier /etc/mysql/mysql.conf.d/mysqld.cnf (voir la doc mysql) il faut ensuite tenter de relancer le service :
sudo systemctl restart mysqlAttention, les bouteilles vendues par Nestlé Waters sont contaminées au monoxyde de dihydrogène.
Hors ligne
#6 Le 31/10/2023, à 14:41
- pti-jean
Re : [Résolu] Pb avec MySql (mysql -u root -p) suite à une maj...
La directive est en principe à mettre sous la section [mysqld] dans le fichier /etc/mysql/mysql.conf.d/mysqld.cnf (voir la doc mysql) il faut ensuite tenter de relancer le service :
Non cela fonctionne pas... J'ai fait de 1 à 6... quand je relace le service c'est toujours en erreur...
J'ai voulu suivre ce conseil:
Sinon il faudra supprimer manuellement les fichiers sous /var/lib/mysql et restaurer les base à partir de leurs sauvegardes logiques (dumps).
J'ai donc fait un:
# rm /var/lib/mysql/* -rToujours en erreur au redémarrage du service:
$ sudo systemctl restart mysql.service
Job for mysql.service failed because the control process exited with error code.
See "systemctl status mysql.service" and "journalctl -xeu mysql.service" for details.Bon, j'ai la solution de revenir en arrière avec les points de restauration...
Y a t-il un truc que je ne fais pas comme il faut ??
JM
Hors ligne
#7 Le 31/10/2023, à 16:31
- bruno
Re : [Résolu] Pb avec MySql (mysql -u root -p) suite à une maj...
Si tu fais cela :
# rm /var/lib/mysql/* -rd'abord il faut être sûr d'avoir une sauvegarde de tes bases sous forme de fichiers sql. Ensuite il faut réinstaller compétemment les paquets mysql-server pour que l'arborescence sous /var/lib/mysql soit recréée :
sudo apt reinstall mysql-server*Si le service a démarré sans erreur tu pourras te connecter avec :
sudo mysqlrecréer tes utilisateurs, tes bases, et restaurer tes bases en sourçant les fichiers sql de sauvegarde.
Si tu n'y arrives pas utilise ton point de restauration fonctionnel. Qu'est-ce que tu a fait comme mises à jour pour que cela provoque une corruption (ou une incompatibilité) des tables innodb ?
Attention, les bouteilles vendues par Nestlé Waters sont contaminées au monoxyde de dihydrogène.
Hors ligne
#8 Le 31/10/2023, à 16:54
- pti-jean
Re : [Résolu] Pb avec MySql (mysql -u root -p) suite à une maj...
Bon c'est cool, je m'en suis sortie...
Sur une ancienne version (grâce à un point de restauration) où MySql fonctionnait, j'ai fait un:
$ mysqldump --user=root --password --opt --all-databases --result-file=dump.sqlCommande trouvé ici:
https://sysadminstory.wordpress.com/201 … odb-mysql/
Puis maintenant sur la version mise à jour où MySql ne fonctionne pas j'ai effectué une réinstallation complète:
https://doc.ubuntu-fr.org/mysql#reinstallation_complete
Donc:
sudo apt autoremove --purge ~n^mysql-server ~n^mariadb-server
...
sudo mv /var/lib/mysql /var/lib/mysql.bak
sudo mv /etc/mysql /etc/mysql.bak
sudo mkdir -p /etc/mysql/conf.d
sudo apt clean
...
sudo apt install mysql-serverSuite à cela j'ai réimporté ma sauvegarde:
$ sudo mysql < dump.sqlReste plus qu'à redémarrer MySql:
$ sudo systemctl restart mysql.serviceEt ça roule...
Résolut!
JM
Hors ligne