1С-Битрикс Разработчикам - Can't connect to local MySQL server through socket '/var/lib/mysqld/mysqld.sock' (2) (400)

Заглянувший

Сообщений: 4 Авторитет: 1 Рейтинг пользователя: 0 Регистрация: 07.02.2017

05.05.2019 07:44:15

Прошу совет:

После отключения электричества Мускул сошел с ума:через web показывает так:

Цитата
[Bitrix\Main\DB\ConnectionException] Mysql connect error [localhost]: (2002) No such file or directory (400) /home/bitrix/www/bitrix/modules/main/lib/db/mysqliconnection.php:65

в ссш показывает так:

Цитата
[root@b ~]# mysql -u root ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysqld/mysqld.sock' (2)

Применял права на папки:

Цитата
chown -Rh mysql /var/lib/mysqld

Цитата
rm /var/lib/mysqld/mysql.sock

Изменено: Михаил Ляпин - 05.05.2019 07:52:58

Михаил Ляпин

Заглянувший

Сообщений: 4 Авторитет: 1 Рейтинг пользователя: 0 Регистрация: 07.02.2017

#27

05.05.2019 07:46:53

Странно конечно, что Битрикс разваливается как карточный домик от обычного отключения света (а если глюкнет железо и будет внезапное отключение????)

вот еще:

Цитата

[root@b ~]# systemctl status mysqld.service -l
● mysqld.service - MySQL Server
Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Sun 2019-05-05 09:05:37 +05; 21s ago
Docs: man:mysqld(

http://dev.mysql.com/doc/refman/en/using-systemd.html
Process: 17453 ExecStart=/usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid $MYSQLD_OPTS (code=exited, status=1/FAILURE)
Process: 17435 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=0/SUCCESS)

May 05 09:05:37 site.ru systemd[1]: Failed to start MySQL Server.
May 05 09:05:37 site.ru systemd[1]: Unit mysqld.service entered failed state.
May 05 09:05:37 site.ru systemd[1]: mysqld.service failed.
May 05 09:05:37 site.ru systemd[1]: mysqld.service holdoff time over, scheduling restart.
May 05 09:05:37 site.ru systemd[1]: start request repeated too quickly for mysqld.service
May 05 09:05:37 site.ru systemd[1]: Failed to start MySQL Server.
May 05 09:05:37 site.ru systemd[1]: Unit mysqld.service entered failed state.
May 05 09:05:37 site.ru systemd[1]: mysqld.service failed.

Изменено: Михаил Ляпин - 05.05.2019 07:47:47

Михаил Ляпин

Заглянувший

Сообщений: 4 Авторитет: 1 Рейтинг пользователя: 0 Регистрация: 07.02.2017

#28

05.05.2019 07:51:57

Вот это тоже применял:

Цитата
sudo mkfifo /var/lib/mysqld/mysqld.sock sudo chown -R mysql:mysql /var/lib/mysqld

проверяем:

Цитата
[root@b ~]# ls -l /var/lib/mysqld/ total 0 prw-r--r-- 1 mysql mysql 0 May 5 09:49 mysqld.sock

После этого меняется ошибка:

Цитата
[Bitrix\Main\DB\ConnectionException] Mysql connect error [localhost]: (2002) Permission denied (400) /home/bitrix/www/bitrix/modules/main/lib/db/mysqliconnection.php:65

Цитата
[root@b ~]# mysql -u root ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysqld/mysqld.sock' (111)

Михаил Ляпин

Заглянувший

Сообщений: 4 Авторитет: 1 Рейтинг пользователя: 0 Регистрация: 07.02.2017

#29

05.05.2019 07:54:18

Вот из еррор.лог

Цитата

2019-05-05T03:58:45.138904Z 0 [Warning] Changed limits: max_open_files: 5000 (requested 16246)
2019-05-05T03:58:45.139066Z 0 [Warning] Changed limits: table_open_cache: 2473 (requested 8096)
2019-05-05T03:58:45.283444Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2019-05-05T03:58:45.284404Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.21-21) starting as process 16755 ...
2019-05-05T03:58:45.288204Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-05-05T03:58:45.288232Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-05-05T03:58:45.288235Z 0 [Note] InnoDB: Uses event mutexes
2019-05-05T03:58:45.288239Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-05-05T03:58:45.288242Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
2019-05-05T03:58:45.288248Z 0 [Note] InnoDB: Using Linux native AIO
2019-05-05T03:58:45.288409Z 0 [Note] InnoDB: Number of pools: 1
2019-05-05T03:58:45.288483Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-05-05T03:58:45.289745Z 0 [Note] InnoDB: Initializing buffer pool, total size = 1G, instances = 8, chunk size = 128M
2019-05-05T03:58:45.309553Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-05-05T03:58:45.315954Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-05-05T03:58:45.333722Z 0 [Note] InnoDB: Recovering partial pages fr om the parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite
2019-05-05T03:58:45.368434Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-05-05T03:58:45.371743Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 12164232838
2019-05-05T03:58:45.371785Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 12164271377
2019-05-05T03:58:45.373488Z 0 [Note] InnoDB: Database was not shutdown normally!
2019-05-05T03:58:45.373504Z 0 [Note] InnoDB: Starting crash recovery.
2019-05-05T03:58:45.857160Z 0 [Note] InnoDB: Created parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite, size 31457280 bytes
2019-05-05T03:58:45.921864Z 0 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 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 03:58:45 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.
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 http://bugs.percona.com/

key_buffer_size=50331648
read_buffer_size=131072
max_used_connections=0
max_threads=44
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 = 407533 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...
61 stack_bottom = 0 thread_stack 0x20000
62 63 /usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xef5c1b]

Семён Забусов

Посетитель

Сообщений: 111 Баллов: 9 Авторитет: 1 Рейтинг пользователя: 0 Регистрация: 21.12.2016

#30

06.05.2019 03:28:26

Цитата
Михаил Ляпин написал: Цитатаsudo

щито о_О?
в студию

Код
cat /etc/redhat-release

и версию виртуального окружения

Капитан токсичность

Can't connect to local MySQL server through socket '/var/lib/mysqld/mysqld.sock' (2) (400)

Технологии

Эрмитаж

Мобильное приложение

Автокеширование

SiteUpdate

Производительность

Виртуальная машина

Веб-окружение

Результаты тестов

Выбрать хостинг

Веб кластер

Безопасность

Проактивная защита

Веб-антивирус

Аутентификация