The mysql_upgrade errors look like the mysql command line client can't be located by the script... some kind of path error induced by a security "fix" I'm thinking
On 02/12/2015 12:37 PM, Cameron Mann wrote: > Hi all, > > I've encountered a problem with MySQL 5.6.23 on CentOS 7.0 and would > greatly appreciate any advice on what to do next. > > Synopsis: > > 1. Fresh install of CentOS 7.0 using minimal install ISO > 2. yum update -y > 3. rpm -i http://dev.mysql.com/get/mysql-community-release-el7-5.noarch.rpm > 4. yum install mysql-community-server -y > 5. service mysqld start > > After installing mysql-community-server 5.6.23 on a fresh minimal > install of CentOS 7.0 (running in VirtualBox 4.3.20) it will fail to > start with the following error: > > $ sudo service mysqld start > Redirecting to /bin/systemctl start mysqld.service > Job for mysqld.service failed. See 'systemctl status mysqld.service' > and 'journalctl -xn' for details. > > $ systemctl status mysqld.service > mysqld.service - MySQL Community Server > Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled) > Active: activating (start-post) since Thu 2015-02-12 20:07:08 UTC; > 1min 30s ago > Process: 5643 ExecStart=/usr/bin/mysqld_safe (code=exited, status=0/SUCCESS) > Process: 5632 ExecStartPre=/usr/bin/mysql-systemd-start pre > (code=exited, status=0/SUCCESS) > Main PID: 5643 (code=exited, status=0/SUCCESS); : 5644 > (mysql-systemd-s) > CGroup: /system.slice/mysqld.service > └─control > ├─5644 /bin/bash /usr/bin/mysql-systemd-start post > └─6115 sleep 1 > > Snippet from mysqld.log: > 150212 19:47:08 mysqld_safe Starting mysqld daemon with databases from > /var/lib/mysql > 2015-02-12 19:47:08 0 [Warning] TIMESTAMP with implicit DEFAULT value > is deprecated. Please use --explicit_defaults_for_timestamp server > option (see documentation for more details). > 2015-02-12 19:47:08 1244 [Warning] Buffered warning: Changed limits: > max_open_files: 1024 (requested 5000) > 2015-02-12 19:47:08 1244 [Warning] Buffered warning: Changed limits: > table_cache: 431 (requested 2000) > 2015-02-12 19:47:08 1244 [Note] Plugin 'FEDERATED' is disabled. > /usr/sbin/mysqld: Table 'mysql.plugin' doesn't exist > 2015-02-12 19:47:08 1244 [ERROR] Can't open the mysql.plugin table. > Please run mysql_upgrade to create it. > 2015-02-12 19:47:08 1244 [Note] InnoDB: Using atomics to ref count > buffer pool pages > 2015-02-12 19:47:08 1244 [Note] InnoDB: The InnoDB memory heap is disabled > 2015-02-12 19:47:08 1244 [Note] InnoDB: Mutexes and rw_locks use GCC > atomic builtins > 2015-02-12 19:47:08 1244 [Note] InnoDB: Memory barrier is not used > 2015-02-12 19:47:08 1244 [Note] InnoDB: Compressed tables use zlib 1.2.3 > 2015-02-12 19:47:08 1244 [Note] InnoDB: Using Linux native AIO > 2015-02-12 19:47:08 1244 [Note] InnoDB: Using CPU crc32 instructions > 2015-02-12 19:47:08 1244 [Note] InnoDB: Initializing buffer pool, size = > 128.0M > 2015-02-12 19:47:08 1244 [Note] InnoDB: Completed initialization of buffer > pool > InnoDB: Error: pthread_create returned 13 > 150212 19:47:08 mysqld_safe mysqld from pid file > /var/run/mysqld/mysqld.pid ended > > The suggested mysql_upgrade command gives the following output: > > $ mysql_upgrade > Looking for 'mysql' as: mysql > Looking for 'mysqlcheck' as: mysqlcheck > FATAL ERROR: Upgrade failed > > $ mysql_upgrade -uroot --password="" > Warning: Using a password on the command line interface can be insecure. > Looking for 'mysql' as: mysql > Looking for 'mysqlcheck' as: mysqlcheck > FATAL ERROR: Upgrade failed > > I've also observed the same behaviour on a CentOS 7.0 image (I believe > from http://cloud.centos.org) running in OpenStack under the KVM > hypervisor. I have not been able to test in a non-virtualized > environment. > > I've attempted rebooting before and after installation of > mysql-community-server to no effect. > > Previous versions of 5.6.x appear unaffected. > > Cameron Mann > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
