mysql 突然无法启动原因排查

最新推荐文章于 2021-10-21 07:50:00 发布
最新推荐文章于 2021-10-21 07:50:00 发布
阅读量2.8k 收藏
点赞数
分类专栏： java 文章标签： mysql sql 数据库
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/m0_37986274/article/details/114526565
版权

问题描述：

项目上线一直运行的非常的好，就在这几天mysql突然出现连接不上，去手动重启msyql也启动不了，找到mysql.log 日志文件，发现了一堆报错信息，报错信息如下：

2021-03-07T13:07:42.747281Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2021-03-07T13:07:42.747304Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-03-07T13:07:42.747309Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-03-07T13:07:42.747313Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: './test@002dorange@002dtoken/chapter.ibd' OS error: 71
2021-03-07T13:07:42.747316Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2021-03-07T13:07:42.747319Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-03-07T13:07:42.747323Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-03-07T13:07:42.747328Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `test@002dorange@002dtoken/chapter`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2021-03-07T13:07:42.747333Z 0 [Warning] InnoDB: Ignoring tablespace `test@002dorange@002dtoken/chapter` because it could not be opened.
2021-03-07T13:07:42.747351Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2021-03-07T13:07:42.747355Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-03-07T13:07:42.747359Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-03-07T13:07:42.747362Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: './test@002dorange@002dtoken/edition.ibd' OS error: 71
2021-03-07T13:07:42.747365Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2021-03-07T13:07:42.747368Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-03-07T13:07:42.747371Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-03-07T13:07:42.747374Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `test@002dorange@002dtoken/edition`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2021-03-07T13:07:42.747378Z 0 [Warning] InnoDB: Ignoring tablespace `test@002dorange@002dtoken/edition` because it could not be opened.
2021-03-07T13:07:42.747388Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2021-03-07T13:07:42.747397Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-03-07T13:07:42.747400Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-03-07T13:07:42.747415Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: './test@002dorange@002dtoken/grade.ibd' OS error: 71
2021-03-07T13:07:42.747419Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2021-03-07T13:07:42.747422Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-03-07T13:07:42.747425Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-03-07T13:07:42.747433Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `test@002dorange@002dtoken/grade`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2021-03-07T13:07:42.747437Z 0 [Warning] InnoDB: Ignoring tablespace `test@002dorange@002dtoken/grade` because it could not be opened.
2021-03-07T13:07:42.747447Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2021-03-07T13:07:42.747450Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-03-07T13:07:42.747453Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-03-07T13:07:42.747456Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: './test@002dorange@002dtoken/knowledge_basic.ibd' OS error: 71
2021-03-07T13:07:42.747459Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2021-03-07T13:07:42.747467Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-03-07T13:07:42.747470Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-03-07T13:07:42.747474Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `test@002dorange@002dtoken/knowledge_basic`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2021-03-07T13:07:42.747478Z 0 [Warning] InnoDB: Ignoring tablespace `test@002dorange@002dtoken/knowledge_basic` because it could not be opened.
2021-03-07T13:07:42.747487Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2021-03-07T13:07:42.747497Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-03-07T13:07:42.747501Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-03-07T13:07:42.747506Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: './test@002dorange@002dtoken/knowledge_level.ibd' OS error: 71
2021-03-07T13:07:42.747510Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2021-03-07T13:07:42.747514Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-03-07T13:07:42.747519Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-03-07T13:07:42.747523Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `test@002dorange@002dtoken/knowledge_level`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2021-03-07T13:07:42.747529Z 0 [Warning] InnoDB: Ignoring tablespace `test@002dorange@002dtoken/knowledge_level` because it could not be opened.
2021-03-07T13:07:42.747551Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2021-03-07T13:07:42.747562Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-03-07T13:07:42.747566Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-03-07T13:07:42.747570Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: './test@002dorange@002dtoken/pharse.ibd' OS error: 71
2021-03-07T13:07:42.747574Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2021-03-07T13:07:42.747587Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-03-07T13:07:42.747591Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-03-07T13:07:42.747595Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `test@002dorange@002dtoken/pharse`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2021-03-07T13:07:42.747604Z 0 [Warning] InnoDB: Ignoring tablespace `test@002dorange@002dtoken/pharse` because it could not be opened.
2021-03-07T13:07:42.747617Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2021-03-07T13:07:42.747645Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-03-07T13:07:42.747648Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-03-07T13:07:42.747652Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: './test@002dorange@002dtoken/pharsegrade.ibd' OS error: 71
2021-03-07T13:07:42.747659Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2021-03-07T13:07:42.747662Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-03-07T13:07:42.747665Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-03-07T13:07:42.747668Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `test@002dorange@002dtoken/pharsegrade`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2021-03-07T13:07:42.747672Z 0 [Warning] InnoDB: Ignoring tablespace `test@002dorange@002dtoken/pharsegrade` because it could not be opened.
2021-03-07T13:07:42.747682Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2021-03-07T13:07:42.747729Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-03-07T13:07:42.747732Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-03-07T13:07:42.747735Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: './test@002dorange@002dtoken/question_knowledge_basic_id.ibd' OS error: 71
2021-03-07T13:07:42.747738Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2021-03-07T13:07:42.747741Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-03-07T13:07:42.747744Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-03-07T13:07:42.747748Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `test@002dorange@002dtoken/question_knowledge_basic_id`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2021-03-07T13:07:42.747757Z 0 [Warning] InnoDB: Ignoring tablespace `test@002dorange@002dtoken/question_knowledge_basic_id` because it could not be opened.
2021-03-07T13:07:42.747767Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2021-03-07T13:07:42.747770Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-03-07T13:07:42.747773Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-03-07T13:07:42.747776Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: './test@002dorange@002dtoken/questions.ibd' OS error: 71
2021-03-07T13:07:42.747779Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2021-03-07T13:07:42.747782Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-03-07T13:07:42.747791Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-03-07T13:07:42.747796Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `test@002dorange@002dtoken/questions`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2021-03-07T13:07:42.747807Z 0 [Warning] InnoDB: Ignoring tablespace `test@002dorange@002dtoken/questions` because it could not be opened.
2021-03-07T13:07:42.747823Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2021-03-07T13:07:42.747886Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-03-07T13:07:42.747891Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-03-07T13:07:42.747896Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: './test@002dorange@002dtoken/subject.ibd' OS error: 71
2021-03-07T13:07:42.747900Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2021-03-07T13:07:42.747910Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-03-07T13:07:42.747915Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2021-03-07T13:07:42.747920Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `test@002dorange@002dtoken/subject`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2021-03-07T13:07:42.747925Z 0 [Warning] InnoDB: Ignoring tablespace `test@002dorange@002dtoken/subject` because it could not be opened.
2021-03-07T13:07:42.748999Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2021-03-07T13:07:42.749035Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2021-03-07T13:07:42.846343Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2021-03-07T13:07:42.847017Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2021-03-07T13:07:42.847030Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2021-03-07T13:07:42.847798Z 0 [Note] InnoDB: 5.7.20 started; log sequence number 62495148947
2021-03-07T13:07:42.847957Z 0 [Note] InnoDB: Loading buffer pool(s) from /usr/local/mysql/data/ib_buffer_pool
2021-03-07T13:07:42.848148Z 0 [Note] Plugin 'FEDERATED' is disabled.
2021-03-07T13:07:42.850021Z 0 [Note] InnoDB: Buffer pool(s) load completed at 210307 21:07:42
2021-03-07T13:07:42.850991Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
2021-03-07T13:07:42.851152Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
2021-03-07T13:07:42.851185Z 0 [Note] IPv6 is available.
2021-03-07T13:07:42.851215Z 0 [Note]   - '::' resolves to '::';
2021-03-07T13:07:42.851234Z 0 [Note] Server socket created on IP: '::'.
2021-03-07T13:07:42.859078Z 0 [Note] Event Scheduler: Loaded 0 events
2021-03-07T13:07:42.859270Z 0 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.7.20'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Server (GPL)
2021-03-07T13:07:42.859286Z 0 [Note] Executing 'SELECT * FROM INFORMATION_SCHEMA.TABLES;' to get a list of tables using the deprecated partition engine. You may use the startup option '--disable-partition-engine-check' to skip this check. 
2021-03-07T13:07:42.859289Z 0 [Note] Beginning of list of non-natively partitioned tables
2021-03-07T13:07:42.874246Z 0 [Note] End of list of non-natively partitioned tables
2021-03-07T13:07:43.019536Z 3 [Warning] Host name 'ecs-121-37-221-237.compute.hwclouds-dns.com' could not be resolved: Name or service not known
2021-03-07T13:07:44.212367Z 8 [Warning] Host name 'ecs-139-159-243-117.compute.hwclouds-dns.com' could not be resolved: Name or service not known
2021-03-07T13:09:00.045669Z 18 [Warning] Host name 'ecs-121-37-201-229.compute.hwclouds-dns.com' could not be resolved: Name or service not known

原因分析：

注意看到如下报错信息：

由此分析应该是由于磁盘满了导致mysql无法继续重新启动成功。

解决方案：

找到根目录：du -h -x --max-depth=1 找到相关的磁盘，删除一些日志，我这边的问题是发现mysql.log 等各种日志的大小已经非常大，然后再调节mysql日志大小自动删除。
 

世外小虫
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 1
    评论
专栏目录
mysql服务无法启动报错误1067解决方法(mysql启动错误1067 )
09-10
mysql服务无法启动报错误1067解决方法，大家参考使用吧
mysql crash recovery,MySQL崩溃-如何修复损坏的innodb：innodb_force_recovery
weixin_39916360的博客
03-17 417
一、问题描述今天在线运行的一个mysql崩溃了，重启后发现还是无法正常启动。查看错误日志，如下：2018-08-20 10:19:16 7740 [Note] InnoDB: Page size:8192 Pages to analyze:82018-08-20 10:19:16 7740 [Note] InnoDB: Page size: 8192, Possible space_id coun...
windows无法启动MySQL服务报错1067的解决方法
09-09
主要为大家详细介绍了windows无法启动MySQL服务报错1067的3种解决方法，具有一定的参考价值，感兴趣的小伙伴们可以参考一下
MYSQL小问题解决集锦
天道酬勤
08-05 2462
1、 MySQL错误日志里出现： 140331 10:08:18 [ERROR] Error reading master configuration 140331 10:08:18 [ERROR] Failed to initialize the master info structure 140331 10:08:18 [Note] Event Scheduler: L
mysql insert 不需要日志_详解MySQL｜你不知道的新特性-8.0错误日志增强
weixin_39667626的博客
12-20 331
MySQL 8.0 重新定义了错误日志输出和过滤，改善了原来臃肿并且可读性很差的错误日志。比如增加了 JSON 输出，在原来的日志后面以序号以及 JSON 后缀的方式展示。比如我机器上的 MySQL 以 JSON 保存的错误日志 mysqld.log.00.json：[root@centos-ytt80 mysql80]# jq . mysqld.log.00.json{ "log_type":...
mamp mysql启动失败_MAMP PRO mysql无法启动
weixin_33241808的博客
01-19 382
mac上可能勾选了软件自动更新，然后MAMP PRO 升级了。升级了之后，mysql启动就出问题了，看报错日志：InnoDB: The error means the system cannot find the path specified.InnoDB: If you are installing InnoDB, remember that you must createInnoDB: dir...
mamp mysql启动失败_MAMP pro mysql 启动失败
weixin_39790738的博客
01-19 629
网上有很多关于Mac os 安装MAMP PRO后出现数据库无法启动的故障处理办法，然而每个都试了，完全不能解决问题，错误提示是：InnoDB: The error means the system cannot find the path specified.InnoDB: If you are installing InnoDB, remember that you must createIn...
小白学习MySQL - 聊聊数据备份的重要性
bisal的专栏
10-21 628
最近某套MySQL数据库服务器异常关机，导致MySQL不能正常拉起来，启动过程中，error日志中记录了如下的信息，可以看到，数据库因为异常关闭，此时会进行实例恢复的操作，[Note] I...
mysql移动数据无数据_mysql移动数据存放目录及问题
weixin_39754603的博客
01-19 189
我计划更换数据库的存放目录，下面是我的操作步骤1：首先创建新的数据存放路径并授予权限[root@pacteralinux mntsdc2formysql]# df -hFilesystem Size Used Avail Use% Mounted on/dev/sda1 29G 20G 7.5G 73% /tmpfs ...
Windows下MySQL 5.7无法启动的解决方法
09-09
从网上下了5.7 的MySQL，在bin目录下执行 start mysqld ，弹出个cmd窗口一闪就没了，也看不清是什么报错。mysqld --install安装了服务，也启动不了，下面通过本文给大家分享下解决办法
MySQL无法启动的解决办法
12-16
MySQL无法启动的解决办法 MySQL无法启动 在停止mysql之后，执行了一些操作（如修改主机名），重新启动 mysql，发现起不来。  [root@www ~]$ service mysql start Starting MySQL..^[[A............................
Mysql修改datadir导致无法启动问题解决方法
09-10
主要介绍了Mysql修改datadir导致无法启动问题解决方法,本文原因是SELINUX导致,用关闭SELINUX的方法解决了这个问题,需要的朋友可以参考下
记一次Mysql数据库Innodb故障--误删除idb文件
han156的博客
06-16 1万+
       某天中午，午休快要结束的时候，勤奋、努力、敬业的小编巡检服务器，发现有一台服务器的/home分区空间不足。因为历史原因，这是一个旧的平台，新平台已经建成，也已经投入生产。可是旧平台上依然还有很多的业务。因
mysql innodb启动失败_MYSQL教程MySQL数据库innodb启动失败无法重启的解决方法
weixin_32237761的博客
01-27 1287
《MYSQL教程MySQL数据库innodb启动失败无法重启的解决方法》要点：本文介绍了MYSQL教程MySQL数据库innodb启动失败无法重启的解决方法，希望对您有用。如果有疑问，可以联系我们。MYSQL应用问题介绍MYSQL应用电脑在使用过程中死机,重启后发现mysql没有启动成功,查看错误日志发现是innodb出现问题导致mysql启动失败.MYSQL应用错误日志MYSQL应用$ mysq...
mysql负载高排查_mysql负载突然增大，网站无法访问，排查处理方案
weixin_35742195的博客
01-28 401
一、开启慢查询日志记录1、vi /etc/my.cnf#slow_queryslow_query_log=onlong_query_time=1slow_query_log_file=/data/mysql_query/mysql-slow.log注意事项：配置需要写到[mysqld_safe]上面，日志文件需要有读写权限service mysqld restart重启数据库才会生效开启慢日志查...
Operating system error number 2 in a file operation
热门推荐
lwei_998的专栏
11-13 2万+
innobackupex 备份时遇到下述错误： innobackupex --defaults-file=/data/dbbak/my.cnf --stream=tar  ./ |gzip -> /data/dbbak/`date +%F`_full.tar.gz  2> backupout_`date +%F`.log xtrabackup version 2.2.5 based on My
mysql数据库启动失败自动解决_MySQL数据库innodb启动失败无法重启的解决方法
weixin_28750379的博客
01-18 1793
问题介绍电脑在使用过程中死机，重启后发现mysql没有启动成功，查看错误日志发现是innodb出现问题导致mysql启动失败。错误日志$ mysql.server startStarting MySQL. ERROR! The server quit without updating PID file (/usr/local/var/mysql/fdipzonedeMacBook-Air.loca...
mysqlworkbench突然无法连接的原因
最新发布
06-10
mysqlworkbench无法连接可能有多种原因，以下是一些常见的排查方法： 1. 确认MySQL服务器是否在运行，并且端口是否正确配置。 2. 检查MySQL服务器是否允许远程连接。可以在MySQL服务器上执行以下命令：`SELECT user,host FROM mysql.user;`，如果host列为localhost，则无法远程连接。 3. 确认MySQL服务器的防火墙是否正确配置，允许MySQL端口通过。 4. 确认MySQL服务器的配置文件是否正确配置，比如bind-address是否绑定了正确的IP地址。 5. 确认MySQL服务器是否有足够的权限，比如对应的用户是否有足够的权限连接到MySQL服务器。 如果以上方法都无法解决问题，可以尝试重新安装MySQL服务器和MySQL Workbench。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值