后台程序跑了一段时间,一直很正常。早上过来发现中间有两个小时没有取到数据,查看了一下日志发现执行下面这个句子的时候出现了MySQL server has gone away。的错误,时间为[2010-11-10 08:51:19]。
insert into test111 values('1.1.1.1', 21108, 154019, 1289350279, 0, 111948.000000, 122067.000000, 4, 96.403593, 0.077637, 5692.191406, 7993.843750, 15994.390625, 15994.390625)查看wait_timeout/interactive_timeout均为28800。我的程序每隔5分钟都会有数据插入到数据库,所有并没有修改timeout值,和使用mysql_ping(...)。继续看程序的日志,发现几分钟前还有数据插入,时间为[2010-11-10 08:46:20],应该不会是数据库响应超时导致的错误。
insert into test112 values(NULL, '1.1.1.3', 21108, 1289349980, 0, 480.474000, 2.270000, 9.760000, 6.230000, 65536, 63877, 100, 0.003790, 0.005620, 0.050460, 0.047760, 0.002860, 0.003790, 0.000000, 0.000000, 136.338050, 90.000000)查看mysql日志也没有发现异常情况。
所以我就很奇怪,还有什么情况会导致MySQL server has gone away的发生。
请大虾指点。
insert into test111 values('1.1.1.1', 21108, 154019, 1289350279, 0, 111948.000000, 122067.000000, 4, 96.403593, 0.077637, 5692.191406, 7993.843750, 15994.390625, 15994.390625)查看wait_timeout/interactive_timeout均为28800。我的程序每隔5分钟都会有数据插入到数据库,所有并没有修改timeout值,和使用mysql_ping(...)。继续看程序的日志,发现几分钟前还有数据插入,时间为[2010-11-10 08:46:20],应该不会是数据库响应超时导致的错误。
insert into test112 values(NULL, '1.1.1.3', 21108, 1289349980, 0, 480.474000, 2.270000, 9.760000, 6.230000, 65536, 63877, 100, 0.003790, 0.005620, 0.050460, 0.047760, 0.002860, 0.003790, 0.000000, 0.000000, 136.338050, 90.000000)查看mysql日志也没有发现异常情况。
所以我就很奇怪,还有什么情况会导致MySQL server has gone away的发生。
请大虾指点。
解决方案 »
- 在.net里,怎么让mySql通过ODbc的Driver链接数据库?
- PostgreSQL-PL/pgSQL教程--基本语句
- 第一次用java连接mysql 失败,郁闷了很长时间了
- mysql的并发问题
- mysql里有没有DateDiff()函数?
- 如何给属性添加自定义约束
- 关于SQL语句
- 本人初次使用MySQL,有点问题想请教。问题是我启动mysql.exe后,输入“uses testmysql;”后有一个错误提示,请问是什么问题??
- myisam_data_pointer_size的值
- 求一条条件插入语句
- 关于模糊匹配的问题
- 我在debian上apt-get安装mysql,找不到数据库文件在哪
Linux 2.6.9-42.ELsmp #1 SMP Wed Jul 12 23:32:02 EDT 2006 x86_64 x86_64 x86_64 GNU/LinuxMysql版本:
Server version 5.1.46-log刚才查看的mysql基本状态参数。
Threads: 11 Questions: 21627604 Slow queries: 200 Opens: 76260 Flush tables: 2 Open tables: 256 Queries per second avg: 84.669
我程序就运行在Mysql服务器上,应该不存在网络问题。
# Example MySQL config file for large systems.
#
# This is for a large system with memory = 512M where the system runs mainly
# MySQL.
#
# You can copy this file to
# /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is /usr/local/mysql/var) or
# ~/.my.cnf to set user-specific options.
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.# The following options will be passed to all MySQL clients
[client]
#password = your_password
port = 3306
socket = /tmp/mysql.sock# Here follows entries for some specific programs# The MySQL server
[mysqld]
port = 3306
socket = /tmp/mysql.sock
skip-locking
key_buffer_size = 256M
max_allowed_packet = 1M
table_open_cache = 256
sort_buffer_size = 1M
read_buffer_size = 1M
read_rnd_buffer_size = 4M
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size= 16M
# Try number of CPU's*2 for thread_concurrency
thread_concurrency = 8# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
#skip-networking# Replication Master Server (default)
# binary logging is required for replication
log-bin=mysql-bin# binary logging format - mixed recommended
binlog_format=mixed# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id = 1# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
# the syntax is:
#
# CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
# MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
# where you replace <host>, <user>, <password> by quoted strings and
# <port> by the master's port number (3306 by default).
#
# Example:
#
# CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
# MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
# start replication for the first time (even unsuccessfully, for example
# if you mistyped the password in master-password and the slave fails to
# connect), the slave will create a master.info file, and any later
# change in this file to the variables' values below will be ignored and
# overridden by the content of the master.info file, unless you shutdown
# the slave server, delete master.info and restart the slaver server.
# For that reason, you may want to leave the lines below untouched
# (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id = 2
#
# The replication master for this slave - required
#master-host = <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user = <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password = <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port = <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin# Point the following paths to different dedicated disks
#tmpdir = /tmp/
#log-update = /path-to-dedicated-directory/hostname# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /usr/local/mysql/var/
#innodb_data_file_path = ibdata1:10M:autoextend
#innodb_log_group_home_dir = /usr/local/mysql/var/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 256M
#innodb_additional_mem_pool_size = 20M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 64M
#innodb_log_buffer_size = 8M
#innodb_flush_log_at_trx_commit = 1
#innodb_lock_wait_timeout = 50[mysqldump]
quick
max_allowed_packet = 16M[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates[myisamchk]
key_buffer_size = 128M
sort_buffer_size = 128M
read_buffer = 2M
write_buffer = 2M[mysqlhotcopy]
interactive-timeout