MYSQL的10061错误

问题描述

首先,系统服务中的MySQL服务正常运行,在eclipse中通过加入mysql-connector-java-5.1.10-bin.jar连接mysql,运行程序也正常,增删改查的功能都正常,图略.通过dos命令也能连接到mysql但是通过navicat无法连接,错误信息:使用其他连接mysql的工具也是10061错误信息.HELP:我程序正常运行,应该mysql没有问题,我就是想用navicat一类的工具,如果只是一些神马重装的建议,就不劳烦了,3Q! 问题补充:全部内容,没有bind-address # MySQL Server Instance Configuration File# ----------------------------------------------------------------------# Generated by the MySQL Server Instance Configuration Wizard
解决方案二:
Installation Instructions# ----------------------------------------------------------------------## On Linux you can copy this file to /etc/my.cnf to set global options,# mysql-data-dir/my.cnf to set server-specific options# (@localstatedir@ for this installation) or to# ~/.my.cnf to set user-specific options.## On Windows you should keep this file in the installation directory # of your server (e.g. C:Program FilesMySQLMySQL Server X.Y). To# make sure the server reads the config file use the startup option # "--defaults-file". ## To run run the server from the command line, execute this in a # command line shell, e.g.# mysqld --defaults-file="C:Program FilesMySQLMySQL Server X.Ymy.ini"## To install the server as a Windows service manually, execute this in a # command line shell, e.g.# mysqld --install MySQLXY --defaults-file="C:Program FilesMySQLMySQL Server X.Ymy.ini"## And then execute this in a command line shell to start the server, e.g.# net start MySQLXY
解决方案三:
Guildlines for editing this file# ----------------------------------------------------------------------## In this file, you can use all long options that the program supports.# If you want to know the options a program supports, start the program# with the "--help" option.## More detailed information about the individual options can also be# found in the manual.
解决方案四:
CLIENT SECTION# ----------------------------------------------------------------------## The following options will be read by MySQL client applications.# Note that only client applications shipped by MySQL are guaranteed# to read this section. If you want your own MySQL client program to# honor these values, you need to specify it as an option during the# MySQL client library initialization.#[client]port=3306[mysql]default-character-set=utf8# SERVER SECTION# ----------------------------------------------------------------------## The following options will be read by the MySQL Server. Make sure that# you have installed the server correctly (see above) so it reads this # file.#[mysqld]# The TCP/IP Port the MySQL Server will listen onport=3306#Path to installation directory. All paths are usually resolved relative to this.basedir="C:/Program Files/MySQL/MySQL Server 5.6/"#Path to the database rootdatadir="C:/Documents and Settings/All Users/Application Data/MySQL/MySQL Server 5.6/Data/"# The default character set that will be used when a new schema or table is# created and no character set is definedcharacter-set-server=utf8# The default storage engine that will be used when create new tables whendefault-storage-engine=INNODB# Set the SQL mode to strictsql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"# The maximum amount of concurrent sessions the MySQL server will# allow. One of these connections will be reserved for a user with# SUPER privileges to allow the administrator to login even if the# connection limit has been reached.max_connections=329# Query cache is used to cache SELECT results and later return them# without actual executing the same query once again. Having the query# cache enabled may result in significant speed improvements, if your# have a lot of identical queries and rarely changing tables. See the# "Qcache_lowmem_prunes" status variable to check if the current value# is high enough for your load.# Note: In case your tables change very often or if your queries are# textually different every time, the query cache may result in a# slowdown instead of a performance improvement.query_cache_size=9M# The number of open tables for all threads. Increasing this value# increases the number of file descriptors that mysqld requires.# Therefore you have to make sure to set the amount of open files# allowed to at least 4096 in the variable "open-files-limit" in# section [mysqld_safe]table_cache=700# Maximum size for internal (in-memory) temporary tables. If a table# grows larger than this value, it is automatically converted to disk# based table This limitation is for a single table. There can be many# of them.tmp_table_size=16M# How many threads we should keep in a cache for reuse. When a client# disconnects, the client's threads are put in the cache if there aren't# more than thread_cache_size threads from before. This greatly reduces# the amount of thread creations needed if you have a lot of new# connections. (Normally this doesn't give a notable performance# improvement if you have a good thread implementation.)thread_cache_size=16#*** MyISAM Specific options# The maximum size of the temporary file MySQL is allowed to use while# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.# If the file-size would be bigger than this, the index will be created# through the key cache (which is slower).myisam_max_sort_file_size=100G# If the temporary file used for fast index creation would be bigger# than using the key cache by the amount specified here, then prefer the# key cache method. This is mainly used to force long character keys in# large tables to use the slower key cache method to create the index.myisam_sort_buffer_size=8M# Size of the Key Buffer, used to cache index blocks for MyISAM tables.# Do not set it larger than 30% of your available memory, as some memory# is also required by the OS to cache rows. Even if you're not using# MyISAM tables, you should still set it to 8-64M as it will also be# used for internal temporary disk tables.key_buffer_size=12M# Size of the buffer used for doing full table scans of MyISAM tables.# Allocated per thread, if a full scan is needed.read_buffer_size=64Kread_rnd_buffer_size=256K# This buffer is allocated when MySQL needs to rebuild the index in# REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE# into an empty table. It is allocated per thread so be careful with# large settings.sort_buffer_size=208K#*** INNODB Specific options ***innodb_data_home_dir="D:/MySQL Datafiles/"# Use this option if you have a MySQL server with InnoDB support enabled# but you do not plan to use it. This will save memory and disk space# and speed up some things.#skip-innodb# Additional memory pool that is used by InnoDB to store metadata# information. If InnoDB requires more memory for this purpose it will# start to allocate it from the OS. As this is fast enough on most# recent operating systems, you normally do not need to change this# value. SHOW INNODB STATUS will display the current amount used.innodb_additional_mem_pool_size=2M# If set to 1, InnoDB will flush (fsync) the transaction logs to the# disk at each commit, which offers full ACID behavior. If you are# willing to compromise this safety, and you are running small# transactions, you may set this to 0 or 2 to reduce disk I/O to the# logs. Value 0 means that the log is only written to the log file and# the log file flushed to disk approximately once per second. Value 2# means the log is written to the log file at each commit, but the log# file is only flushed to disk approximately once per second.innodb_flush_log_at_trx_commit=1# The size of the buffer InnoDB uses for buffering log data. As soon as# it is full, InnoDB will have to flush it to disk. As it is flushed# once per second anyway, it does not make sense to have it very large# (even with long transactions).innodb_log_buffer_size=1M# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and# row data. The bigger you set this the less disk I/O is needed to# access data in tables. On a dedicated database server you may set this# parameter up to 80% of the machine physical memory size. Do not set it# too large, though, because competition of the physical memory may# cause paging in the operating system. Note that on 32bit systems you# might be limited to 2-3.5G of user level memory per process, so do not# set it too high.innodb_buffer_pool_size=21M# Size of each log file in a log group. You should set the combined size# of log files to about 25%-100% of your buffer pool size to avoid# unneeded buffer pool flush activity on log file overwrite. However,# note that a larger logfile size will increase the time needed for the# recovery process.innodb_log_file_size=23M# Number of threads allowed inside the InnoDB kernel. The optimal value# depends highly on the application, hardware as well as the OS# scheduler properties. A too high value may lead to thread thrashing.innodb_thread_concurrency=8

解决方案

在[mysqld]这一节中添加上这一行:bind-address = 0.0.0.0试试
解决方案五:
MySQL数据库默认是不允许这些工具远程连接的,你可以找到my.ini这个文件,将bind-address=127.0.0.1改为 bind-address=0.0.0.0 或将其注释掉

时间: 2024-09-21 03:38:08

MYSQL的10061错误的相关文章

mysql登陆总是错误,提示连接不上服务器

问题描述 mysql登陆总是错误,提示连接不上服务器 今天登陆mysql客户端的时候,总是提示这样的错误: "can't connect to MYSQL server on 'localhost' (10061)",尝试很多办法都不行,请问该怎么办?? 解决方案 看下你的mysql服务有没有启动起来. 如果有故障,参考:http://www.jb51.net/article/26505.htm 解决方案二: 贴一下连接语句 顺便确定连接的电脑的mysqld服务是开启的 解决方案三:

jsp 网站开发-jsp连接 mysql 更新语法错误,大家帮我看看,谢谢~

问题描述 jsp连接 mysql 更新语法错误,大家帮我看看,谢谢~ update test set check='1' where memName ='lmy' 解决方案 有可能表中列名不对应或者设置的类型不对应

连接MySQL出现2013错误解决

环境:Navicat for Mysql 8.2+ MySQL Sever 5.1 问题:使用Navicat for Mysql连接MySQL出现 如下错误:2013-Lost connection to MySQL server at 'reading initialcommunication packet',system error:0.如图: 解决:重启MySQL服务------ ->重新连接. 附:MySQL批处理下载:http://ishare.iask.sina.com.cn/f/2

mysql-登陆MySQL出现下图错误,怎么解决?

问题描述 登陆MySQL出现下图错误,怎么解决? 登陆MySQL时出现这种图错误,MySQL数据库和MySQL-Front都是今天才安装的,怎么解决? 解决方案 重装下系统,软件破坏了 解决方案二: 最下面的: **please tell me this problem *** ** report to me 请发送一个bug报告回复我 可以看出这是mysql工具的问题 建议重新卸载安装一个

创建 表-mysql创建表错误,下面的代码哪儿不对?

问题描述 mysql创建表错误,下面的代码哪儿不对? CREATE TABLE ACCOUNT( ID INT(4) CONSTRAINT ACCOUNT_ID_PK PRIMARY KEY, RECOMMENDER_ID INT(4) CONSTRAINT ACCOUNT_RECOMMENDER_ID_FK REFERENCES ACCOUNT(ID), LOGIN_NAME VARCHAR(30) NOT NULL CONSTRAINT ACCOUNT_LOGIN_NAME_UK UNIQU

php 操作 mysql 数据库 编码 错误

问题描述 php 操作 mysql 数据库 编码 错误 有两行相同的代码,来自不同的 php 文件,在对 MySql 数据库(UTF-8格式)操作时,一行代码正常,一行代码异常 代码1,异常 update ordersystem.product Set PName='333汽车' Where Bianhao='???XAHNBQ2LC42GJQP-25'; 在将这行代码保存到记事本时提示:需要保存为 Unicode 格式 代码来自文件 A.php,文件保存格式UTF-8,该文件是纯 php 文件

mysql触发器语法错误问题

问题描述 mysql触发器语法错误问题 CREATE TRIGGER tradecost AFTER UPDATE ON fentrust FOR EACH ROW BEGIN DECLARE old_account DECIMAL(16,6) DECLARE old_fid INT(10) DECLARE trade_account DECIMAL(16,6) SET old_fid = SELECT old_fid FROM fentrust WHERE old.fEntrustType =

创建 多个 MySQL docker 出现错误时

创建 多个 MySQL docker 出现错误时 风来了.fox -- 140505 16:05:59 InnoDB: Using Linux native AIO 140505 16:05:59 InnoDB: Warning: io_setup() failed with EAGAIN. Will make 5 attempts before giving up. InnoDB: Warning: io_setup() attempt 1 failed. InnoDB: Warning: i

sql点滴37—mysql中的错误Data too long for column '' at row 1

原文:sql点滴37-mysql中的错误Data too long for column '' at row 1   1.MYSQL服务 我的电脑--(右键)管理--服务与应用程序--服务--MYSQL--开启(停止.重启动)   2.命令行方式 Windows 1.点击"开始"->"运行"(快捷键Win+R). 2.启动:输入 net stop mysql 3.停止:输入 net start mysql 提示* Redhat Linux 也支持service