Fabio-RevendaAlpha Posted February 27, 2019 Share Posted February 27, 2019 Olá amigos desta vez preciso da ajuda de vc´s. Estou com um problema no banco de dados do meu servidor e já abri chamado na buycpanel e eles não podem solucionar pq tem o risco de bugar geral. Preciso de uma pessoa para poder vericar e solucionar esse problema. Quem souber mexer no InnoDB me chame no pv por favor 0 Quote Link to comment Share on other sites More sharing options...
Administration AngelCosta Posted February 27, 2019 Administration Share Posted February 27, 2019 Pq vc não diz qual é o problema? 0 Quote 'Cause he's my best friend, he's my pal. He's my homeboy, my rotten soldier. He's my sweet cheese. My good-time boy. Link to comment Share on other sites More sharing options...
barreto Posted February 27, 2019 Share Posted February 27, 2019 Compartilha o problema. De repente alguém da comunidade pode colaborar com dicas. 0 Quote Link to comment Share on other sites More sharing options...
Fabio-RevendaAlpha Posted February 27, 2019 Author Share Posted February 27, 2019 2019-02-26T19:30:03.205625Z 21485 [Note] Got an error reading communication packets 2019-02-26T19:30:11.498243Z 21487 [Warning] InnoDB: Cannot add field `lightbox_description_font_weight` in table `radio7g_wp877`.`wp_bwg_theme` because after adding it, the row size is 8144 which is greater than maximum allowed size (8126) for a record on index leaf page. 2019-02-26T19:30:11.770397Z 21487 [ERROR] InnoDB: Operating system error number 13 in a file operation. 2019-02-26T19:30:11.770435Z 21487 [ERROR] InnoDB: The error means mysqld does not have the access rights to the directory. 2019-02-26 16:30:11 0x7f48cd034700 InnoDB: Assertion failure in thread 139950653916928 in file fil0fil.cc line 898 InnoDB: Failing assertion: success InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 19:30:11 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. Attempting to collect some information that could help diagnose the problem. As this is a crash and something is definitely wrong, the information collection process might fail. 0 Quote Link to comment Share on other sites More sharing options...
Fabio-RevendaAlpha Posted April 3, 2019 Author Share Posted April 3, 2019 Olá pessoal alguém ai consegue me ajudar? Pois ainda estou com esse problema. 0 Quote Link to comment Share on other sites More sharing options...
barreto Posted April 4, 2019 Share Posted April 4, 2019 Bom dia @Fabio-RevendaAlpha, como vai? No site que o pessoal relata bugs do mysql têm várias dicas. Sinceramente, esse é um erro que nunca me deparei então não me arrisco a dizer pra você adotar esse ou aquele caminho. Pesquisei pela linha abaixo e encontrei várias opções de ajuda. InnoDB: Assertion failure in thread 139950653916928 in file fil0fil.cc line 898 0 Quote Link to comment Share on other sites More sharing options...
barreto Posted April 4, 2019 Share Posted April 4, 2019 @Fabio-RevendaAlpha a propósito, só pra reforçar aquele padrãozão, faça e tenha backup antes de qualquer coisa ... rs 0 Quote Link to comment Share on other sites More sharing options...
pluginscpanelwhm Posted April 4, 2019 Share Posted April 4, 2019 OIá, já tentou adicionar isso innodb_force_recovery = 1 no arquivo de config do mysql 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.