MySQL server won't start?

Question

linux

Please tell me, Bitrix has died, it gives an error

[Bitrix\Main\DB\ConnectionException]
Mysql connect error [localhost]: (2002) Connection refused (400)
/home/bitrix/www/bitrix/modules/main/lib/db/mysqliconnection .php:82
#0: Bitrix\Main\DB\MysqliConnection->connectInternal()
/home/bitrix/www/bitrix/modules/main/lib/data/connection.php:53
#1: Bitrix\Main\Data\ Connection->getResource()
/home/bitrix/www/bitrix/modules/main/lib/db/mysqlisqlhelper.php:21
#2: Bitrix\Main\DB\MysqliSqlHelper->forSql(string)
/home/bitrix/www /bitrix/modules/main/lib/config/option.php:206
#3: Bitrix\Main\Config\Option::load(string)
/home/bitrix/www/bitrix/modules/main/lib/config/option .php:83
#4: Bitrix\Main\Config\Option::getRealValue(string, string, boolean)
/home/bitrix/www/bitrix/modules/main/lib/config/option.php:32
#5: Bitrix\Main\Config \Option::get(string, string, string)
/home/bitrix/www/bitrix/modules/main/lib/httprequest.php:394
#6: Bitrix\Main\HttpRequest->prepareCookie(array)
/home/bitrix /www/bitrix/modules/main/lib/httprequest.php:71
#7: Bitrix\Main\HttpRequest->__construct(object, array, array, array, array)
/home/bitrix/www/bitrix/modules/main /lib/httpapplication.php:49
#8: Bitrix\Main\HttpApplication->initializeContext(array)
/home/bitrix/www/bitrix/modules/main/lib/application.php:130
#9: Bitrix\Main\Application ->initializeExtendedKernel(array)
/home/bitrix/www/bitrix/modules/main/include.php:21
#10: require_once(string)
/home/bitrix/www/bitrix/modules/main/include/prolog_before.php:14
#11: require_once( string)
/home/bitrix/www/index.php:8

Checked service mysql status
Writes that

Redirecting to /bin/systemctl status mysql.service
● mysqld.service - MySQL Server
Loaded: loaded (/usr/lib/systemd/system/ mysqld.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Wed 2022-02-09 00:56:39 +06; 8h ago
Docs: man:mysqld(8)
dev.mysql.com/doc/refman/en/using-systemd.html
Process: 39220 ExecStart=/usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid $MYSQLD_OPTS (code=exited, status=1/FAILURE)
Process: 39195 ExecStartPre=/usr /bin/mysqld_pre_systemd (code=exited, status=0/SUCCESS)
Main PID: 1625 (code=exited, status=2)

There are no logs in the /var/log/mysql.log folder, empty files.

But there are logs in /var/log/mysql/error.log

Server Version: 5.7.36-39 Percona Server (GPL), Release 39, Revision 305619d

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 0x20000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xf45deb]
/usr/sbin/mysqld(handle_fatal_signal+0x505)[0xd77785]
/lib64/libpthread.so.0(+0xf630)[0x7fa68e625630]
/lib64/libc.so. 6(gsignal+0x37)[0x7fa68c722387]
/lib64/libc.so.6(abort+0x148)[0x7fa68c723a78]
/usr/sbin/mysqld[0x78212c]
70 /usr/sbin/mysqld[0x104f985]
/usr/sbin/mysqld (_Z22recv_recover_page_funcmP11buf_block_t + 0xa25) [0x1050a65]
/ usr / sbin / mysqld (_Z20buf_page_io_completeP10buf_page_tb + 0x8a3) [0x11d63b3]
/ usr / sbin / mysqld (_Z12fil_aio_waitm + 0x23e) [0x1250bee]
/ usr / sbin / mysqld (io_handler_thread + 0xc0) [0x112e790]
/lib64/libpthread.so.0(+0x7ea5)[0x7fa68e61dea5]
/lib64/libc.so.6(clone+0x6d)[0x7fa68c7eab0d]
You may download the Percona Server operations manual by visiting
www.percona.com/software/percona-server . You may find information
in the manual which will help you identify the cause of the crash.
2022-02-08T18:56:37.864703Z 0 [Warning] Changed limits: max_open_files: 5000 (requested 24642
)
02-08T18:56:38.031699Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set. 2022-02-08T18:56: 38.033396Z
0 [Note] /usr/sbin/mysqld (mysqld 5.7.36-39) starting as process 39222 ...
: PUNCH HOLE support available
2022-02-08T18
: 56:38.040785Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2022-02-08T18
:56:38.040803Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
2022-02-08T18:56:38.040808 Z 0 [Note] InnoDB: Using Linux native AIO
2022-02-08T18:56:38.041127Z 0 [Note] InnoDB: Number of pools: 1
2022-02-08T18:56:38.041265Z 0 [Note] InnoDB: Using CPU crc32 instructions
2022-02-08T18:56:38.044738Z 0 [Note] InnoDB: Initializing buffer pool, total size = 3G, instances = 8, chunk size = 128M
2022-02-08T18:56:38.118537Z 0 [Note] InnoDB: Completed initialization of buffer
pool be changed. See the man page of setpriority().
2022-02-08T18:56:38.164269Z 0 [Note] InnoDB: Recovering partial pages from the parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite
2022-02-08T18:56:38.384741Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2022-02-08T18:56:38.392518Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn
4453395959
2022-02-08T18:56:38.435640Z 0 [Note] InnoDB: Database was not shutdown normally!
2022-02-08T18:56:38.435651Z 0 [Note] InnoDB: Starting crash recovery.
2022-02-08T18:56:38.693072Z 0 [Note] InnoDB: Created parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite, size 31457280 bytes
2022-02-08T18:56:38.825932Z 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 1 row operations to undo 2022-02-08T18:56 :
38.825991Z 0
0 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 64 65 66 67 68 69 70 2022-02-09 00:56:38 0x7f54048a6700 InnoDB: Assertion failure in thread 139998830159616 in file log0recv.cc line 1912
InnoDB: Failing assertion: !page || (ibool)!!page_is_comp(page) == dict_table_is_comp(index->table)
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to 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: dev.mysql.com/doc/refman/5.7/en/forcing-innodb-rec...
InnoDB: about forcing recovery.
18:56:38 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 = 894620K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Build ID: c31c40a51ba42c4006b66c03ce83fd3625c07bd3
Server Version: 5.7.36-39 Percona Server (GPL), Release 39, Revision 305619d

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 0x20000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[ 0xf45deb
]
/libpthread.so.0(+0xf630)[0x7f54f2343630]
/lib64/libc.so.6(gsignal+0x37)[0x7f54f0440387]
/lib64/libc.so.6(abort+0x148)[0x7f54f0441a78]
/ usr / sbin / mysqld [0x78212c]
/ usr / sbin / mysqld [0x104f985]
/ usr / sbin / mysqld (_Z22recv_recover_page_funcmP11buf_block_t + 0xa25) [0x1050a65]
/ usr / sbin / mysqld (_Z20buf_page_io_completeP10buf_page_tb + 0x8a3) [0x11d63b3]
/ usr / sbin /mysqld(_Z12fil_aio_waitm+0x23e)[ 0x1250bee ]
71 +0x6d)[0x7f54f0508b0d] You may download the Percona Server operations manual by visiting www.percona.com/software/percona-server . You may find information in the manual which will help you identify the cause of the crash. Tried restarting mysql service



Job for mysqld.service failed because the control process exited with error code. See "systemctl status mysqld.service" and "journalctl -xe" for details.

How to solve the problem, where to dig??

Answer 1

Broken tables or unclosed InnoDB transaction logs.
Make backups of all directories and try to repair or simply delete databases and restore from backups.
PS The reason for publishing logs from bitrix is ​​not clear - what did you want to achieve by this.

Answer 2

there may be many options
, I wrote here, but there is no time to formalize normally.
If it’s urgent, write me, so that it’s not the first time;)
let me guess, I bet that such crap happened when the disk was 100% full

Answer 3

Look here.