blocks|key|663106|text|我的问题的根源似乎是selinux，它在操作系统安装时自动打开(强制)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|663107|我希望我的mysql是/data格式的。|663108|在验证my.cnf具有以下内容之后：|663109|datadir=/data/mysql|code-block|syntax|javascript|663110|(并将套接字保留在/var/lib/mysql)我执行命令关闭mysqld的selinux+(另一种方法是完全关闭它)：|663111|setsebool+-P+mysqld_disable_trans=1|663112|我运行了以下命令：|663113|>+chown+-R+mysql+.
>+chgrp+-R+mysql+.
>+mysql_install_db+--user=mysql|663114|我启动了mysql守护进程，之后一切都运行得很好。|663115|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|Z|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|11|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|12|8|@]|9|@]|A|$]]|$1|Q|3|R|5|H|7|13|8|@]|9|@]|A|$I|J]]|$1|S|3|T|5|6|7|14|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

The root of my problem seemed to be selinux, which was turned on (enforcing)
automatically on OS install.

I wanted my mysql in /data.

After verifying that my.cnf had:

<pre><code>datadir=/data/mysql
</code></pre>

(and leaving the socket at /var/lib/mysql) 
I executed the command to turn off selinux for mysqld 
(alternative is to turn it off completely):

<pre><code>setsebool -P mysqld_disable_trans=1
</code></pre>

I ran the following commands:

<pre><code>&gt; chown -R mysql .
&gt; chgrp -R mysql .
&gt; mysql_install_db --user=mysql
</code></pre>

I started the mysql daemon and everything worked fine after that.

blocks|key|663175|text|对于我自己，我必须这样做：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|663176|yum+remove+mysql*

rm+-rf+/var/lib/mysql/
cp+/etc/my.cnf+~/my.cnf.bkup

yum+install+-y+mysql-server+mysql-client

mysql_install_db

chown+-R+mysql:mysql+/var/lib/mysql
chown+-R+mysql:mysql+/var/log/mysql

service+mysql+start|code-block|syntax|javascript|663177|然后，我能够回到我的数据库，并在第一次启动后再次配置它们。|663178|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

For myself, I had to do:

<pre><code>yum remove mysql*

rm -rf /var/lib/mysql/
cp /etc/my.cnf ~/my.cnf.bkup

yum install -y mysql-server mysql-client

mysql_install_db

chown -R mysql:mysql /var/lib/mysql
chown -R mysql:mysql /var/log/mysql

service mysql start
</code></pre>

Then I was able to get back into my databases and configure them again after I nuked them the first go around.

blocks|key|663236|text|在CentOS+EL+6和更早的版本上，有一种方法可以陷入同样的混乱。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|663237|使用最少的安装来安装CentOS+EL6。例如，我使用kickstart安装了以下内容：|663238|%25packages
@core
acpid
bison
cmake
dhcp-common
flex
gcc
gcc-c%2B%2B
git
libaio-devel
make
man
ncurses-devel
perl
ntp
ntpdate
pciutils
tar
tcpdump
wget
%25end|code-block|syntax|javascript|663239|您会发现上述列表的其中一个依赖项是mysql-libs。我发现我的系统在/etc中有一个默认的my.cnf，它包含：|offset|length|style|CODE|663240|[mysqld]
dataddir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
#+Disabling+symbolic-links+is+recommended+to+prevent+assorted+security+risks
symbolic-links=0

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid|663241|当您从Generic+Linux+(Architecture+Independent),+Compressed+TAR+Archive构建时，您的默认数据目录是/usr/local/mysql/data，这与已经存在的定义datadir=/var/lib/mysql的/etc/my.cnf冲突。同样，在同一文件中定义的pid-file没有权限让mysql用户/组在/var/run/mysqld中对其进行写操作。|663242|一个快速的补救方法是使用mv+/etc/my.cnf+/etc/my.cnf.old，它可以让你的通用源程序正常工作。|663243|当然，使用源RPM的体验是不同的。|663244|entityMap^0|0|0|0|H|A|10|4|1B|6|0|0|3|1S|28|L|33|M|3Q|B|4G|8|53|F|0|C|U|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|11|8|@$K|12|L|13|M|N]|$K|14|L|15|M|N]|$K|16|L|17|M|N]]|9|@]|A|$]]|$1|O|3|P|5|F|7|18|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|19|8|@$K|1A|L|1B|M|N]|$K|1C|L|1D|M|N]|$K|1E|L|1F|M|N]|$K|1G|L|1H|M|N]|$K|1I|L|1J|M|N]|$K|1K|L|1L|M|N]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1M|8|@$K|1N|L|1O|M|N]]|9|@]|A|$]]|$1|U|3|V|5|6|7|1P|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|X|$]]

On CentOS EL 6 and perhaps on earlier versions there is one way to get into this same mess.

Install CentOS EL6 with a minimal installation. For example I used kickstart to install the following:

<pre><code>%packages
@core
acpid
bison
cmake
dhcp-common
flex
gcc
gcc-c++
git
libaio-devel
make
man
ncurses-devel
perl
ntp
ntpdate
pciutils
tar
tcpdump
wget
%end
</code></pre>

You will find that one of the dependencies of the above list is <code>mysql-libs</code>. I found that my system has a default <code>my.cnf</code> in <code>/etc</code> and this contains:

<pre><code>[mysqld]
dataddir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
</code></pre>

When you build from the <code>Generic Linux (Architecture Independent), Compressed TAR Archive</code> your default data directory is <code>/usr/local/mysql/data</code> which conflicts with the <code>/etc/my.cnf</code> already present which defines <code>datadir=/var/lib/mysql</code>. Also the <code>pid-file</code> defined in the same file does not have permissions for the mysql user/group to write to it in <code>/var/run/mysqld</code>. 

A quick remedy is to <code>mv /etc/my.cnf /etc/my.cnf.old</code> which should get your generic source procedure working. 

Of course the experience is different of you use the source RPMs.

blocks|key|449026|text|在chown和chgrp'ing+/var/lib/mysql+per+chown+by+@Bad+Programmer之后，您可能还必须执行以下命令：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|449027|sudo+mysql_install_db+--user=mysql+--ldata=/var/lib/mysql|code-block|syntax|javascript|449028|然后重新启动mysqld。|449029|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/9099557/55075^0|1|5|7|5|H|E|10|5|19|F|0|0|0|6|6|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@$9|13|A|14|1|15]]|E|$]]|$1|F|3|G|5|H|7|16|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

After <code>chown</code> and <code>chgrp</code>'ing <code>/var/lib/mysql</code> per the answer by <a href="https://stackoverflow.com/a/9099557/55075">@Bad Programmer</a>, you may also have to execute the following command:

<pre><code>sudo mysql_install_db --user=mysql --ldata=/var/lib/mysql
</code></pre>

Then restart your <code>mysqld</code>.

blocks|key|449129|text|我在尝试启动服务器时也遇到了同样的问题，并遵循了“检查”的解决方案。但还是有问题。问题是我的/etc/my.cnf文件没有指向我定义的指定数据目录，因为我在执行mysql_install_db时定义了--datadir。一旦我更新了它，服务器就正确地启动了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|449130|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same issue in trying to start the server and followed the "checked" solution.
But still had the problem. The issue was the my /etc/my.cnf file was not pointing to my
designated datadir as defined when I executed the mysql_install_db with --datadir defined. Once I updated this, the server started correctly.

blocks|key|663422|text|mysql_install_db+–-user=mysql+--ldata=/var/lib/mysql|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|663423|在Centos+7中为我工作|unstyled|663424|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>mysql_install_db –-user=mysql --ldata=/var/lib/mysql
</code></pre>

Worked for me in Centos 7

blocks|key|449260|text|我在Ubuntu14.04.2LTS上的情况与其他使用my.cnf的情况类似，但对我来说，原因是一个~/.my.cnf，它是上一个安装过程中遗留下来的。在删除该文件并清除/重新安装mysql-server之后，它工作得很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|449261|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

My case on Ubuntu 14.04.2 LTS was similar to others with my.cnf, but for me the cause was a ~/.my.cnf that was leftover from a previous installation. After deleting that file and purging/re-installing mysql-server, it worked fine.

blocks|key|663571|text|在windows上启动前初始化mysql。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|663572|mysqld+--initialize|code-block|syntax|javascript|663573|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

initialize mysql before start on windows.

<pre><code>mysqld --initialize
</code></pre>

blocks|key|449414|text|下载mysql+zip版本时，如果直接运行mysqld，会得到这样的错误:+2016-02-18T07:23:48.318481Z+0错误致命错误:无法打开并锁定权限表:表'mysql.user‘不存在2016-02-18T07:23:48.319482Z+0中止|type|unstyled|depth|inlineStyleRanges|entityRanges|data|449415|您必须首先运行以下命令:+mysqld+--initialize|449416|在执行此命令之前，请确保您的数据文件夹为空。|449417|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

When download mysql zip version, if run mysqld directly, you'll get this error: 
2016-02-18T07:23:48.318481Z 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist
2016-02-18T07:23:48.319482Z 0 [ERROR] Aborting

You have to run below command first: 
mysqld --initialize

Make sure your data folder is empty before this command.

blocks|key|663888|text|仅此命令就足以在centos+6.6上施展魔法|type|unstyled|depth|inlineStyleRanges|entityRanges|data|663889|mysql_install_db|663890|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Just this command is enough to do the magic on centos 6.6 

mysql_install_db

blocks|key|663965|text|我在arch+linux上也遇到过这个问题。问题是pacman将软件包安装在与MySQL预期不同的位置。我能够用这个来解决这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|663966|sudo+mysql_install_db+--user=mysql+--basedir=/usr/+--ldata=/var/lib/mysql/|code-block|syntax|javascript|663967|希望这对某些人有帮助！|663968|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I had this issue on arch linux as well. The issue was pacman installed the package in a different location than MySQL was expecting. I was able to fix the issue with this:

<pre><code>sudo mysql_install_db --user=mysql --basedir=/usr/ --ldata=/var/lib/mysql/
</code></pre>

Hope this helps someone!

blocks|key|664091|text|我刚刚在OSX上的MySQL5.7上遇到了同样的问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|664092|rm+-rf+{datadir}
mysqld+--initialize+--datadir+{datadir}
mysqld+--datadir+{datadir}|code-block|syntax|javascript|664093|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I just met the same problem with mysql 5.7 on OSX:

<pre><code>rm -rf {datadir}
mysqld --initialize --datadir {datadir}
mysqld --datadir {datadir}
</code></pre>

blocks|key|449855|text|如果您的服务器曾经愉快地运行MySQL，但现在给出此错误，则卸载并重新安装MySQL是多余的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|449856|在我的例子中，服务器死了，并占用了几个磁盘块。这影响了一些文件，包括/var/lib/mysql/mysql/host.frm和/var/lib/mysql/mysql/proc.frm|449857|幸运的是，我可以从另一台服务器上复制这些文件，这让我克服了那个表错误。|449858|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

If you have a server which used to happily run MySQL, but now gives this error, then an uninstall and re-install of MySQL is overkill.

In my case, the server died and took a few disk blocks with it. This affected a few files, including /var/lib/mysql/mysql/host.frm and /var/lib/mysql/mysql/proc.frm

Luckily, I could copy these from another server, and this got me past that table error.

blocks|key|664236|text|我在overlayfs+(overlay2)上得到了类似的错误，这是Docker+for+Mac上的默认错误。使用mysql创建镜像后，在镜像上启动mysql时出错。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|664237|2017-11-15T06:44:22.141481Z+0+[ERROR]+Fatal+error:+Can't+open+and+lock+privilege+tables:+Table+storage+engine+for+'user'+doesn't+have+this+option|code-block|syntax|javascript|664238|切换到"aufs“解决了这个问题。(在Docker+for+Mac上，可以通过选择"Preferences...“来编辑"daemon.json”。菜单，选择“守护程序”选项卡，然后选择“高级”选项卡。)|664239|/etc/docker/daemon.json：|664240|{
++"storage-driver"+:+"aufs",
++"debug"+:+true,
++"experimental"+:+true
}|664241|参考：|664242|https://github.com/moby/moby/issues/35503|offset|length|664243|https://qiita.com/Hige-Moja/items/7b1208f16997e2aa9028|664244|entityMap|0|LINK|mutability|MUTABLE|url|1^0|0|0|0|0|0|0|0|15|0|0|0|1I|1|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|14|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|15|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|16|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|17|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|18|8|@]|9|@$Q|19|R|1A|1|1B]]|A|$]]|$1|S|3|T|5|6|7|1C|8|@]|9|@$Q|1D|R|1E|1|1F]]|A|$]]|$1|U|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|P]]|11|$5|X|Y|Z|A|$10|T]]]]

I got similar error on overlayfs (overlay2) that is the default on Docker for Mac.
The error happens when starting mysql on the image, after creating a image with mysql.

<pre><code>2017-11-15T06:44:22.141481Z 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table storage engine for 'user' doesn't have this option
</code></pre>

Switching to "aufs" solved the issue.
(On Docker for Mac, the "daemon.json" can be edited by choosing "Preferences..." menu, and selecting "Daemon" tab, and selecting "Advanced" tab.)

/etc/docker/daemon.json :

<pre><code>{
 "storage-driver" : "aufs",
 "debug" : true,
 "experimental" : true
}
</code></pre>

Ref:

<a href="https://github.com/moby/moby/issues/35503" rel="nofollow noreferrer">https://github.com/moby/moby/issues/35503</a>

<a href="https://qiita.com/Hige-Moja/items/7b1208f16997e2aa9028" rel="nofollow noreferrer">https://qiita.com/Hige-Moja/items/7b1208f16997e2aa9028</a>

blocks|key|664372|text|在Windows中，以管理员身份在命令提示符下运行以下命令|type|unstyled|depth|inlineStyleRanges|entityRanges|data|664373|Step+1:
mysql_install_db.exe

Step+2:
mysqld+--initialize

Step+3:
mysqld+--console

Step+4:
In+windows

Step+4:
mysqladmin+-u+root+password+"XXXXXXX"

Step+5:
mysql+-u+root+-p|code-block|syntax|javascript|664374|​|664375|📷|atomic|offset|length|664376|664377|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/880f9d20b871eec82b56cca5a072d754.png|imageAlt^0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Y|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Z|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|10|8|@]|9|@$L|11|M|12|1|13]]|A|$]]|$1|N|3|H|5|6|7|14|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V|W|-4]]]]

In Windows run the following commands in the command prompt as adminstrator
<pre><code>Step 1:
mysql_install_db.exe

Step 2:
mysqld --initialize

Step 3:
mysqld --console

Step 4:
In windows

Step 4:
mysqladmin -u root password &quot;XXXXXXX&quot;

Step 5:
mysql -u root -p
</code></pre>
<a href="https://i.stack.imgur.com/lB6XO.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/lB6XO.png" alt="Mariadb database information" /></a>

I am on a server that has afresh install on RHEL 5. I was able to install Apache and PHP just fine., but I am having serious trouble with my MySQL installation. I tried the following:

<pre><code>yum install mysql-server mysql 
</code></pre>

And didn't get any errors or conflicts. Then I tried to start mysql with the following commands:

<pre><code>chkconfig --levels 235 mysqld on
service mysqld start
</code></pre>

And get <code>Timeout error occurred trying to start MySQL Daemon.</code> 

I checked my logs and see this error:

<pre><code>[ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist
</code></pre>

I'm not sure where to go from here.

For reference I am using RHEL 5 and installed the latest versions of PHP 5 and Apache.

Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist

数据库

服务器

Windows

Docker

CentOS

MySQL

Linux

我在一台服务器上重新安装了RHEL5，我可以很好地安装Apache和PHP，但是我的MySQL安装出了严重的问题。我尝试了以下几种方法：yum install mysql-server mysql 并且没有收到任何错误或冲突。然后，我尝试使用以下命令启动mysql：chkconfig --levels 235 mysq...

问致命错误:无法打开和锁定权限表:表'mysql.host‘不存在
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问致命错误:无法打开和锁定权限表:表'mysql.host‘不存在EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问致命错误:无法打开和锁定权限表:表'mysql.host‘不存在
EN