エラー内容
# /usr/bin/mysql_install_db FATAL ERROR: please install the following Perl modules before executing /usr/bin/mysql_install_db: Data::Dumper
対処
上記が出たら
# yum install -y perl-Data-Dumper
でData-Dumperモジュールを導入してmysql_install_dbを再実行
# /usr/bin/mysql_install_db WARNING: The host 'host' could not be looked up with /usr/bin/resolveip. This probably means that your libc libraries are not 100 % compatible with this binary MySQL version. The MySQL daemon, mysqld, should work normally with the exception that host name resolving will not work. This means that you should use IP addresses instead of hostnames when specifying MySQL privileges ! Installing MySQL system tables...2015-02-04 13:38:26 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2015-02-04 13:38:26 2940 [Note] InnoDB: Using atomics to ref count buffer pool pages 2015-02-04 13:38:26 2940 [Note] InnoDB: The InnoDB memory heap is disabled 2015-02-04 13:38:26 2940 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2015-02-04 13:38:26 2940 [Note] InnoDB: Memory barrier is not used 2015-02-04 13:38:26 2940 [Note] InnoDB: Compressed tables use zlib 1.2.3 2015-02-04 13:38:26 2940 [Note] InnoDB: Using Linux native AIO 2015-02-04 13:38:26 2940 [Note] InnoDB: Using CPU crc32 instructions 2015-02-04 13:38:26 2940 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2015-02-04 13:38:26 2940 [Note] InnoDB: Completed initialization of buffer pool 2015-02-04 13:38:26 2940 [Note] InnoDB: Highest supported file format is Barracuda. 2015-02-04 13:38:26 2940 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463 2015-02-04 13:38:26 2940 [Note] InnoDB: Database was not shutdown normally! 2015-02-04 13:38:26 2940 [Note] InnoDB: Starting crash recovery. 2015-02-04 13:38:26 2940 [Note] InnoDB: Reading tablespace information from the .ibd files... 2015-02-04 13:38:26 2940 [Note] InnoDB: Restoring possible half-written data pages 2015-02-04 13:38:26 2940 [Note] InnoDB: from the doublewrite buffer... InnoDB: Doing recovery: scanned up to log sequence number 1600607 2015-02-04 13:38:26 2940 [Note] InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percent: 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 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed 2015-02-04 13:38:27 2940 [Note] InnoDB: 128 rollback segment(s) are active. 2015-02-04 13:38:27 2940 [Note] InnoDB: Waiting for purge to start 2015-02-04 13:38:27 2940 [Note] InnoDB: 5.6.23 started; log sequence number 1600607 2015-02-04 13:38:27 2940 [Note] Binlog end 2015-02-04 13:38:27 2940 [Note] InnoDB: FTS optimize thread exiting. 2015-02-04 13:38:27 2940 [Note] InnoDB: Starting shutdown... 2015-02-04 13:38:29 2940 [Note] InnoDB: Shutdown completed; log sequence number 1625987 OK Filling help tables...2015-02-04 13:38:29 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2015-02-04 13:38:29 2964 [Note] InnoDB: Using atomics to ref count buffer pool pages 2015-02-04 13:38:29 2964 [Note] InnoDB: The InnoDB memory heap is disabled 2015-02-04 13:38:29 2964 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2015-02-04 13:38:29 2964 [Note] InnoDB: Memory barrier is not used 2015-02-04 13:38:29 2964 [Note] InnoDB: Compressed tables use zlib 1.2.3 2015-02-04 13:38:29 2964 [Note] InnoDB: Using Linux native AIO 2015-02-04 13:38:29 2964 [Note] InnoDB: Using CPU crc32 instructions 2015-02-04 13:38:29 2964 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2015-02-04 13:38:29 2964 [Note] InnoDB: Completed initialization of buffer pool 2015-02-04 13:38:29 2964 [Note] InnoDB: Highest supported file format is Barracuda. 2015-02-04 13:38:29 2964 [Note] InnoDB: 128 rollback segment(s) are active. 2015-02-04 13:38:29 2964 [Note] InnoDB: Waiting for purge to start 2015-02-04 13:38:29 2964 [Note] InnoDB: 5.6.23 started; log sequence number 1625987 2015-02-04 13:38:29 2964 [Note] Binlog end 2015-02-04 13:38:29 2964 [Note] InnoDB: FTS optimize thread exiting. 2015-02-04 13:38:29 2964 [Note] InnoDB: Starting shutdown... 2015-02-04 13:38:31 2964 [Note] InnoDB: Shutdown completed; log sequence number 1625997 OK To start mysqld at boot time you have to copy support-files/mysql.server to the right place for your system PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER ! To do so, start the server, then issue the following commands: /usr/bin/mysqladmin -u root password 'new-password' /usr/bin/mysqladmin -u root -h host password 'new-password' Alternatively you can run: /usr/bin/mysql_secure_installation which will also give you the option of removing the test databases and anonymous user created by default. This is strongly recommended for production servers. See the manual for more instructions. You can start the MySQL daemon with: cd /usr ; /usr/bin/mysqld_safe & You can test the MySQL daemon with mysql-test-run.pl cd mysql-test ; perl mysql-test-run.pl Please report any problems at http://bugs.mysql.com/ The latest information about MySQL is available on the web at http://www.mysql.com Support MySQL by buying support/licenses at http://shop.mysql.com New default config file was created as /usr/my.cnf and will be used by default by the server when you start it. You may edit this file to change server settings
