Unable to keep MySQL running on new install

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

Unable to keep MySQL running on new install

Postby jaseinatl » 13. November 2018 07:48

I installed Xampp (for the 3rd time) and made sure that there were no conflicting ports before installing. I installed it to my P:/XAMPP folder and it claims to have installed without error.

I launch Apapche..no problems.
I launch MySQL and no problems at first, then it shuts down 20 seconds later and tells me to post this error log here:
2015-11-10 15:26:56 10fc 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.
2015-11-10 15:26:56 4348 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2015-11-10 15:26:56 4348 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-10 15:26:56 4348 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-10 15:26:56 4348 [Note] InnoDB: Memory barrier is not used
2015-11-10 15:26:56 4348 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-10 15:26:56 4348 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-10 15:26:56 4348 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-11-10 15:26:56 4348 [Note] InnoDB: Completed initialization of buffer pool
2015-11-10 15:26:56 4348 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-10 15:26:57 4348 [Note] InnoDB: 128 rollback segment(s) are active.
2015-11-10 15:26:57 4348 [Note] InnoDB: Waiting for purge to start
2015-11-10 15:26:57 4348 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1835027
2015-11-10 15:26:57 6140 [Note] InnoDB: Dumping buffer pool(s) not yet started
2015-11-10 15:26:57 4348 [Note] Plugin 'FEEDBACK' is disabled.
2015-11-10 15:26:57 4348 [Note] Server socket created on IP: '::'.
2015-11-10 15:26:57 4348 [Note] Event Scheduler: Loaded 0 events
2015-11-10 15:26:57 4348 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.8-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2015-11-10 15:27:11 5152 [Note] C:\xampp\mysql\bin\mysqld.exe: Normal shutdown

2015-11-10 15:27:11 5152 [Note] Event Scheduler: Purging the queue. 0 events
2015-11-10 15:27:11 5732 [Note] InnoDB: FTS optimize thread exiting.
2015-11-10 15:27:11 5152 [Note] InnoDB: Starting shutdown...
2015-11-10 15:27:13 5152 [Note] InnoDB: Shutdown completed; log sequence number 1835037
2015-11-10 15:27:13 5152 [Note] C:\xampp\mysql\bin\mysqld.exe: Shutdown complete

2018-11-13 01:30:14 93c 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.
2018-11-13 1:30:14 2364 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-11-13 1:30:14 2364 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-11-13 1:30:14 2364 [Note] InnoDB: The InnoDB memory heap is disabled
2018-11-13 1:30:14 2364 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-11-13 1:30:14 2364 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-11-13 1:30:14 2364 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-11-13 1:30:14 2364 [Note] InnoDB: Using generic crc32 instructions
2018-11-13 1:30:14 2364 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-11-13 1:30:14 2364 [Note] InnoDB: Completed initialization of buffer pool
2018-11-13 01:30:15 93c InnoDB: Operating system error number 6 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
InnoDB: Operation close to file d:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 2493
2018-11-13 1:30:15 2364 [ERROR] InnoDB: File (unknown): 'close' returned OS error 206. Cannot continue operation
181113 1:30:15 [ERROR] 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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.36-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787136 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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlValidSecurityDescriptor()
ntdll.dll!RtlValidSecurityDescriptor()
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.
2018-11-13 01:30:59 5078 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.
2018-11-13 1:30:59 20600 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-11-13 1:30:59 20600 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-11-13 1:30:59 20600 [Note] InnoDB: The InnoDB memory heap is disabled
2018-11-13 1:30:59 20600 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-11-13 1:30:59 20600 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-11-13 1:30:59 20600 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-11-13 1:30:59 20600 [Note] InnoDB: Using generic crc32 instructions
2018-11-13 1:30:59 20600 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-11-13 1:30:59 20600 [Note] InnoDB: Completed initialization of buffer pool
2018-11-13 01:30:59 5078 InnoDB: Operating system error number 6 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
InnoDB: Operation close to file d:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 2493
2018-11-13 1:30:59 20600 [ERROR] InnoDB: File (unknown): 'close' returned OS error 206. Cannot continue operation
181113 1:30:59 [ERROR] 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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.36-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787136 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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlValidSecurityDescriptor()
ntdll.dll!RtlValidSecurityDescriptor()
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.
2018-11-13 01:35:15 31f8 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.
2018-11-13 1:35:15 12792 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-11-13 1:35:15 12792 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-11-13 1:35:15 12792 [Note] InnoDB: The InnoDB memory heap is disabled
2018-11-13 1:35:15 12792 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-11-13 1:35:15 12792 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-11-13 1:35:15 12792 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-11-13 1:35:15 12792 [Note] InnoDB: Using generic crc32 instructions
2018-11-13 1:35:15 12792 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-11-13 1:35:15 12792 [Note] InnoDB: Completed initialization of buffer pool
2018-11-13 01:35:15 31f8 InnoDB: Operating system error number 6 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
InnoDB: Operation close to file d:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 2493
2018-11-13 1:35:15 12792 [ERROR] InnoDB: File (unknown): 'close' returned OS error 206. Cannot continue operation
181113 1:35:15 [ERROR] 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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.36-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787136 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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlValidSecurityDescriptor()
ntdll.dll!RtlValidSecurityDescriptor()
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.
2018-11-13 01:35:46 1f3c 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.
2018-11-13 1:35:46 7996 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-11-13 1:35:46 7996 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-11-13 1:35:46 7996 [Note] InnoDB: The InnoDB memory heap is disabled
2018-11-13 1:35:46 7996 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-11-13 1:35:46 7996 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-11-13 1:35:46 7996 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-11-13 1:35:46 7996 [Note] InnoDB: Using generic crc32 instructions
2018-11-13 1:35:46 7996 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-11-13 1:35:46 7996 [Note] InnoDB: Completed initialization of buffer pool
2018-11-13 01:35:46 1f3c InnoDB: Operating system error number 6 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
InnoDB: Operation close to file d:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 2493
2018-11-13 1:35:46 7996 [ERROR] InnoDB: File (unknown): 'close' returned OS error 206. Cannot continue operation
181113 1:35:46 [ERROR] 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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.36-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787136 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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlValidSecurityDescriptor()
ntdll.dll!RtlValidSecurityDescriptor()
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.
2018-11-13 01:36:38 29b4 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.
2018-11-13 1:36:38 10676 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-11-13 1:36:38 10676 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-11-13 1:36:38 10676 [Note] InnoDB: The InnoDB memory heap is disabled
2018-11-13 1:36:38 10676 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-11-13 1:36:38 10676 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-11-13 1:36:38 10676 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-11-13 1:36:38 10676 [Note] InnoDB: Using generic crc32 instructions
2018-11-13 1:36:38 10676 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-11-13 1:36:38 10676 [Note] InnoDB: Completed initialization of buffer pool
2018-11-13 01:36:39 29b4 InnoDB: Operating system error number 6 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
InnoDB: Operation close to file d:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 2493
2018-11-13 1:36:39 10676 [ERROR] InnoDB: File (unknown): 'close' returned OS error 206. Cannot continue operation
181113 1:36:39 [ERROR] 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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.36-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787136 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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlValidSecurityDescriptor()
ntdll.dll!RtlValidSecurityDescriptor()
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.
---------------------------------------------------------

one thing I notices was this line in the innodb section: d:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 2493

needless to say I don't have a d:\win32-packages\... file so perhaps thats the problem.

How do I fix it?

Steps taken: Installed MySQL Community server--didn't help. Uninstalled, Uninstalled XAMPP.
Reinstalled XAMPP - same problem
checked ports again
UNINSTALLED XAMPP AGAIN
reinstalled XAMPP - same problem.

I notice the build date on the control panel was 2015, is XAMPP dead or just old?

I'm going to try installing an even older version of XAMPP that worked previously. Perhaps that will solve it, but if anyone knows what the problem is, let me know. Thanks.
jaseinatl
 
Posts: 1
Joined: 13. November 2018 07:39
XAMPP version: 3.22
Operating System: Windows 10

Re: Unable to keep MySQL running on new install

Postby djwest » 01. February 2019 16:43

found this in another post- seems to get past the OS error 6

Open MySQL config file by “Config” —> “my.ini”.
Insert
innodb_flush_method=normal
between
innodb_lock_wait_timeout = 50
and
## UTF 8 Settings


Start MySQL again in xampp.
djwest
 
Posts: 1
Joined: 01. February 2019 16:40
XAMPP version: 3.2.2
Operating System: windows 10

Re: Unable to keep MySQL running on new install

Postby andrew_ » 12. March 2019 02:47

@djwest Thank you!!! All currently available XAMPP versions fail here when initializing mysql. Took me couple of hours searching around for "system error 6", "OS error 206", etc.

Why isn't that setting already in my.ini?? :)
andrew_
 
Posts: 1
Joined: 12. March 2019 02:41
XAMPP version: 732-2
Operating System: Win10


Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 62 guests