@CASPER01

Как запустить mysql?

На хостинг cloudstorm после просрочки оплаты отключили сайт, когда включили, не запускается mysql
systemctl status mysql.service
● mysql.service - MySQL Community Server
Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2019-03-22 16:01:22 CET; 13s ago
Process: 4664 ExecStart=/usr/sbin/mysqld --daemonize --pid-file=/run/mysqld/mysqld.pid (code=exited, status=1/FAILURE)
Process: 4644 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS)

Mar 22 16:01:21 vps640049 systemd[1]: mysql.service: Failed with result 'exit-code'.
Mar 22 16:01:21 vps640049 systemd[1]: Failed to start MySQL Community Server.
Mar 22 16:01:22 vps640049 systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Mar 22 16:01:22 vps640049 systemd[1]: mysql.service: Scheduled restart job, restart counter is at 5.
Mar 22 16:01:22 vps640049 systemd[1]: Stopped MySQL Community Server.
Mar 22 16:01:22 vps640049 systemd[1]: mysql.service: Start request repeated too quickly.
Mar 22 16:01:22 vps640049 systemd[1]: mysql.service: Failed with result 'exit-code'.
Mar 22 16:01:22 vps640049 systemd[1]: Failed to start MySQL Community Server.

Вот лог
2019-03-22T07:12:46.255307Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-03-22T07:12:46.255381Z 0 [Note] Shutting down plugin 'MEMORY'
2019-03-22T07:12:46.255401Z 0 [Note] Shutting down plugin 'CSV'
2019-03-22T07:12:46.255422Z 0 [Note] Shutting down plugin 'sha256_password'
2019-03-22T07:12:46.255429Z 0 [Note] Shutting down plugin 'mysql_native_password'
2019-03-22T07:12:46.261879Z 0 [Note] Shutting down plugin 'binlog'
2019-03-22T07:12:46.265966Z 0 [Note] /usr/sbin/mysqld: Shutdown complete

2019-03-22T08:06:51.080350Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-03-22T08:06:51.085126Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.25-0ubuntu0.18.04.2) starting as process 828 ...
2019-03-22T08:06:51.133762Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-03-22T08:06:51.133829Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-03-22T08:06:51.133840Z 0 [Note] InnoDB: Uses event mutexes
2019-03-22T08:06:51.133848Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-03-22T08:06:51.133862Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-03-22T08:06:51.133870Z 0 [Note] InnoDB: Using Linux native AIO
2019-03-22T08:06:51.142648Z 0 [Note] InnoDB: Number of pools: 1
2019-03-22T08:06:51.148938Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-03-22T08:06:51.157007Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-03-22T08:06:51.196461Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-03-22T08:06:51.213267Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-03-22T08:06:51.275232Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-03-22T08:06:51.618759Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-03-22T08:06:51.618877Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-03-22T08:06:51.619245Z 0 [Warning] InnoDB: Retry attempts for writing partial data failed.
2019-03-22T08:06:51.619266Z 0 [ERROR] InnoDB: Write to file ./ibtmp1failed at offset 0, 1048576 bytes should have been written, only 0 were written. Operating system error number 28. Check that your OS and file system support files of this size. Check also that the disk is not full or a disk quota exceeded.
2019-03-22T08:06:51.619279Z 0 [ERROR] InnoDB: Error number 28 means 'No space left on device'
2019-03-22T08:06:51.619285Z 0 [Note] InnoDB: Some operating system error numbers are described at dev.mysql.com/doc/refman/5.7/en/operating-system-e...
2019-03-22T08:06:51.619292Z 0 [ERROR] InnoDB: Could not set the file size of './ibtmp1'. Probably out of disk space
2019-03-22T08:06:51.619299Z 0 [ERROR] InnoDB: Unable to create the shared innodb_temporary
2019-03-22T08:06:51.619305Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2019-03-22T08:06:52.033029Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-03-22T08:06:52.033066Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2019-03-22T08:06:52.033077Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2019-03-22T08:06:52.033087Z 0 [ERROR] Failed to initialize builtin plugins.
2019-03-22T08:06:52.033093Z 0 [ERROR] Aborting

2019-03-22T08:06:52.033119Z 0 [Note] Binlog end
2019-03-22T08:06:52.033187Z 0 [Note] Shutting down plugin 'CSV'
2019-03-22T08:06:52.033550Z 0 [Note] /usr/sbin/mysqld: Shutdown complete

2019-03-22T08:06:52.729787Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-03-22T08:06:52.732065Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.25-0ubuntu0.18.04.2) starting as process 953 ...
2019-03-22T08:06:52.737297Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-03-22T08
  • Вопрос задан
  • 463 просмотра
Пригласить эксперта
Ответы на вопрос 1
dimonchik2013
@dimonchik2013
non progredi est regredi
мало текста

но начать можете с

Could not set the file size of './ibtmp1'. Probably out of disk space
Ответ написан
Комментировать
Ваш ответ на вопрос

Войдите, чтобы написать ответ

Войти через центр авторизации
Похожие вопросы