MySQL cannot be started after Fedora18 is installed

Source: Internet
Author: User
There are some differences between Fedora18 and earlier versions, so it cannot be the same as before. Run # yuminstallmysql-servermysql to start the mysql service and run # systemctlstartmysqld. service. However, Jobformysqld. servicefailed. See 'systemctlstatusmysqld. s

There are some differences between Fedora 18 and earlier versions, so it cannot be the same as before.

Use

# Yum install mysql-server mysql

After the installation is successful, start the mysql service and use

# Systemctl start mysqld. service
However, there will be the following problems: Job for mysqld. service failed. See 'systemctl status mysqld. service' and 'journalctl-xn 'for details.

Use

# Journalctl-xn,Prompt
-- Logs begin at 4 2013-04-11 16:13:02 CST, end at 4 2013-04-11 22:07:06 CST .--
April 11 22:05:47 localhost. localdomain failed-daemon [654]: reply [654]: [system] Rejected send message, 2 matched rules; type = "method_return", sender = ": 1.0
April 11 22:05:47 localhost. localdomain failed [654]: [system] Rejected send message, 2 matched rules; type = "method_return", sender = ": 1.0" (uid = 0 pid = 648 c
April 11 22:06:13 localhost. localdomain failed-daemon [654]: ** Message: No devices in use, exit
April 11 22:07:03 localhost. localdomain systemd [1]: Starting MySQL database server...
-- Subject: Unit mysqld. service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/7d4958e842da4a758f6c1cdc7b36dcc5
--
-- Unit mysqld. service has begun starting up.
April 11 22:07:03 localhost. localdomain mysqld_safe [7422]: 130411 22:07:03 mysqld_safe Logging to '/var/log/mysqld. log '.
April 11 22:07:04 localhost. localdomain mysqld_safe [7422]: 130411 22:07:04 mysqld_safe Starting mysqld daemon with databases from/var/lib/mysql
April 11 22:07:06 localhost. localdomain mysqld_safe [7422]: 130411 22:07:06 mysqld_safe mysqld from pid file/var/run/mysqld. pid ended
April 11 22:07:06 localhost. localdomain systemd [1]: mysqld. service: control process exited, code = exited status = 1
April 11 22:07:06 localhost. localdomain systemd [1]: Failed to start MySQL database server.
-- Subject: Unit mysqld. service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
--
-- Unit mysqld. service has failed.
--
-- The result is failed.
April 11 22:07:06 localhost. localdomain systemd [1]: Unit mysqld. service entered failed state

View/var/log/mysqld. log as follows:

[Root @ localhost log] # more mysqld. log
130413 13:45:12 mysqld_safe Starting mysqld daemon with databases from/var/lib/
Mysql
130413 13:45:12 [Note] Plugin 'federated 'is disabled.
/Usr/libexec/mysqld: Can't find file: './mysql/plugin. frm' (errno: 13)
130413 13:45:12 [ERROR] Can't open the mysql. plugin table. Please run mysql_upgr
Ade to create it.
130413 13:45:12 InnoDB: The InnoDB memory heap is disabled
130413 13:45:12 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130413 13:45:12 InnoDB: Compressed tables use zlib 1.2.7
130413 13:45:12 InnoDB: Using Linux native AIO
130413 13:45:12 InnoDB: Initializing buffer pool, size = 128.0 M
130413 13:45:12 InnoDB: Completed initialization of buffer pool
130413 13:45:12 InnoDB: highest supported file format is Barracuda.
130413 13:45:12 InnoDB: Waiting for the background threads to start
130413 13:45:13 InnoDB: 5.5.30 started; log sequence number 1595675
130413 13:45:13 [Note] Server hostname (bind-address): '0. 0.0.0 '; port: 3306
130413 13:45:13 [Note]-'0. 0.0.0 'resolves to '0. 0.0.0 ';
130413 13:45:13 [Note] Server socket created on IP: '0. 0.0.0 '.
130413 13:45:13 [ERROR]/usr/libexec/mysqld: Can't find file: './mysql/host. frm'
(Errno: 13)
130413 13:45:13 [ERROR] Fatal error: Can't open and lock privilege tables: Can't
Find file: './mysql/host. frm' (errno: 13)
130413 13:45:13 mysqld_safe mysqld from pid file/var/run/mysqld. pid ende
D
130413 13:48:32 mysqld_safe Starting mysqld daemon with databases from/var/lib/
Mysql
130413 13:48:32 [Note] Plugin 'federated 'is disabled.
/Usr/libexec/mysqld: Can't find file: './mysql/plugin. frm' (errno: 13)
130413 13:48:32 [ERROR] Can't open the mysql. plugin table. Please run mysql_upgr
Ade to create it.
130413 13:48:32 InnoDB: The InnoDB memory heap is disabled
130413 13:48:32 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130413 13:48:32 InnoDB: Compressed tables use zlib 1.2.7
130413 13:48:32 InnoDB: Using Linux native AIO
130413 13:48:32 InnoDB: Initializing buffer pool, size = 128.0 M
130413 13:48:32 InnoDB: Completed initialization of buffer pool
130413 13:48:32 InnoDB: highest supported file format is Barracuda.
130413 13:48:32 InnoDB: Waiting for the background threads to start
130413 13:48:33 InnoDB: 5.5.30 started; log sequence number 1595675
130413 13:48:33 [Note] Server hostname (bind-address): '0. 0.0.0 '; port: 3306
130413 13:48:33 [Note]-'0. 0.0.0 'resolves to '0. 0.0.0 ';
130413 13:48:33 [Note] Server socket created on IP: '0. 0.0.0 '.
130413 13:48:33 [ERROR]/usr/libexec/mysqld: Can't find file: './mysql/host. frm'
(Errno: 13)
130413 13:48:33 [ERROR] Fatal error: Can't open and lock privilege tables: Can't
Find file: './mysql/host. frm' (errno: 13)
130413 13:48:33 mysqld_safe mysqld from pid file/var/run/mysqld. pid ende
D

This indicates a permission issue.

# Cd/var/lib/mysql
# Chown mysql. mysql-R *
# Service mysqld start

At this time, mysql is successfully started ..

For more information about Fedora, see Fedora topics page http://www.linuxidc.com/topicnews.aspx? Tid = 5

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.