Форум

С октября с одним из заказчиков сидим на РЕД ОС, PHP 8.1 - в целом жить можно, но пришлось перейти на fpm, а то apache падал сам по себе.

Кстати, очень жду в документации настройки для php-fpm, а то самописный конфиг поначалу приходилось часто править

Подскажите, есть решение? 3 дня бьюсь...

Здравствуйте!

Сегодня на виртуалке легли сайты. Увидев ошибку
[Bitrix\Main\DB\ConnectionException]
Mysql connect error [localhost]: (2002) Connection refused (400)

Проверил место, его достаточно. Потом полез в error.log mysql файл заканчивается сообщениями типа:

Build ID: 38a1b1b717598d7fe5f8153c01fd1a5c62d9054e
Server Version: 5.7.33-36-log Percona Server (GPL), Release 36, Revision 7e403c5

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 0x80000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xf2793b]
/usr/sbin/mysqld(handle_fatal_signal+0x505)[0xd59bf5]
/lib64/libpthread.so.0(+0xf630)[0x7f11b3fa6630]
/lib64/libc.so.6(gsignal+0x37)[0x7f11b20a33d7]
/lib64/libc.so.6(abort+0x148)[0x7f11b20a4ac8]
/usr/sbin/mysqld[0x7819d4]
/usr/sbin/mysqld(_ZN2ib5fatalD1Ev+0xfd)[0x116dcad]
/usr/sbin/mysqld(_Z17buf_dblwr_processv+0x14d2)[0x11c15f2]
/usr/sbin/mysqld(_Z35recv_recovery_from_checkpoint_startm+0x28b0)[0x10372d0]
/usr/sbin/mysqld(_Z34innobase_start_or_create_for_mysqlv+0x4495)[0x11187e5]
/usr/sbin/mysqld[0xfc2297]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x51)[0x7b2bb1]
/usr/sbin/mysqld[0xc98b65]
/usr/sbin/mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0xc9eb00]
/usr/sbin/mysqld[0xd505bd]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0xaa5)[0xd54105]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f11b208f555]
/usr/sbin/mysqld[0x7a4144]
You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
2023-07-11T22:27:30.079558Z 0 [Warning] Changed limits: max_open_files: 5000 (requested 24642)
2023-07-11T22:27:30.079766Z 0 [Warning] Changed limits: table_open_cache: 2467 (requested 12288)
2023-07-11T22:27:30.239359Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2023-07-11T22:27:30.240775Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.33-36-log) starting as process 28015 ...
2023-07-11T22:27:30.248677Z 0 [Note] InnoDB: PUNCH HOLE support available
2023-07-11T22:27:30.248711Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-07-11T22:27:30.248715Z 0 [Note] InnoDB: Uses event mutexes
2023-07-11T22:27:30.248718Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2023-07-11T22:27:30.248722Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
2023-07-11T22:27:30.248735Z 0 [Note] InnoDB: Using Linux native AIO
2023-07-11T22:27:30.248931Z 0 [Note] InnoDB: Number of pools: 1
2023-07-11T22:27:30.249031Z 0 [Note] InnoDB: Using CPU crc32 instructions
2023-07-11T22:27:30.251407Z 0 [Note] InnoDB: Initializing buffer pool, total size = 3G, instances = 8, chunk size = 128M
2023-07-11T22:27:30.331433Z 0 [Note] InnoDB: Completed initialization of buffer pool
2023-07-11T22:27:30.352981Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2023-07-11T22:27:30.368210Z 0 [Note] InnoDB: Crash recovery did not find the parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite
2023-07-11T22:27:30.369539Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2023-07-11T22:27:30.382429Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 273686241366
2023-07-11T22:27:30.382461Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 273686241375
2023-07-11T22:27:30.382468Z 0 [Note] InnoDB: Database was not shutdown normally!
2023-07-11T22:27:30.382472Z 0 [Note] InnoDB: Starting crash recovery.
2023-07-11T22:27:30.488251Z 0 [Warning] InnoDB: Retry attempts for writing partial data failed.
2023-07-11T22:27:30.488289Z 0 [ERROR] InnoDB: Write to file /var/lib/mysql/xb_doublewritefailed at offset 30408704, 1048576 bytes should have been written, only 0 were written. Operating system error number 28. 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-07-11T22:27:30.488306Z 0 [ERROR] InnoDB: Error number 28 means 'No space left on device'
2023-07-11T22:27:30.488311Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2023-07-11T22:27:30.488421Z 0 [ERROR] [FATAL] InnoDB: Creating the parallel doublewrite buffer failed
2023-07-12 01:27:30 0x7f2da671b880  InnoDB: Assertion failure in thread 139834042726528 in file ut0ut.cc line 924
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.
22:27:30 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.
Please help us make Percona Server better by reporting any
bugs at https://bugs.percona.com/

key_buffer_size=100663296
read_buffer_size=131072
max_used_connections=0
max_threads=56
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 894620 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Не подскажите, каков порядок действий должен быть? Заранее спасибо, просто для меня это пока "китайская грамота" ... Что я понял,  так "2023-07-11T22:27:30.488306Z 0 [ERROR] InnoDB: Error number 28 means 'No space left on device'" Не хватило места? а Сейчас после чистки mysql заново нужно перезапустить? Или это я просто выхватил строку из контекста?  

Вопрос, кто-то пробывал обновить ядро linux до 5.x? Bitrix не ломается от этого? Просто столклулся с проблемой Centos, что он не поддерживает новые процессоры Zen3, и требуется обновить на более новое ядро