Добрый день!
После неудачной миграции на главной сайта выдаёт следующее:
[CODE][Bitrix\Main\DB\ConnectionException]
Mysql connect error [localhost, 127.0.0.1]: Can't connect to local MySQL server through socket '/var/lib/mysqld/mysqld.sock' (2) (400)
/home/bitrix/www/bitrix/modules/main/lib/db/mysqlconnection.php:50
#0: Bitrix\Main\DB\MysqlConnection->connectInternal()
/home/bitrix/www/bitrix/modules/main/lib/db/mysqlconnection.php:103
#1: Bitrix\Main\DB\MysqlConnection->queryInternal(string, array, NULL)
/home/bitrix/www/bitrix/modules/main/lib/db/connection.php:329
#2: Bitrix\Main\DB\Connection->query(string)
/home/bitrix/www/bitrix/modules/main/lib/config/option.php:183
#3: Bitrix\Main\Config\Option::load(string, NULL)
/home/bitrix/www/bitrix/modules/main/lib/config/option.php:53
#4: Bitrix\Main\Config\Option::get(string, string, string)
/home/bitrix/www/bitrix/modules/main/lib/httprequest.php:337
#5: Bitrix\Main\HttpRequest->prepareCookie(array)
/home/bitrix/www/bitrix/modules/main/lib/httprequest.php:63
#6: Bitrix\Main\HttpRequest->__construct(object, array, array, array, array)
/home/bitrix/www/bitrix/modules/main/lib/httpapplication.php:43
#7: Bitrix\Main\HttpApplication->initializeContext(array)
/home/bitrix/www/bitrix/modules/main/lib/application.php:122
#8: Bitrix\Main\Application->initializeExtendedKernel(array)
/home/bitrix/www/bitrix/modules/main/include.php:24
#9: require_once(string)
/home/bitrix/www/bitrix/modules/main/include/prolog_before.php:14
#10: require_once(string)
/home/bitrix/www/bitrix/modules/main/include/prolog.php:10
#11: require_once(string)
/home/bitrix/www/bitrix/header.php:1
#12: require(string)
/home/bitrix/www/index.php:2[/CODE]в var/lib/mysql/имя_сервера.err появилось следующее:
160622 17:21:12 mysqld_safe Starting mysqld daemon with databases fr om /var/lib/mysql
160622 17:21:12 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
160622 17:21:12 [Note] /usr/libexec/mysqld (mysqld 5.5.50) starting as process 5828 ...
160622 17:21:12 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
160622 17:21:12 [Note] Plugin 'FEDERATED' is disabled.
160622 17:21:12 InnoDB: The InnoDB memory heap is disabled
160622 17:21:12 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160622 17:21:12 InnoDB: Compressed tables use zlib 1.2.3
160622 17:21:12 InnoDB: Using Linux native AIO
160622 17:21:12 InnoDB: Initializing buffer pool, size = 128.0M
160622 17:21:12 InnoDB: Completed initialization of buffer pool
160622 17:21:12 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 26936435002
160622 17:21:12 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 26936457161
160622 17:21:12 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 14:21:12 UTC - mysqld got signal 11 ;
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.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=18
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 = 92623 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
wh ere mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x20000
/usr/libexec/mysqld(my_print_stacktrace+0x2e)[0x78ee3e]
/usr/libexec/mysqld(handle_fatal_signal+0x493)[0x6771f3]
/lib64/libpthread.so.0(+0xf7e0)[0x7f03a86827e0]
/usr/libexec/mysqld[0x8ccadb]
/usr/libexec/mysqld[0x8c9688]
/usr/libexec/mysqld[0x8c9cc5]
/usr/libexec/mysqld[0x8b8148]
/usr/libexec/mysqld[0x8b968c]
/usr/libexec/mysqld[0x85c3e1]
/usr/libexec/mysqld[0x884cb9]
/usr/libexec/mysqld[0x81c550]
/lib64/libpthread.so.0(+0x7aa1)[0x7f03a867aaa1]
/lib64/libc.so.6(clone+0x6d)[0x7f03a6f94aad]
The manual page at [URL=http://dev.mysql.com/doc/mysql/en/crashing.html]http://dev.mysql.com/doc/mysql/en/crashing.html[/URL] contains
information that should help you find out what is causing the crash.
160622 17:21:12 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
Что делать?
