MySQL登录010119报错_MySQL无法启动,求解,在线等

2018-05-26T06:28:24.032571Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.11) starting as process 13143

2018-05-26T06:28:24.062933Z 1 [ERROR] [MY-012592] [InnoDB] InnoDB: Operating system error number 2 in a file operation.

2018-05-26T06:28:24.062972Z 1 [ERROR] [MY-012593] [InnoDB] InnoDB: The error means the system cannot find the path specified.

2018-05-26T06:28:24.062980Z 1 [ERROR] [MY-012594] [InnoDB] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.

2018-05-26T06:28:24.062989Z 1 [ERROR] [MY-012646] [InnoDB] InnoDB: File ./ibdata1: 'open' returned OS error 71. Cannot continue operation

2018-05-26T06:28:24.062999Z 1 [ERROR] [MY-012981] [InnoDB] InnoDB: Cannot continue operation.

2018-05-26T06:28:25.172069Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.11) starting as process 13178

2018-05-26T06:28:25.201941Z 1 [ERROR] [MY-012592] [InnoDB] InnoDB: Operating system error number 2 in a file operation.

2018-05-26T06:28:25.201976Z 1 [ERROR] [MY-012593] [InnoDB] InnoDB: The error means the system cannot find the path specified.

2018-05-26T06:28:25.201985Z 1 [ERROR] [MY-012594] [InnoDB] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.

2018-05-26T06:28:25.201993Z 1 [ERROR] [MY-012646] [InnoDB] InnoDB: File ./ibdata1: 'open' returned OS error 71. Cannot continue operation

2018-05-26T06:28:25.202002Z 1 [ERROR] [MY-012981] [InnoDB] InnoDB: Cannot continue operation.

2018-05-26T06:28:26.428896Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.11) starting as process 13214

2018-05-26T06:28:26.461862Z 1 [ERROR] [MY-012592] [InnoDB] InnoDB: Operating system error number 2 in a file operation.

2018-05-26T06:28:26.461906Z 1 [ERROR] [MY-012593] [InnoDB] InnoDB: The error means the system cannot find the path specified.

2018-05-26T06:28:26.461914Z 1 [ERROR] [MY-012594] [InnoDB] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.

2018-05-26T06:28:26.461924Z 1 [ERROR] [MY-012646] [InnoDB] InnoDB: File ./ibdata1: 'open' returned OS error 71. Cannot continue operation

2018-05-26T06:28:26.461933Z 1 [ERROR] [MY-012981] [InnoDB] InnoDB: Cannot continue operation.

2018-05-26T06:28:27.662607Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.11) starting as process 13248

2018-05-26T06:28:27.692006Z 1 [ERROR] [MY-012592] [InnoDB] InnoDB: Operating system error number 2 in a file operation.

2018-05-26T06:28:27.692041Z 1 [ERROR] [MY-012593] [InnoDB] InnoDB: The error means the system cannot find the path specified.

2018-05-26T06:28:27.692048Z 1 [ERROR] [MY-012594] [InnoDB] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.

2018-05-26T06:28:27.692058Z 1 [ERROR] [MY-012646] [InnoDB] InnoDB: File ./ibdata1: 'open' returned OS error 71. Cannot continue operation

2018-05-26T06:28:27.692067Z 1 [ERROR] [MY-012981] [InnoDB] InnoDB: Cannot continue operation.

2018-05-26T06:28:28.925266Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.11) starting as process 13284

2018-05-26T06:28:28.954619Z 1 [ERROR] [MY-012592] [InnoDB] InnoDB: Operating system error number 2 in a file operation.

2018-05-26T06:28:28.954652Z 1 [ERROR] [MY-012593] [InnoDB] InnoDB: The error means the system cannot find the path specified.

2018-05-26T06:28:28.954660Z 1 [ERROR] [MY-012594] [InnoDB] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.

2018-05-26T06:28:28.954676Z 1 [ERROR] [MY-012646] [InnoDB] InnoDB: File ./ibdata1: 'open' returned OS error 71. Cannot continue operation

2018-05-26T06:28:28.954685Z 1 [ERROR] [MY-012981] [InnoDB] InnoDB: Cannot continue operation.

2018-05-26T06:29:50.995170Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.11) starting as process 13400

2018-05-26T06:29:53.138642Z 1 [ERROR] [MY-010781] [Server] Found ./mysql/index_stats.frm file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.

2018-05-26T06:29:53.138675Z 1 [ERROR] [MY-010336] [Server] Found .frm file with same name as one of the Dictionary Tables.

2018-05-26T06:29:53.138856Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.

2018-05-26T06:29:53.138886Z 0 [ERROR] [MY-010119] [Server] Aborting

2018-05-26T06:29:54.760802Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.11) MySQL Community Server - GPL.

2018-05-26T06:29:54.760902Z 0 [ERROR] [MY-010065] [Server] Failed to shutdown components infrastructure.

2018-05-26T07:18:31.679961Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.11) starting as process 15975

2018-05-26T07:18:32.081626Z 1 [ERROR] [MY-010781] [Server] Found ./mysql/index_stats.frm file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.

2018-05-26T07:18:32.081651Z 1 [ERROR] [MY-010336] [Server] Found .frm file with same name as one of the Dictionary Tables.

2018-05-26T07:18:32.081857Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.

2018-05-26T07:18:32.081887Z 0 [ERROR] [MY-010119] [Server] Aborting

2018-05-26T07:18:33.407529Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.11) MySQL Community Server - GPL.

2018-05-26T07:18:33.407655Z 0 [ERROR] [MY-010065] [Server] Failed to shutdown components infrastructure

systemctl status mysqld.service

● mysqld.service - MySQL Server

Loaded: loaded (/usr/lib/systemd/system/mysqld.service; bad; vendor preset: disabled)

Active: failed (Result: exit-code) since Sat 2018-05-26 15:18:33 CST; 5s ago

Docs: man:mysqld(8)

http://dev.mysql.com/doc/refman/en/using-systemd.html

Process: 15975 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS (code=exited, status=1/FAILURE)

Process: 15958 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=0/SUCCESS)

Main PID: 15975 (code=exited, status=1/FAILURE)

Status: "SERVER_BOOTING"

Error: 2 (No such file or directory)

May 26 15:18:31 izuf65ov2pu9wezsqgtvbiz systemd[1]: Starting MySQL Server...

May 26 15:18:33 izuf65ov2pu9wezsqgtvbiz systemd[1]: mysqld.service: main process exited, code=exited, status=1/FAILURE

May 26 15:18:33 izuf65ov2pu9wezsqgtvbiz systemd[1]: Failed to start MySQL Server.

May 26 15:18:33 izuf65ov2pu9wezsqgtvbiz systemd[1]: Unit mysqld.service entered failed state.

May 26 15:18:33 izuf65ov2pu9wezsqgtvbiz systemd[1]: mysqld.service failed.

在线等,生产数据!!救济啊~

### 回答1: 这个错误通常是由于MySQL无法找到有效的数据目录导致的。可能的原因是在安装MySQL时指定了不正确的数据目录或者数据目录不可用。 可以尝试以下解决方法: 1. 确认MySQL的数据目录是否存在。可以在MySQL的配置文件(my.cnf或my.ini)中查找定义的数据目录路径。 2. 检查MySQL的数据目录权限是否正确。确保MySQL用户(通常是mysql)有访问该目录的权限。 3. 如果MySQL的数据目录不存在,可以尝试手动创建数据目录并确保MySQL用户有访问权限。 4. 如果MySQL的数据目录存在但不可用,可以尝试在配置文件中指定另一个数据目录或重新安装MySQL。 希望以上解决方法能够帮到你。 ### 回答2: MySQL登录报错"010119"是由于MySQL找不到有效的数据目录而引起的。而MySQL安装报错"Failed to find valid data directory"是同样的原因。 出现这个错误常见的原因有以下几种: 1. 数据目录不存在:MySQL需要一个数据目录来存储数据库文件和其他数据。如果安装过程中没有正确指定数据目录,或者数据目录已经被移动或删除,就会出现这个错误。解决方法是创建一个新的数据目录,并确保在MySQL配置文件中正确指定数据目录的路径。 2. 数据目录权限问题:如果数据目录的权限设置不正确,MySQL无法访问或写入数据目录,从而导致该错误。解决方法是使用适当的权限设置来确保MySQL可以访问和写入数据目录。 3. 数据目录损坏:如果数据目录中的文件损坏或丢失,MySQL无法启动。这可能是由于硬件故障、不当的系统关闭或其他原因引起的。解决方法是恢复数据目录中的文件,或者如果没有重要的数据,可以尝试删除数据目录并重新安装MySQL。 4. 数据目录路径错误:在MySQL的配置文件中,数据目录的路径必须与实际存在的路径完全匹配。如果路径不正确,MySQL无法找到数据目录,从而导致该错误。解决方法是确保在MySQL的配置文件中正确指定数据目录的路径。 综上所述,MySQL登录报错"010119"和安装报错"Failed to find valid data directory"都是因为MySQL无法找到有效的数据目录导致的。解决方法包括创建正确的数据目录、设置正确的权限、修复损坏的数据目录文件或确保正确的数据目录路径。 ### 回答3: MySQL登录010119报错是因为在安装MySQL的过程中出现了错误。具体报错信息 "Failed to find valid data directory" 表示无法找到有效的数据目录。 这个问题可能是由以下原因引起的: 1. 安装过程中选择了错误的数据目录。在安装MySQL时,需要指定一个合适的数据目录,用于存储数据库文件。如果选择的目录无效或不存在,就会导致这个错误。 解决方法:重新安装MySQL,并在安装过程中正确选择一个有效的数据目录。 2. 数据目录的权限设置不正确。MySQL需要对数据目录具有读写权限,否则会报错解决方法:使用管理员权限打开终端窗口,并使用 chown 命令修改数据目录的所有者为当前用户。例如,可以执行以下命令来修复权限问题: ``` sudo chown -R <当前用户名>:<当前用户组> /path/to/data_directory ``` 请将 `<当前用户名>` 替换为你的用户名,`<当前用户组>` 替换为你的用户组,`/path/to/data_directory` 替换为数据目录的路径。 3. 数据目录已被损坏或删除。如果数据目录的文件被删除或损坏,MySQL无法找到有效的数据目录。 解决方法:如果你有最新的数据库备份,可以使用它来恢复数据目录。否则,你需要重新创建一个新的数据目录,并重新导入数据。 综上所述,MySQL登录010119报错 "Failed to find valid data directory" 是由于安装过程中选择了无效的数据目录、数据目录的权限设置错误或数据目录被损坏或删除所致。通过重新安装、修复权限或恢复数据目录,可以解决这个问题。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值