Description:
I have install MySQL and configuration it. After first installation it run normally. After a Day, i can't startet it, in the Configurition i see sort_buffer_size=11K and read_buffer_size=8K. If i reinstall it, it will be sort_buffer_size=256K and read_buffer_size=64K.
And in the Errorfile:
===============================================================
InnoDB: The first specified data file .\ibdata1 did not exist:
InnoDB: a new database to be created!
100310 12:31:31 InnoDB: Setting file .\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
100310 12:31:32 InnoDB: Log file .\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile0 size to 10 MB
InnoDB: Database physically writes the file full: wait...
100310 12:31:32 InnoDB: Log file .\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
100310 12:31:32 InnoDB: Started; log sequence number 0 0
100310 12:31:32 [Note] Event Scheduler: Loaded 0 events
100310 12:31:32 [Note] C:\Programme\MySQL\MySQL Server 5.1\bin\mysqld: ready for connections.
Version: '5.1.30-community' socket: '' port: 53306 MySQL Community Server (GPL)
100311 9:36:48 - 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=8200
max_used_connections=0
max_threads=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 12824 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x0
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...
006B8853 mysqld.exe!srv_parse_data_file_paths_and_sizes()[srv0start.c:211]
006A7E18 mysqld.exe!innobase_init()[ha_innodb.cc:1536]
00442748 mysqld.exe!ha_initialize_handlerton()[handler.cc:434]
00561253 mysqld.exe!plugin_initialize()[sql_plugin.cc:1002]
00565AE5 mysqld.exe!plugin_init()[sql_plugin.cc:1209]
004CE1B4 mysqld.exe!init_server_components()[mysqld.cc:3831]
004CE8C6 mysqld.exe!win_main()[mysqld.cc:4267]
004CECDB mysqld.exe!mysql_service()[mysqld.cc:4439]
00724593 mysqld.exe!_callthreadstart()[thread.c:293]
0072462C mysqld.exe!_threadstart()[thread.c:275]
7C80B729 kernel32.dll!GetModuleFileNameA()
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.
100311 10:44:32 - 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.
....
How to repeat:
i don't know
