CentOS6.5启动MariaDB错误
2017-05-01 00:00
225 查看
摘要: MariaDB
初始化数据库,指定数据存储路径
[root@localhost ~]# /etc/init.d/mysql start Starting MySQL.170430 23:07:56 mysqld_safe Logging to '/home/mysql/db/mianbao/localhost.localdomain.err'. 170430 23:07:56 mysqld_safe Starting mysqld daemon with databases from /home/mysql/db/mianbao /usr/bin/mysqld_safe_helper: Can't create/write to file '/home/mysql/db/mianbao/localhost.localdomain.err' (Errcode: 2 "No such file or directory") . ERROR!
[root@localhost mianbao]# tail -f localhost.localdomain.err 170430 23:08:57 [Note] InnoDB: Creating tablespace and datafile system tables. 170430 23:08:57 [Note] InnoDB: Tablespace and datafile system tables created. 170430 23:08:57 [Note] InnoDB: Waiting for purge to start 170430 23:08:57 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 0 170430 23:08:57 [Note] Plugin 'FEEDBACK' is disabled. 170430 23:08:57 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 170430 23:08:57 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist 170430 23:08:57 [Note] Server socket created on IP: '127.0.0.1'. 170430 23:08:57 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist 170430 23:08:57 mysqld_safe mysqld from pid file /home/mysql/db/mianbao/localhost.localdomain.pid ended
初始化数据库,指定数据存储路径
[root@localhost mianbao]# mysql_install_db --user=mysql --datadir=/home/mysql/db/mianbao/ Installing MariaDB/MySQL system tables in '/home/mysql/db/mianbao/' ... 170430 23:14:18 [Note] /usr/sbin/mysqld (mysqld 10.0.30-MariaDB) starting as process 46784 ... 170430 23:14:18 [Note] InnoDB: Using mutexes to ref count buffer pool pages 170430 23:14:18 [Note] InnoDB: The InnoDB memory heap is disabled 170430 23:14:18 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 170430 23:14:18 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 170430 23:14:18 [Note] InnoDB: Compressed tables use zlib 1.2.3 170430 23:14:18 [Note] InnoDB: Using Linux native AIO 170430 23:14:18 [Note] InnoDB: Using CPU crc32 instructions 170430 23:14:18 [Note] InnoDB: Initializing buffer pool, size = 128.0M 170430 23:14:18 [Note] InnoDB: Completed initialization of buffer pool 170430 23:14:18 [Note] InnoDB: Highest supported file format is Barracuda. 170430 23:14:18 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463 170430 23:14:18 [Note] InnoDB: Database was not shutdown normally! 170430 23:14:18 [Note] InnoDB: Starting crash recovery. 170430 23:14:18 [Note] InnoDB: Reading tablespace information from the .ibd files... 170430 23:14:18 [Note] InnoDB: Restoring possible half-written data pages 170430 23:14:18 [Note] InnoDB: from the doublewrite buffer... InnoDB: Doing recovery: scanned up to log sequence number 1600607 170430 23:14:18 [Note] InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percent: 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 170430 23:14:18 [Note] InnoDB: 128 rollback segment(s) are active. 170430 23:14:18 [Note] InnoDB: Waiting for purge to start 170430 23:14:18 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 1600607 170430 23:14:19 [Note] InnoDB: FTS optimize thread exiting. 170430 23:14:19 [Note] InnoDB: Starting shutdown... 170430 23:14:20 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool 170430 23:14:22 [Note] InnoDB: Shutdown completed; log sequence number 1616707 OK Filling help tables... 170430 23:14:22 [Note] /usr/sbin/mysqld (mysqld 10.0.30-MariaDB) starting as process 46814 ... 170430 23:14:22 [Note] InnoDB: Using mutexes to ref count buffer pool pages 170430 23:14:22 [Note] InnoDB: The InnoDB memory heap is disabled 170430 23:14:22 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 170430 23:14:22 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 170430 23:14:22 [Note] InnoDB: Compressed tables use zlib 1.2.3 170430 23:14:22 [Note] InnoDB: Using Linux native AIO 170430 23:14:22 [Note] InnoDB: Using CPU crc32 instructions 170430 23:14:22 [Note] InnoDB: Initializing buffer pool, size = 128.0M 170430 23:14:22 [Note] InnoDB: Completed initialization of buffer pool 170430 23:14:22 [Note] InnoDB: Highest supported file format is Barracuda. 170430 23:14:22 [Note] InnoDB: 128 rollback segment(s) are active. 170430 23:14:22 [Note] InnoDB: Waiting for purge to start 170430 23:14:22 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 1616707 170430 23:14:22 [Note] InnoDB: FTS optimize thread exiting. 170430 23:14:22 [Note] InnoDB: Starting shutdown... 170430 23:14:23 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool 170430 23:14:25 [Note] InnoDB: Shutdown completed; log sequence number 1616717 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 MariaDB 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 localhost.localdomain 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 MariaDB Knowledgebase at http://mariadb.com/kb or the MySQL manual for more instructions. You can start the MariaDB daemon with: cd '/usr' ; /usr/bin/mysqld_safe --datadir='/home/mysql/db/mianbao/' You can test the MariaDB daemon with mysql-test-run.pl cd '/usr/mysql-test' ; perl mysql-test-run.pl Please report any problems at http://mariadb.org/jira The latest information about MariaDB is available at http://mariadb.org/. You can find additional information about the MySQL part at: http://dev.mysql.com Consider joining MariaDB's strong and vibrant community: https://mariadb.org/get-involved/ [root@localhost mianbao]# /etc/init.d/mysql start Starting MySQL.170430 23:14:34 mysqld_safe Logging to '/home/mysql/db/mianbao/localhost.localdomain.err'. 170430 23:14:34 mysqld_safe Starting mysqld daemon with databases from /home/mysql/db/mianbao SUCCESS!
相关文章推荐
- Centos 6.5启动 an error occurred during the file system check错误的解决
- CentOS 6.5安装libvirt启动不了libvirtd进程的错误
- CentOS 4000 6.5 xinetd启动/重启错误
- 双十一前4小时,CentOS 6.5server启动错误排查
- 【CentOS 6.5】QtCreator启动时关于dbus-1的错误解决方法
- CentOS6.5 mysql5.6 启动错误 server PID file could not be found
- Centos 6.5启动 an error occurred during the file system check错误的解决
- 双十一前4小时,CentOS 6.5服务器启动错误排查
- vmware 下启动centos6.5 出现内部错误
- 修改centos6.3启动级别以及启动级别配置错误的修改问题
- CentOS 6.5,64bit 上安装MariaDB
- centos 6.5 64 eth0不能自动启动?原来是network的问题
- CentOS (linux) 启动错误 *** Run 'setenforce 1'to reenable. 解决
- CentOS6.5 安装Python2.7后, yum出现“No module named yum”错误
- vmware 安装centos 启动时弹出“内部错误”
- CentOS 6.5 MySQL/MariaDB数据备份与恢复备份详解
- 【CentOS 6.5】 Qt Creator 启动失败
- CentOS hadoop启动错误 JAVA_HOME is not set and could not be found
- 总结之:CentOS 6.5 MariaDB或MySQL主从复制详解 推荐
- 解决MyEclipse6.5启动错误或中途崩溃自动关闭jvm terminated. exit code 1 的错误