Cpanel - после обновления до 8.0.38 - Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware - откат до 8.0.37: различия между версиями

Материал из Wiki - Iphoster - the best ever hosting and support. 2005 - 2024
Перейти к:навигация, поиск
 
Строка 1: Строка 1:
=== Cpanel - после обновления до 8.0.38 - Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware - откат до 8.0.37 ===
+
=== Cpanel - после обновления mysql до 8.0.38 - Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware - откат до 8.0.37 ===
  
  
После обновления до 8.0.38 - отвалился mysql сервер с ошибками:
+
После обновления mysql до 8.0.38 - отвалился mysql сервер с ошибками:
 
  2024-06-30T21:08:33.296628Z 0 [Warning] [MY-010140] [Server] Could not increase number of max_open_files to more than 10000 (request: 47000)
 
  2024-06-30T21:08:33.296628Z 0 [Warning] [MY-010140] [Server] Could not increase number of max_open_files to more than 10000 (request: 47000)
 
  2024-06-30T21:08:33.413740Z 0 [Warning] [MY-010918] [Server] 'default_authentication_plugin' is deprecated and will be removed in a future  release. Please use authentication_policy instead.  
 
  2024-06-30T21:08:33.413740Z 0 [Warning] [MY-010918] [Server] 'default_authentication_plugin' is deprecated and will be removed in a future  release. Please use authentication_policy instead.  

Текущая версия на 14:29, 1 июля 2024

Cpanel - после обновления mysql до 8.0.38 - Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware - откат до 8.0.37

После обновления mysql до 8.0.38 - отвалился mysql сервер с ошибками:

2024-06-30T21:08:33.296628Z 0 [Warning] [MY-010140] [Server] Could not increase number of max_open_files to more than 10000 (request: 47000)
2024-06-30T21:08:33.413740Z 0 [Warning] [MY-010918] [Server] 'default_authentication_plugin' is deprecated and will be removed in a future  release. Please use authentication_policy instead. 
2024-06-30T21:08:33.413748Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.38) starting as process 357682
2024-06-30T21:08:33.429519Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-06-30T21:08:35.296630Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2024-06-30T21:08:35Z UTC - mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=4b91dfbd6b28893d9e23ff8c0b0b69b03c59974a
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x100000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x5630cfe0bb01]
/usr/sbin/mysqld(print_fatal_signal(int)+0x393) [0x5630cec82693]
/usr/sbin/mysqld(handle_fatal_signal+0xa5) [0x5630cec82745]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x14420) [0x7f964f0d4420]
/usr/sbin/mysqld(Validate_files::check(__gnu_cxx::__normal_iterator<dd::Tablespace const* const*, std::vector<dd::Tablespace const*,   std::allocator<dd::Tablespace const*> > > const&, __gnu_cxx::__normal_iterator<dd::Tablespace const* const*, std::vector<dd::Tablespace const*,  std::allocator<dd::Tablespace const*> > > const&, unsigned long)+0x15a0) [0x5630cfe58670 ]
/usr/sbin/mysqld(std::thread::_State_impl<std::thread::_Invoker<std::tuple<Detached_thread, std::function<void  (__gnu_cxx::__normal_iterator<dd::Tablespace const* const*, std::vector<dd::Tablespace const*, std::allocator<dd::Tablespace const*> > >  const&, __gnu_cxx::__normal_iterator<dd::Tablespace const* const*, std::vector<dd::Tablespace const*, std::allocator<dd::Tablespace const*> > >  const&, unsigned long)>, __gnu_cxx::__normal_iterator<dd::Tablespace const* const*, std::vector<dd::Tablespace const*, /lib/x86_64-linux- gnu/libstdc++.so.6(+0xd6df4) [0x7f964efaedf4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8609) [0x7f964f0c8609]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x43) [0x7f964ec9b353]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2024-06-30T21:08:36.184582Z 0 [Warning] [MY-010140] [Server] Could not increase number of max_open_files to more than 10000 (request: 47000)


Решение - это откатить до mysql 8.0.37
Пример для Ubuntu 20.04:

# mkdir -v /root/mysqldown && cd /root/mysqldown
# wget https://downloads.mysql.com/archives/get/p/23/file/mysql-server_8.0.37-1ubuntu20.04_amd64.deb-bundle.tar
# tar xvf mysql-server_8.0.37-1ubuntu20.04_amd64.deb-bundle.tar
# rm -rvf ./mysql-community-test-debug_8.0.37-1ubuntu20.04_amd64.deb ./mysql-community-test_8.0.37-1ubuntu20.04_amd64.deb ./mysql-testsuite_8.0.37-1ubuntu20.04_amd64.deb
# dpkg -i *mysql*.deb
# /scripts/restartsrv_mysql --status

Запретить обновления MySQL:

# apt-mark hold mysql-client mysql-common mysql-community-client-core mysql-community-client-plugins mysql-community-client mysql-community-server-core mysql-community-server-debug mysql-community-server mysql-server mysql-shell

Из официальной документации:

https://support.cpanel.net/hc/en-us/articles/24546938662039-Upstream-issue-MySQL-8-0-38-does-not-start-Segmentation-Fault