Bug 34956 - После обновления до MySQL-server-5.7.21-alt4.S1 не запускается
Summary: После обновления до MySQL-server-5.7.21-alt4.S1 не запускается
Status: CLOSED FIXED
Alias: None
Product: Sisyphus
Classification: Development
Component: MySQL-server (show other bugs)
Version: unstable
Hardware: all Linux
: P3 normal
Assignee: Anton Farygin
QA Contact: qa-sisyphus
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-28 16:51 MSK by Vitaly Lipatov
Modified: 2018-05-28 19:27 MSK (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vitaly Lipatov 2018-05-28 16:51:09 MSK
После обновления до MySQL-server-5.7.21-alt4.S1 не запускается:

# /etc/init.d/mysqld start
/etc/init.d/mysqld: line 36: [: missing `]'
Adjusting environment for mysqld:                                                                                                                                                                          [ DONE ]
Starting mysqld service: 2018-05-28T13:49:24.962562Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-05-28T13:49:24.966790Z 0 [ERROR] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!

2018-05-28T13:49:24.966855Z 0 [ERROR] Aborting

2018-05-28T13:49:24.966920Z 0 [Note] Binlog end
Initialization of mysqld failed: 0


Ну про [] это там пробел пропущен:
+ '[' '!' -d '/var/lib/mysql/db/mysql]'
/etc/init.d/mysqld: line 36: [: missing `]'
Comment 1 Vitaly Lipatov 2018-05-28 17:19:45 MSK
(В ответ на комментарий №0)
...> 2018-05-28T13:49:24.966790Z 0 [ERROR] Fatal error: Please read "Security"
> section of the manual to find out how to run mysqld as root!
Эта проблема решилась
# mv /etc/my.cnf.rpmnew /etc/my.cnf
 
 
> Ну про [] это там пробел пропущен:
> + '[' '!' -d '/var/lib/mysql/db/mysql]'
> /etc/init.d/mysqld: line 36: [: missing `]'
Эта остаётся

Далее запуск всё равно проваливается
# tail /var/lib/mysql/log/mysqld.log

2018-05-28T14:10:07.857727Z 0 [Warning] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
2018-05-28T14:10:07.857806Z 0 [ERROR] /usr/sbin/mysqld: Can't create/write to file '/var/lib/mysql/mysqld.pid' (Errcode: 2 - No such file or directory)
2018-05-28T14:10:07.857818Z 0 [ERROR] Can't start server: can't create PID file: No such file or directory
Comment 2 Vitaly Lipatov 2018-05-28 17:22:25 MSK
(В ответ на комментарий №1)
...

> 2018-05-28T14:10:07.857806Z 0 [ERROR] /usr/sbin/mysqld: Can't create/write to
> file '/var/lib/mysql/mysqld.pid' (Errcode: 2 - No such file or directory)
> 2018-05-28T14:10:07.857818Z 0 [ERROR] Can't start server: can't create PID
> file: No such file or directory
После создания симлинка
# ls /var/lib/mysql/var/lib/mysql  -l
lrwxrwxrwx 1 root root 15 мая 28 17:20 /var/lib/mysql/var/lib/mysql -> /var/lib/mysql/

получил ошибку
2018-05-28T14:20:56.019329Z 0 [ERROR] /usr/sbin/mysqld: Can't create/write to file '/var/lib/mysql/mysqld.pid' (Errcode: 40 - Too many levels of symbolic links)
2018-05-28T14:20:56.019341Z 0 [ERROR] Can't start server: can't create PID file: Too many levels of symbolic links

Уж явно путаница в чруте.
Comment 3 Anton Farygin 2018-05-28 19:23:38 MSK
mysql_upgrade нужно запустить. Смотри обновление пакета mysql в Sisyphus
Comment 4 Anton Farygin 2018-05-28 19:24:56 MSK
Вообще странно у тебя как-то отвалилось, у меня такого не наблюдается.
Системы правда на systemd.
Comment 5 Anton Farygin 2018-05-28 19:27:17 MSK
исправлено в 5.7.27-alt5