Mysql 无法安装在 Ubuntu Server 20.04 上

Question 1

根本原因是软件包libpam-tmpdir（由https://github.com/konstruktoid/hardening/blob/master/scripts/17_packages）

此包改变所创建的文件或文件夹的格式mktemp。

和libpam-tmpdir：

root@test-ub-64:~# mktemp
/tmp/user/0/tmp.qqRG7A24WV

没有libpam-tmpdir：

root@test-ub-64:~# mktemp
/tmp/tmp.HIUu5D514X

使用的格式libpam-tmpdir打破剧本/var/lib/dpkg/info/mysql-server-8.0.postinst。

简单的方法是：

删除包
退出你的shell
创建新的 root shell
检查mktemp该文件是否类似于 /tmp/tmp.XXXXXXXXXX

Answer

根本原因是软件包libpam-tmpdir（由https://github.com/konstruktoid/hardening/blob/master/scripts/17_packages）

此包改变所创建的文件或文件夹的格式mktemp。

和libpam-tmpdir：

root@test-ub-64:~# mktemp
/tmp/user/0/tmp.qqRG7A24WV

没有libpam-tmpdir：

root@test-ub-64:~# mktemp
/tmp/tmp.HIUu5D514X

使用的格式libpam-tmpdir打破剧本/var/lib/dpkg/info/mysql-server-8.0.postinst。

简单的方法是：

删除包
退出你的shell
创建新的 root shell
检查mktemp该文件是否类似于 /tmp/tmp.XXXXXXXXXX

Question 2

这实际上不是对您的问题的回答，但在升级我的 Ubuntu 服务器（18.04 -> 20.04）后，我的 mysql-server 也遇到了类似的问题。

2020-10-03T16:07:22.635008Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.21-0ubuntu0.20.04.4)  (Ubuntu).
2020-10-03T16:07:23.415771Z 0 [Warning] [MY-011068] [Server] The syntax 'expire-logs-days' is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2020-10-03T16:07:23.417551Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.21-0ubuntu0.20.04.4) starting as process 2477739
2020-10-03T16:07:23.429381Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2020-10-03T16:07:24.553589Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2020-10-03T16:07:24.725172Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock
2020-10-03T16:07:25.048647Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2020-10-03T16:07:25.049185Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2020-10-03T16:07:25.057082Z 0 [ERROR] [MY-000067] [Server] unknown variable 'query_cache_limit=1M'.
2020-10-03T16:07:25.057711Z 0 [ERROR] [MY-010119] [Server] Aborting

和

2020-10-03T16:22:22.002048Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.21-0ubuntu0.20.04.4)  (Ubuntu).
2020-10-03T16:22:22.683274Z 0 [Warning] [MY-011068] [Server] The syntax 'expire-logs-days' is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2020-10-03T16:22:22.685313Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.21-0ubuntu0.20.04.4) starting as process 2495404
2020-10-03T16:22:22.698694Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2020-10-03T16:22:24.126243Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2020-10-03T16:22:24.323307Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock
2020-10-03T16:22:24.593481Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2020-10-03T16:22:24.593803Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2020-10-03T16:22:24.599233Z 0 [ERROR] [MY-000067] [Server] unknown variable 'query_cache_size=16M'.
2020-10-03T16:22:24.600082Z 0 [ERROR] [MY-010119] [Server] Aborting

因此我在文件 /etc/mysql/my.cnf 中注释了以下几行：

query_cache_limit  = 1M                                                           
query_cache_size        = 16M

并重新安装 mysql-server

sudo apt install mysql-server

我希望这篇文章能有所帮助

马丁

Answer

这实际上不是对您的问题的回答，但在升级我的 Ubuntu 服务器（18.04 -> 20.04）后，我的 mysql-server 也遇到了类似的问题。

2020-10-03T16:07:22.635008Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.21-0ubuntu0.20.04.4)  (Ubuntu).
2020-10-03T16:07:23.415771Z 0 [Warning] [MY-011068] [Server] The syntax 'expire-logs-days' is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2020-10-03T16:07:23.417551Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.21-0ubuntu0.20.04.4) starting as process 2477739
2020-10-03T16:07:23.429381Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2020-10-03T16:07:24.553589Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2020-10-03T16:07:24.725172Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock
2020-10-03T16:07:25.048647Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2020-10-03T16:07:25.049185Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2020-10-03T16:07:25.057082Z 0 [ERROR] [MY-000067] [Server] unknown variable 'query_cache_limit=1M'.
2020-10-03T16:07:25.057711Z 0 [ERROR] [MY-010119] [Server] Aborting

和

2020-10-03T16:22:22.002048Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.21-0ubuntu0.20.04.4)  (Ubuntu).
2020-10-03T16:22:22.683274Z 0 [Warning] [MY-011068] [Server] The syntax 'expire-logs-days' is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2020-10-03T16:22:22.685313Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.21-0ubuntu0.20.04.4) starting as process 2495404
2020-10-03T16:22:22.698694Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2020-10-03T16:22:24.126243Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2020-10-03T16:22:24.323307Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock
2020-10-03T16:22:24.593481Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2020-10-03T16:22:24.593803Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2020-10-03T16:22:24.599233Z 0 [ERROR] [MY-000067] [Server] unknown variable 'query_cache_size=16M'.
2020-10-03T16:22:24.600082Z 0 [ERROR] [MY-010119] [Server] Aborting

因此我在文件 /etc/mysql/my.cnf 中注释了以下几行：

query_cache_limit  = 1M                                                           
query_cache_size        = 16M

并重新安装 mysql-server

sudo apt install mysql-server

我希望这篇文章能有所帮助

马丁

Question 3

我花了很多时间在谷歌上搜索，浪费了很多时间，最终我得到了以下步骤，这些步骤对我有用

user@host:~$ mysql --version

导致

mysql Ver 8.0.22-0 ubuntu0.20.04.3 适用于 x86_64 上的 Linux ((Ubuntu))

首先停止所有 mysql 实例

sudo systemctl stop mysql.service

您还可以通过以下方式验证

ps ax | grep mysql

如果没有 mysql 进程/服务正在运行，则完全删除 mysql

sudo apt remove --purge mysql*

我也有强迫症，总是运行太多更新命令

sudo updatedb

然后重新启动（不确定是否有必要，但我还是这样做了）这是关键的区别....

sudo apt install mysql-server-core-8.0 mysql-server-8.0

瞧瞧——它真的有效了！

然后重新验证这一点，并确保它不是我在使用自己的机器时所做的更改，我快速启动了一个 GCP VPS，全新安装了 20.04LTS、NGINX，然后运行上述 MYSQL 安装命令——WayHay 验证通过！

这个故事的寓意是不要简单地安装“mysql-server”- 这通用版本在 20.04LTS 上失败。

现在我们有一个正在运行的 mysql，但无法访问 root

然后从这个链接（感谢@Partha Sen）https://stackoverflow.com/users/7056704/partha-sen）！！

我关注了 https://stackoverflow.com/questions/42153059/mysqld-safe-directory-var-run-mysqld-for-unix-socket-file-dont-exists

安全模式和重置mysql root密码的方法如下

sudo systemctl stop mysql.service

为了确保没有 mysql 进程正在运行，我检查了

ps ax | grep mysql

如果它们全部停止

sudo mysqld_safe --skip-grant-tables &

你应该得到以下回应

2021-01-24T12:20:39.840380Z mysqld_safe 记录到 '/var/log/mysql/error.log'。2021-01-24T12:20:39.870570Z mysqld_safe 使用来自 /var/lib/mysql 的数据库启动 mysqld 守护程序

如果是这样，那么这是个好消息 - 如果你没有得到好的回应并且mysql抱怨

“UNIX 套接字文件的 mysqld_safe 目录‘/var/run/mysqld’不存在。”

然后你需要添加以下附加步骤

sudo mkdir -p /var/run/mysqld
sudo chown mysql:mysql /var/run/mysqld

现在从你的 ssh 会话到同一台服务器的 linux 提示符 user@host:~$mysql 我得到了一个 sql 提示符 mysql>

然后在 mysql>提示符下 FLUSH PRIVILEGES；

ALTER USER 'root'@'localhost' IDENTIFIED BY 'n3w_p4$$w0rd';

将上面的“n3w_p4$$w0rd”修改为你选择的一个

然后

mysql>quit;

将带你回到Linux提示符

返回第一个 ssh 会话（带有 --skip grant tables 会话）并按 ctrl+c 终止“mysql --skip-grant-tables”会话

然后你需要以正常模式（不跳过授权表）重新启动 mysql，如下所示

sudo systemctl restart mysql.service

此时我再次重启了整个服务器

全部解决。

Answer