============== my.ini配置 START ==============
Example MySQL config file for medium systems.
#
This is for a system with little memory (32M - 64M) where MySQL plays
an important part, or systems up to 128M where MySQL is used together with
other programs (such as a web server)
#
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 C:\mysql\data) 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 = 16M
max_allowed_packet = 10M
table_cache = 128
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 64M
max_connections = 1000
default-character-set = utf8
thread_cache_size = 8
query_cache_size = 0
query_cache_type = 0
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
Disable Federated by default
skip-federated
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=, MASTER_PORT=,
MASTER_USER=, MASTER_PASSWORD= ;
#
where you replace , , by quoted strings and
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 =
#
The username the slave will use for authentication when connecting
to the master - required
#master-user =
#
The password the slave will authenticate with when connecting to
the master - required
#master-password =
#
The port the master is listening on.
optional - defaults to 3306
#master-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 = C:\mysql\data/
#innodb_data_file_path = ibdata1:10M:autoextend
#innodb_log_group_home_dir = C:\mysql\data/
You can set .._buffer_pool_size up to 50 - 80 %
of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 16M
#innodb_additional_mem_pool_size = 2M
Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 5M
#innodb_log_buffer_size = 8M
#innodb_flush_log_at_trx_commit = 1
#innodb_lock_wait_timeout = 50
[mysqldump]
quick
max_allowed_packet = 10M
[mysql]
no-auto-rehash
Remove the next comment character if you are not familiar with SQL
#safe-updates
[isamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M
[myisamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M
[mysqlhotcopy]
interactive-timeout
============== my.ini配置 END ==============
============== mysql 错误日志 START ==============
180120 18:16:36 InnoDB: Starting shutdown...
180120 18:16:38 InnoDB: Shutdown completed; log sequence number 2 1119799076
180120 18:16:38 [Warning] Forcing shutdown of 1 plugins
180120 18:16:38 [Note] D:\PHPnow-1.5.3\MySQL-5.1.33\bin\mysqld.exe: Shutdown complete
180120 18:16:39 InnoDB: Started; log sequence number 2 1119799076
180120 18:16:39 [Note] Event Scheduler: Loaded 0 events
180120 18:16:39 [Note] D:\PHPnow-1.5.3\MySQL-5.1.33\bin\mysqld.exe: ready for connections.
Version: '5.1.33-community-log' socket: '' port: 3306 MySQL Community Server (GPL)
180120 21:12:28 - mysqld got exception 0xc0000005 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=8388608
read_buffer_size=262144
max_used_connections=43
max_threads=1000
threads_connected=20
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 782496 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x37f7930
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
00725584 mysqld.exe!???
004E6C5A mysqld.exe!???
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 05CE2E30=select * from massage_common_user where yn=1 and id=29156
thd->thread_id=8430
thd->killed=NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
InnoDB: Log scan progressed past the checkpoint lsn 2 1125547569
180120 21:14:56 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 2 1125550276
180120 21:14:56 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 4956330, file name .\mysql-bin.000053
180120 21:14:57 InnoDB: Started; log sequence number 2 1125550276
180120 21:14:57 [Note] Recovering after a crash using mysql-bin
180120 21:14:57 [Note] Starting crash recovery...
180120 21:14:57 [Note] Crash recovery finished.
180120 21:14:57 [Note] Event Scheduler: Loaded 0 events
180120 21:14:57 [Note] D:\PHPnow-1.5.3\MySQL-5.1.33\bin\mysqld.exe: ready for connections.
Version: '5.1.33-community-log' socket: '' port: 3306 MySQL Community Server (GPL)
============== mysql 错误日志 END ==============
服务器环境
window server 2012
16G
