my sql isnt working

Problems with the Windows version of XAMPP, questions, comments, and anything related.

my sql isnt working

Postby kingsley724 » 24. January 2014 19:22

2014-01-24 12:57:46 8552 [Note] Plugin 'FEDERATED' is disabled.
2014-01-24 12:57:47 1b34 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2014-01-24 12:57:47 8552 [Note] InnoDB: The InnoDB memory heap is disabled
2014-01-24 12:57:47 8552 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-01-24 12:57:47 8552 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-01-24 12:57:47 8552 [Note] InnoDB: Not using CPU crc32 instructions
2014-01-24 12:57:47 8552 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-01-24 12:57:47 8552 [Note] InnoDB: Completed initialization of buffer pool
2014-01-24 12:57:47 8552 [Note] InnoDB: Highest supported file format is Barracuda.
2014-01-24 12:57:49 8552 [Warning] InnoDB: Resizing redo log from 2*3072 to 2*320 pages, LSN=1625987
2014-01-24 12:57:49 8552 [Warning] InnoDB: Starting to delete and rewrite log files.
2014-01-24 12:57:49 8552 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2014-01-24 12:57:50 8552 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2014-01-24 12:57:50 8552 [Note] InnoDB: Renaming log file C:\xampp\mysql\data\ib_logfile101 to C:\xampp\mysql\data\ib_logfile0
2014-01-24 12:57:50 1b34 InnoDB: Operating system error number 183 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: ... codes.html
2014-01-24 12:57:50 8552 [ERROR] InnoDB: File C:\xampp\mysql\data\ib_logfile101: 'rename' returned OS error 283.
2014-01-24 12:57:50 1b34 InnoDB: Assertion failure in thread 6964 in file line 705
InnoDB: Failing assertion: success
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
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: ... overy.html
InnoDB: about forcing recovery.
17:57:50 UTC - mysqld got exception 0x80000003 ;
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.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133774 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 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...
1326da0 mysqld.exe!my_thread_name()
155fc7d mysqld.exe!my_mb_ctype_mb()
139ce92 mysqld.exe!xor_string()
1359f5a mysqld.exe!xor_string()
10d9df0 mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
1113d2e mysqld.exe!?plugin_lock_by_name@@YAPAUst_plugin_int@@PAVTHD@@PBUst_mysql_lex_string@@H@Z()
1118384 mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
10d151d mysqld.exe!?init_common_variables@@YAHXZ()
10d2238 mysqld.exe!?win_main@@YAHHPAPAD@Z()
10d27a7 mysqld.exe!?mysql_service@@YAHPAX@Z()
155a7da mysqld.exe!my_mb_ctype_mb()
7515336a kernel32.dll!BaseThreadInitThunk()
76fa9f72 ntdll.dll!RtlInitializeExceptionChain()
76fa9f45 ntdll.dll!RtlInitializeExceptionChain()
The manual page at contains
information that should help you find out what is causing the crash.
Posts: 1
Joined: 24. January 2014 19:19
XAMPP Version: 1.8.3
Operating System: windows 7

Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 48 guests