Оживлю. Сегодня внезапно вылезло то же самое, после пары лет работы. Никто никуда не лазил. Со свободными ресурсами все норм:
Код |
---|
[root@ bitrix]# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 873M 0 873M 0% /dev
tmpfs 883M 0 883M 0% /dev/shm
tmpfs 883M 8.7M 874M 1% /run
tmpfs 883M 0 883M 0% /sys/fs/cgroup
/dev/sda1 20G 6.5G 13G 35% /
tmpfs 177M 0 177M 0% /run/user/0
[root@ bitrix]# df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
devtmpfs 223284 313 222971 1% /dev
tmpfs 225854 1 225853 1% /dev/shm
tmpfs 225854 430 225424 1% /run
tmpfs 225854 16 225838 1% /sys/fs/cgroup
/dev/sda1 1310720 156346 1154374 12% /
tmpfs 225854 1 225853 1% /run/user/0
[root@ bitrix]# free -m -h
total used free shared buff/cache available
Mem: 1.7G 238M 653M 181M 872M 1.2G
Swap: 0B 0B 0B
|
После изучения, понял что постоянно пытается стартануть mysql:
Код |
---|
InnoDB: Dump of the tablespace extent descriptor: len 40; hex 0000000000000000ffffffff0000ffffffff000000000002aafafeaefeffffffffffffffffffffff; asc ;2023-05-05T05:05:02.627067Z 0 [ERROR] InnoDB: InnoDB is trying to free page [page id: space=184, page number=6] though it is already marked as free in the tablespace! The tablespace free space info is corrupt. You may need to dump your tables and recreate the whole database!
2023-05-05T05:05:02.627130Z 0 [ERROR] [FATAL] InnoDB: Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-05-05 08:05:02 0x7f660d390700 InnoDB: Assertion failure in thread 140076285232896 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.
05:05:02 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=25165824
read_buffer_size=131072
max_used_connections=6
max_threads=32
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 = 155975 K 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: 0x7f65f80008c0
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 = 7f660d38fcb0 thread_stack 0x20000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xf45deb]
/usr/sbin/mysqld(handle_fatal_signal+0x505)[0xd77785]
/lib64/libpthread.so.0(+0xf630)[0x7f6631283630]
/lib64/libc.so.6(gsignal+0x37)[0x7f662f380387]
/lib64/libc.so.6(abort+0x148)[0x7f662f381a78]
/usr/sbin/mysqld[0x78212c]
/usr/sbin/mysqld(_ZN2ib5fatalD1Ev+0xfd)[0x118ddad]
/usr/sbin/mysqld[0x1273d89]
/usr/sbin/mysqld(_Z14fseg_free_pagePhmmbP5mtr_t+0x21c)[0x127682c]
/usr/sbin/mysqld(_Z12btr_compressP9btr_cur_tmP5mtr_t+0xe0c)[0x11a002c]
/usr/sbin/mysqld(_Z26btr_cur_compress_if_usefulP9btr_cur_tmP5mtr_t+0x1cc)[0x11adaac]
/usr/sbin/mysqld(_Z26btr_cur_pessimistic_deleteP7dberr_tmP9btr_cur_tmbP5mtr_t+0x735)[0x11b3bd5]
/usr/sbin/mysqld[0x10ec4ed]
/usr/sbin/mysqld(_Z14row_purge_stepP9que_thr_t+0x851)[0x10eeff1]
/usr/sbin/mysqld(_Z15que_run_threadsP9que_thr_t+0x89f)[0x10946df]
/usr/sbin/mysqld(_Z9trx_purgemmb+0x305)[0x1157d45]
/usr/sbin/mysqld(srv_purge_coordinator_thread+0xa47)[0x1129917]
/lib64/libpthread.so.0(+0x7ea5)[0x7f663127bea5]
/lib64/libc.so.6(clone+0x6d)[0x7f662f448b0d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
Status: NOT_KILLED
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-05-05T05:05:05.671756Z 0 [Warning] Changed limits: max_open_files: 5000 (requested 8234)
2023-05-05T05:05:05.672033Z 0 [Warning] Changed limits: table_open_cache: 2479 (requested 4096)
2023-05-05T05:05:05.852522Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2023-05-05T05:05:05.855027Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.36-39) starting as process 28253 ...
2023-05-05T05:05:05.872016Z 0 [Note] InnoDB: PUNCH HOLE support available
2023-05-05T05:05:05.872073Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-05-05T05:05:05.872080Z 0 [Note] InnoDB: Uses event mutexes
2023-05-05T05:05:05.872088Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2023-05-05T05:05:05.872094Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
2023-05-05T05:05:05.872101Z 0 [Note] InnoDB: Using Linux native AIO
2023-05-05T05:05:05.872455Z 0 [Note] InnoDB: Number of pools: 1
2023-05-05T05:05:05.872630Z 0 [Note] InnoDB: Using CPU crc32 instructions
2023-05-05T05:05:05.877369Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2023-05-05T05:05:05.884431Z 0 [Note] InnoDB: Completed initialization of buffer pool
2023-05-05T05:05:05.887230Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2023-05-05T05:05:05.907304Z 0 [Note] InnoDB: Recovering partial pages from the parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite
2023-05-05T05:05:05.917827Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2023-05-05T05:05:05.922510Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 8654483912
2023-05-05T05:05:05.957053Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 8654639539
2023-05-05T05:05:05.960358Z 0 [Note] InnoDB: Database was not shutdown normally!
2023-05-05T05:05:05.960381Z 0 [Note] InnoDB: Starting crash recovery.
2023-05-05T05:05:06.202725Z 0 [Note] InnoDB: Created parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite, size 3932160 bytes
2023-05-05T05:05:06.440817Z 0 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 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 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
2023-05-05T05:05:06.954589Z 0 [Note] InnoDB: Apply batch completed
2023-05-05T05:05:07.682429Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2023-05-05T05:05:07.682465Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-05-05T05:05:07.691839Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-05-05T05:05:07.765384Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2023-05-05T05:05:07.766854Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2023-05-05T05:05:07.766881Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2023-05-05T05:05:07.767245Z 0 [Note] InnoDB: Waiting for purge to start
|
Запустить mysqld получилось с forcing-innodb-recovery=2, но стоящая в .settings.php база "sitemanager", при SHOW TABLES - пуста. Я уже и не вспомню какие были настройки и пароли, но в SHOW DATABASES есть более менее понятное имя базы с последним изменением как минимум от 20.03 (добавлял инфоблок). Сделал ее дамп. Со слов девицы: "...я добавила статью, но она вся появилась как ссылка, попыталась исправить и зайти больше не смогла..."
в первой строке написано You may need to dump your tables and recreate the whole database. Вроде сделал дамп, но как пересоздать базу в Битрикс ВМ чет не пойму. Прошу помочь в решении проблемы!