Problemas com container MySQL no Docker

27/03/2023

0

Olá a todos!

Venho trabalhando nos últimos meses com um banco de dados MySQL e um servidor Apache com o uso do Docker. Possuo 3 containers integrados através do docker-compose: um container para o servidor Apache + PHP, outro para o MySQL e mais outro para o PHPMyAdmin. Tudo estava funcionando como deveria até alguns dias atrás, quando comecei a ter problemas com o container do MySQL, o qual fica constantemente iniciando e reiniciando.

O log da execução é bastante extenso, por isso incluo abaixo somente as linhas que mencionam erros na execução:

2023-03-25 18:24:57 2023-03-25T18:24:57.118075Z 0 [ERROR] [MY-012639] [InnoDB] Write to file ./#innodb_redo/#ib_redo34_tmp failed at offset 0, 512 bytes should have been written, only 0 were written. Operating system error number 5. Check that your OS and file system support files of this size. Check also that the disk is not full or a disk quota exceeded.
2023-03-25 18:24:57 2023-03-25T18:24:57.119027Z 0 [ERROR] [MY-012640] [InnoDB] Error number 5 means 'Input/output error'
2023-03-25 18:24:57 2023-03-25T18:24:57.122176Z 0 [ERROR] [MY-012891] [InnoDB] Failed to create redo log file ./#innodb_redo/#ib_redo34 (error: 100) for start LSN 164677632
2023-03-25 18:24:57 2023-03-25T18:24:57.122589Z 0 [ERROR] [MY-013864] [InnoDB] [FATAL] Error 100 encountered when writing to the redo log file: ./#innodb_redo/#ib_redo33.
2023-03-25 18:24:57 2023-03-25T18:24:57.123393Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0write.cc:2115:ib::fatal triggered thread 140058477823744
2023-03-25 18:24:57 InnoDB: We intentionally generate a memory trap.
2023-03-25 18:24:57 InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
2023-03-25 18:24:57 InnoDB: If you get repeated assertion failures or crashes, even
2023-03-25 18:24:57 InnoDB: immediately after the mysqld startup, there may be
2023-03-25 18:24:57 InnoDB: corruption in the InnoDB tablespace. Please refer to
2023-03-25 18:24:57 InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
2023-03-25 18:24:57 InnoDB: about forcing recovery.
2023-03-25 18:24:57 2023-03-25T18:24:57Z UTC - mysqld got signal 6 ;
2023-03-25 18:24:57 Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
2023-03-25 18:24:57 BuildID[sha1]=6b049f17400f850658b2eb3ff165ec9a085d9655
2023-03-25 18:24:57 Thread pointer: 0x0
2023-03-25 18:24:57 Attempting backtrace. You can use the following information to find out
2023-03-25 18:24:57 where mysqld died. If you see no messages after this, something went
2023-03-25 18:24:57 terribly wrong...
2023-03-25 18:24:57 stack_bottom = 0 thread_stack 0x100000
2023-03-25 18:24:57 /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x213de91]
2023-03-25 18:24:57 /usr/sbin/mysqld(print_fatal_signal(int)+0x387) [0xfdeac7]
2023-03-25 18:24:57 /usr/sbin/mysqld(my_server_abort()+0x7e) [0xfdec1e]
2023-03-25 18:24:57 /usr/sbin/mysqld(my_abort()+0xe) [0x2137c7e]
2023-03-25 18:24:57 /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x33a) [0x243b28a]
2023-03-25 18:24:57 /usr/sbin/mysqld(ib::fatal::~fatal()+0xc8) [0x243db48]
2023-03-25 18:24:57 /usr/sbin/mysqld() [0x2313868]
2023-03-25 18:24:57 /usr/sbin/mysqld() [0x2314c39]
2023-03-25 18:24:57 /usr/sbin/mysqld(log_writer(log_t*)+0x4b0) [0x2316420]
2023-03-25 18:24:57 /usr/sbin/mysqld(std::thread::_State_impl<std::thread::_Invoker<std::tuple<Detached_thread, void (*)(log_t*), log_t*> > >::_M_run()+0xce) [0x22e697e]
2023-03-25 18:24:57 /lib64/libstdc++.so.6(+0xc2ba3) [0x7f6211be0ba3]
2023-03-25 18:24:57 /lib64/libpthread.so.0(+0x81da) [0x7f6212c471da]
2023-03-25 18:24:57 /lib64/libc.so.6(clone+0x43) [0x7f62111f6e73]
2023-03-25 18:24:57 The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
2023-03-25 18:24:57 information that should help you find out what is causing the crash.
2023-03-25 18:25:03 2023-03-25T18:25:03.493357Z 0 [Warning] [MY-011068] [Server] The syntax '--skip-host-cache' is deprecated and will be removed in a future release. Please use SET GLOBAL host_cache_size=0 instead.
2023-03-25 18:25:03 2023-03-25T18:25:03.529138Z 0 [Warning] [MY-010918] [Server] 'default_authentication_plugin' is deprecated and will be removed in a future release. Please use authentication_policy instead.
2023-03-25 18:25:03 2023-03-25T18:25:03.529429Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.32) starting as process 1
2023-03-25 18:25:03 2023-03-25T18:25:03.663891Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2023-03-25 18:25:08 2023-03-25T18:25:08.125680Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2023-03-25 18:25:08 
2023-03-25 18:25:08 InnoDB: Progress in percents: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 732023-03-25T18:25:08.786497Z 0 [System] [MY-010229] [Server] Starting XA crash recovery...
2023-03-25 18:25:08  74 75 76 77 78 79 802023-03-25T18:25:08.803542Z 0 [System] [MY-010232] [Server] XA crash recovery finished.
2023-03-25 18:25:09  81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 1002023-03-25T18:25:09.005691Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2023-03-25 18:25:09 2023-03-25T18:25:09.006567Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2023-03-25 18:25:09 2023-03-25T18:25:09.039844Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.
2023-03-25 18:25:09 2023-03-25T18:25:09.117442Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock
2023-03-25 18:25:09 2023-03-25T18:25:09.117652Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.32'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server - GPL.
2023-03-25 22:25:40 2023-03-25T22:25:40.227395Z 0 [System] [MY-013172] [Server] Received SHUTDOWN from user <via user signal>. Shutting down mysqld (Version: 8.0.32).
2023-03-25 22:25:41 2023-03-25T22:25:41.577897Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.32)  MySQL Community Server - GPL.
2023-03-26 18:33:04 2023-03-26T17:33:04.241060Z 0 [Warning] [MY-011068] [Server] The syntax '--skip-host-cache' is deprecated and will be removed in a future release. Please use SET GLOBAL host_cache_size=0 instead.
2023-03-26 18:33:04 2023-03-26T17:33:04.255140Z 0 [Warning] [MY-010918] [Server] 'default_authentication_plugin' is deprecated and will be removed in a future release. Please use authentication_policy instead.
2023-03-26 18:33:04 2023-03-26T17:33:04.255860Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.32) starting as process 1
2023-03-26 18:33:04 2023-03-26T17:33:04.331388Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2023-03-26 18:33:07 2023-03-26T17:33:07.119909Z 1 [ERROR] [MY-013893] [InnoDB] Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.
2023-03-26 18:33:07 2023-03-26T17:33:07.120002Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error.
2023-03-26 18:33:07 2023-03-26T17:33:07.259482Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2023-03-26 18:33:07 2023-03-26T17:33:07.259854Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.


Agradeço se alguém puder me ajudar a resolver esta questão.
Ze Rocha

Ze Rocha

Responder

Assista grátis a nossa aula inaugural

Assitir aula

Saiba por que programar é uma questão de
sobrevivência e como aprender sem riscos

Assistir agora

Utilizamos cookies para fornecer uma melhor experiência para nossos usuários, consulte nossa política de privacidade.

Aceitar