не могу войти в нее

J

14

jpchv

30 июня 2019, 06:42

566

Добро пожаловать в phpMyAdmin

Невозможно подключиться к серверу MySQL

Язык - Language

АвторизацияДокументация

Пользователь:

Пароль:

mysqli_real_connect(): (HY000/2002): No such file or directory

:sudo mysql_secure_installation

mysql_secure_installation: [ERROR] unknown variable 'default-character-set=utf8mb4'

Securing the MySQL server deployment.

Enter password for user root:

Error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)

24

ZomBat

30 июня 2019, 06:48

#1

MySQL лежит, попробуй запустить:

service mysqld start

или

service mysql start

в свободное время шаманю над веб-окружением VPS...

J

14

jpchv

30 июня 2019, 07:16

#2

service mysqld start

Failed to start mysqld.service: Unit mysqld.service not found

---------- Добавлено 30.06.2019 в 07:17 ----------

service mysql start

Job for mysql.service failed because the control process exited with error code.

See "systemctl status mysql.service" and "journalctl -xe" for details.

я не знаю какой пароль

Ошибка запуска кэш сервера Apache2 server strat failed! Требуется проигрывание видосов с

A

18

Armano

30 июня 2019, 07:19

#3

Не могу войти в нее... Зашел в топег только из-за его названия

2

J

14

jpchv

30 июня 2019, 07:24

#4

как войти в нее

1

264

suffix

30 июня 2019, 07:38

#5

И всё таки где же у НЕЁ кнопка :)

Клуб любителей хрюш (https://www.babai.ru)

24

ZomBat

30 июня 2019, 07:41

#6

давай по очереди, вводим

systemctl status mysql.service

скриншотим

потом

journalctl -xe

скриншотим и сюда выкладываем две ссылки на результат.

J

14

jpchv

30 июня 2019, 07:53

#7

jpchv

---------- Добавлено 30.06.2019 в 07:57 ----------

24

ZomBat

30 июня 2019, 08:27

#8

нет, мы так далеко не уедем наверно)) перед journalctl -xe у тебя что-то еще случилось, посмотри логи MySQL они должны быть где-то в

/var/log/mysql.log

/var/log/mysql/error.log

IL

415

ivan-lev

30 июня 2019, 08:46

#9

jpchv:
не могу войти в нее

ZomBat:
давай по очереди, вводим

Что здесь происходит?.. 🤪

Ошибки MySql искать в

tail -20 /var/log/mysql/error.log

p.s. Вангую нехватку памяти Cannot allocate memory

p.p.s. На втором месте - траблы с диском

.. (http://levik.info/enekaryr-eti-exe-chto-eto.htm). :)

J

14

jpchv

30 июня 2019, 08:50

#10

2019-06-28 21:34:01 139628204792960 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2019-06-28 21:34:01 139628204792960 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2019-06-28 21:34:01 139628204792960 [Note] InnoDB: The InnoDB memory heap is disabled

2019-06-28 21:34:01 139628204792960 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2019-06-28 21:34:01 139628204792960 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2019-06-28 21:34:01 139628204792960 [Note] InnoDB: Compressed tables use zlib 1.2.11

2019-06-28 21:34:01 139628204792960 [Note] InnoDB: Using Linux native AIO

2019-06-28 21:34:01 139628204792960 [Note] InnoDB: Using SSE crc32 instructions

2019-06-28 21:34:01 139628204792960 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2019-06-28 21:34:01 139628204792960 [Note] InnoDB: Completed initialization of buffer pool

2019-06-28 21:34:01 139628204792960 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!

2019-06-28 21:34:01 139628204792960 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB

2019-06-28 21:34:01 139628204792960 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB

2019-06-28 21:34:01 139628204792960 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB

2019-06-28 21:34:01 139628204792960 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0

2019-06-28 21:34:01 139628204792960 [Warning] InnoDB: New log files created, LSN=45781

2019-06-28 21:34:01 139628204792960 [Note] InnoDB: Doublewrite buffer not found: creating new

2019-06-28 21:34:01 139628204792960 [Note] InnoDB: Doublewrite buffer created

2019-06-28 21:34:01 139628204792960 [Note] InnoDB: 128 rollback segment(s) are active.

2019-06-28 21:34:01 139628204792960 [Warning] InnoDB: Creating foreign key constraint system tables.

2019-06-28 21:34:01 139628204792960 [Note] InnoDB: Foreign key constraint system tables created

2019-06-28 21:34:01 139628204792960 [Note] InnoDB: Creating tablespace and datafile system tables.

2019-06-28 21:34:01 139628204792960 [Note] InnoDB: Tablespace and datafile system tables created.

2019-06-28 21:34:01 139628204792960 [Note] InnoDB: Waiting for purge to start

2019-06-28 21:34:01 139628204792960 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.43-84.3 started; log sequence number 0

2019-06-28 21:34:01 139627541296896 [Note] InnoDB: Dumping buffer pool(s) not yet started

2019-06-28 21:34:04 140713491229824 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2019-06-28 21:34:04 140713491229824 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2019-06-28 21:34:04 140713491229824 [Note] InnoDB: The InnoDB memory heap is disabled

2019-06-28 21:34:04 140713491229824 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2019-06-28 21:34:04 140713491229824 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2019-06-28 21:34:04 140713491229824 [Note] InnoDB: Compressed tables use zlib 1.2.11

2019-06-28 21:34:04 140713491229824 [Note] InnoDB: Using Linux native AIO

2019-06-28 21:34:04 140713491229824 [Note] InnoDB: Using SSE crc32 instructions

2019-06-28 21:34:04 140713491229824 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2019-06-28 21:34:04 140713491229824 [Note] InnoDB: Completed initialization of buffer pool

2019-06-28 21:34:04 140713491229824 [Note] InnoDB: Highest supported file format is Barracuda.

2019-06-28 21:34:04 140713491229824 [Note] InnoDB: 128 rollback segment(s) are active.

2019-06-28 21:34:04 140713491229824 [Note] InnoDB: Waiting for purge to start

2019-06-28 21:34:04 140713491229824 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.43-84.3 started; log sequence number 1616697

2019-06-28 21:34:04 140712825845504 [Note] InnoDB: Dumping buffer pool(s) not yet started

2019-06-28 21:34:07 140149103324288 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2019-06-28 21:34:07 140149103324288 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2019-06-28 21:34:07 140149103324288 [Note] InnoDB: The InnoDB memory heap is disabled

2019-06-28 21:34:07 140149103324288 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2019-06-28 21:34:07 140149103324288 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2019-06-28 21:34:07 140149103324288 [Note] InnoDB: Compressed tables use zlib 1.2.11

2019-06-28 21:34:07 140149103324288 [Note] InnoDB: Using Linux native AIO

2019-06-28 21:34:07 140149103324288 [Note] InnoDB: Using SSE crc32 instructions

2019-06-28 21:34:07 140149103324288 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2019-06-28 21:34:07 140149103324288 [Note] InnoDB: Completed initialization of buffer pool

2019-06-28 21:34:07 140149103324288 [Note] InnoDB: Highest supported file format is Barracuda.

2019-06-28 21:34:07 140149103324288 [Note] InnoDB: 128 rollback segment(s) are active.

2019-06-28 21:34:07 140149103324288 [Note] InnoDB: Waiting for purge to start

2019-06-28 21:34:07 140149103324288 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.43-84.3 started; log sequence number 1616707

2019-06-28 21:34:07 140148431910656 [Note] InnoDB: Dumping buffer pool(s) not yet started

2019-06-28 21:34:10 140603252493440 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2019-06-28 21:34:10 140603252493440 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2019-06-28 21:34:10 140603252493440 [Note] InnoDB: The InnoDB memory heap is disabled

2019-06-28 21:34:10 140603252493440 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2019-06-28 21:34:10 140603252493440 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2019-06-28 21:34:10 140603252493440 [Note] InnoDB: Compressed tables use zlib 1.2.11

2019-06-28 21:34:10 140603252493440 [Note] InnoDB: Using Linux native AIO

2019-06-28 21:34:10 140603252493440 [Note] InnoDB: Using SSE crc32 instructions

2019-06-28 21:34:10 140603252493440 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2019-06-28 21:34:10 140603252493440 [Note] InnoDB: Completed initialization of buffer pool

2019-06-28 21:34:10 140603252493440 [Note] InnoDB: Highest supported file format is Barracuda.

2019-06-28 21:34:10 140603252493440 [Note] InnoDB: 128 rollback segment(s) are active.

2019-06-28 21:34:10 140603252493440 [Note] InnoDB: Waiting for purge to start

2019-06-28 21:34:10 140603252493440 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.43-84.3 started; log sequence number 1616717

2019-06-28 21:34:10 140603252493440 [Note] Plugin 'FEEDBACK' is disabled.

2019-06-28 21:34:10 140602582759168 [Note] InnoDB: Dumping buffer pool(s) not yet started

2019-06-28 21:34:15 139818583317632 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2019-06-28 21:34:15 139818583317632 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2019-06-28 21:34:15 139818583317632 [Note] InnoDB: The InnoDB memory heap is disabled

2019-06-28 21:34:15 139818583317632 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2019-06-28 21:34:15 139818583317632 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2019-06-28 21:34:15 139818583317632 [Note] InnoDB: Compressed tables use zlib 1.2.11

2019-06-28 21:34:15 139818583317632 [Note] InnoDB: Using Linux native AIO

2019-06-28 21:34:15 139818583317632 [Note] InnoDB: Using SSE crc32 instructions

2019-06-28 21:34:15 139818583317632 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2019-06-28 21:34:15 13981858a3317632 [Note] InnoDB: Completed initialization of buffer pool

2019-06-28 21:34:15 139818583317632 [Note] InnoDB: Highest supported file format is Barracuda.

2019-06-28 21:34:15 139818583317632 [Note] InnoDB: 128 rollback segment(s) are active.

2019-06-28 21:34:15 139818583317632 [Note] InnoDB: Waiting for purge to start

2019-06-28 21:34:15 139818583317632 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.43-84.3 started; log sequence number 1616727

2019-06-28 21:34:15 139818583317632 [Note] Plugin 'FEEDBACK' is disabled.

2019-06-28 21:34:15 139817920755456 [Note] InnoDB: Dumping buffer pool(s) not yet started

2019-06-28 21:34:15 139818583317632 [Note] Server socket created on IP: '127.0.0.1'.

2019-06-28 21:34:15 139818583317632 [Note] /usr/sbin/mysqld: ready for connections.

Version: '10.1.40-MariaDB-0ubuntu0.18.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Ubuntu 18.04

2019-06-28 21:35:34 139818582521600 [Note] /usr/sbin/mysqld: Normal shutdown

2019-06-28 21:35:34 139818582521600 [Note] Event Scheduler: Purging the queue. 0 events

2019-06-28 21:35:34 139817979451136 [Note] InnoDB: FTS optimize thread exiting.

2019-06-28 21:35:34 139818582521600 [Note] InnoDB: Starting shutdown...

2019-06-28 21:35:35 139818582521600 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool

2019-06-28 21:35:37 139818582521600 [Note] InnoDB: Shutdown completed; log sequence number 1616737

2019-06-28 21:35:37 139818582521600 [Note] /usr/sbin/mysqld: Shutdown complete

Не запускается msql Падает mqsyl 5.6.17 после не понятное с mysql

7 незаменимых инструментов для управления контент-маркетингом в 2020 году

Google: заставить Googlebot сканировать сайт по HTTP/2 нельзя