Description:
mysqld.exe started taking 99% CPU, the same was working fine till last night, the system was running all night.
uninstalled and reinstalled the mysql doesnt help. While configuring the server the service doesnt start and a windows message box appears and says:
An unhandled win32 exception occurred in mysqld.exe. [3952] sometimes [1900].
No event viewer log is available for the same.
I run the same in standalone mode and here is the dump:
mysqld --defaults-file="my.ini path" --standalone --console
It printed 0 multiple times and then below dump:
;InnoDB: End of page dump
101228 11:43:13 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum
1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a freshly allocated page
101228 11:43:13InnoDB: Error: trying to access a stray pointer 82413FF8
InnoDB: buf pool start is at 02404000, end at 02D04000
InnoDB: Probable reason is database corruption or memory
InnoDB: corruption. If this happens in an InnoDB database recovery, see
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: how to force recovery.
101228 11:43:13 InnoDB: Assertion failure in thread 3956 in file G:\mysql-5.1.4
5-winbuild\mysql-community-nt-5.1.45-build\storage\innobase\include\buf0buf.ic l
ine 264
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
101228 11:43:13 - 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=65536
max_used_connections=0
max_threads=160
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 53842 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...
005EE050 mysqld.exe!buf_frame_align()[buf0buf.ic:264]
005D387C mysqld.exe!page_dir_slot_get_rec()[page0page.ic:503]
0061E896 mysqld.exe!page_cur_search_with_match()[page0cur.c:351]
005D9B4C mysqld.exe!btr_cur_search_to_nth_level()[btr0cur.c:521]
00603640 mysqld.exe!btr_pcur_open()[btr0pcur.ic:494]
00604316 mysqld.exe!btr_pcur_open_on_user_rec()[btr0pcur.c:550]
005F9D9A mysqld.exe!dict_load_indexes()[dict0load.c:610]
005FA107 mysqld.exe!dict_load_sys_table()[dict0load.c:1015]
0060F538 mysqld.exe!dict_boot()[dict0boot.c:389]
005C214A mysqld.exe!innobase_start_or_create_for_mysql()[srv0start.c:1521]
005B0138 mysqld.exe!innobase_init()[ha_innodb.cc:1973]
0047E818 mysqld.exe!ha_initialize_handlerton()[handler.cc:435]
00429673 mysqld.exe!plugin_initialize()[sql_plugin.cc:1014]
0042D244 mysqld.exe!plugin_init()[sql_plugin.cc:1238]
00418121 mysqld.exe!init_server_components()[mysqld.cc:3950]
004187E1 mysqld.exe!win_main()[mysqld.cc:4419]
00418B2D mysqld.exe!mysql_service()[mysqld.cc:4597]
00418DC0 mysqld.exe!main()[mysqld.cc:4783]
004011F6 mysqld.exe!__tmainCRTStartup()[crt0.c:327]
003B36CB
2D00646C
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.
How to repeat:
Dont know.
Suggested fix:
not found yet.
Description: mysqld.exe started taking 99% CPU, the same was working fine till last night, the system was running all night. uninstalled and reinstalled the mysql doesnt help. While configuring the server the service doesnt start and a windows message box appears and says: An unhandled win32 exception occurred in mysqld.exe. [3952] sometimes [1900]. No event viewer log is available for the same. I run the same in standalone mode and here is the dump: mysqld --defaults-file="my.ini path" --standalone --console It printed 0 multiple times and then below dump: ;InnoDB: End of page dump 101228 11:43:13 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432 InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0 InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0 InnoDB: Page number (if stored to page already) 0, InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0 InnoDB: Page may be a freshly allocated page 101228 11:43:13InnoDB: Error: trying to access a stray pointer 82413FF8 InnoDB: buf pool start is at 02404000, end at 02D04000 InnoDB: Probable reason is database corruption or memory InnoDB: corruption. If this happens in an InnoDB database recovery, see InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: how to force recovery. 101228 11:43:13 InnoDB: Assertion failure in thread 3956 in file G:\mysql-5.1.4 5-winbuild\mysql-community-nt-5.1.45-build\storage\innobase\include\buf0buf.ic l ine 264 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: about forcing recovery. 101228 11:43:13 - 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=65536 max_used_connections=0 max_threads=160 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 53842 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... 005EE050 mysqld.exe!buf_frame_align()[buf0buf.ic:264] 005D387C mysqld.exe!page_dir_slot_get_rec()[page0page.ic:503] 0061E896 mysqld.exe!page_cur_search_with_match()[page0cur.c:351] 005D9B4C mysqld.exe!btr_cur_search_to_nth_level()[btr0cur.c:521] 00603640 mysqld.exe!btr_pcur_open()[btr0pcur.ic:494] 00604316 mysqld.exe!btr_pcur_open_on_user_rec()[btr0pcur.c:550] 005F9D9A mysqld.exe!dict_load_indexes()[dict0load.c:610] 005FA107 mysqld.exe!dict_load_sys_table()[dict0load.c:1015] 0060F538 mysqld.exe!dict_boot()[dict0boot.c:389] 005C214A mysqld.exe!innobase_start_or_create_for_mysql()[srv0start.c:1521] 005B0138 mysqld.exe!innobase_init()[ha_innodb.cc:1973] 0047E818 mysqld.exe!ha_initialize_handlerton()[handler.cc:435] 00429673 mysqld.exe!plugin_initialize()[sql_plugin.cc:1014] 0042D244 mysqld.exe!plugin_init()[sql_plugin.cc:1238] 00418121 mysqld.exe!init_server_components()[mysqld.cc:3950] 004187E1 mysqld.exe!win_main()[mysqld.cc:4419] 00418B2D mysqld.exe!mysql_service()[mysqld.cc:4597] 00418DC0 mysqld.exe!main()[mysqld.cc:4783] 004011F6 mysqld.exe!__tmainCRTStartup()[crt0.c:327] 003B36CB 2D00646C 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. How to repeat: Dont know. Suggested fix: not found yet.