MySQL安装失败在线等
MySQL安装失败在线等谢谢大佬
Loaded plugins: fastestmirror
Determining fastest mirrors
One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Run the command with the repository temporarily disabled
yum --disablerepo=<repoid> ...
4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:
yum-config-manager --disable <repoid>
or
subscription-manager repos --disable=<repoid>
5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Run the command with the repository temporarily disabled
yum --disablerepo=<repoid> ...
4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:
yum-config-manager --disable <repoid>
or
subscription-manager repos --disable=<repoid>
5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
。。。。。。。
include/mysql.sh: line 400: cmake: command not found
你系统上系统源都无法正常工作，肯定会导致依赖包无法安装，所以也就安装失败了 一样的情况，尝试用了CENTOS的各种版本，包括UBUNTU18.04,都是到最后安装 MYSQL失败，然后单独安装 MYSQL也是失败。
看到这个贴子，更新了YUM源，改为阿里云的，依然失败。附上数据库安装日志。
附上1.8测试版数据库的安装日志，同样是安装失败。
tkinfo 发表于 2021-5-13 10:18
附上1.8测试版数据库的安装日志，同样是安装失败。
前面压缩包是空的，没有任何文件
ERROR: 1Can't create/write to file '/usr/local/mysql/var/mysql/db.MYI' (Errcode: 13)
你服务器上目录无法正常写入
不清楚你服务器是什么环境，如果所有系统安装都失败那就是你环境问题了
lnmp在目前主流vps服务商、pve、vmware上都测试过了
环境是移动云的EC云主机，那个报错之前也看了，当时就手工在目录下建立文件是正常的，目录是可以读写的，但是MYSQL安装完成后，数据库mysql是目录确实是空的,所以用CENTOS的7。3试到7。7都不行，然后装了UBUNTU，还是一同样的错误，系统盘大小是20G，但是装LNMP环境也足够用了吧
本帖最后由 tkinfo 于 2021-5-13 17:42 编辑
附上安装完成后数据库目录的截图
手工建立文件夹操作都是正常的。
PS：系统 提示今日无法上传更多附件，图片暂时上传不了。
https://ftp.bmp.ovh/imgs/2021/05/a47fd70c0021a63b.png tkinfo 发表于 2021-5-13 17:49
检查 /tmp 是否可写，是否单独的分区，是否已满
方便的话短消息ip、root密码我测试看看 已发送，请查收 。 tkinfo 发表于 2021-5-17 09:07
已发送，请查收 。
不确定什么问题，如screen运行中有被kill了现象
有可能系统有安全组件拦截之类的
建议不要使用移动云自带的系统，我尝试dd重装系统貌似好像没成功不清楚原因，建议看看后台上有没有挂载iso的选项 恩，看来是移动云的问题，我在阿里云上新开一个轻量云服务器，安装正常。
看来LNMP目前不太适合用移动云的主机。
页:
[1]