I recently got a virus in my computer, and had to reinstall windows. Luckily I have everything on separate HDDs, so I thought it was just to reformat and start XAMPP again. But apparently it wasn't that easy, I keep getting this error message when I try to start MySQL
2014-04-18 10:26:35 3200 [Note] Plugin 'FEDERATED' is disabled.
2014-04-18 10:26:35 bb4 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-04-18 10:26:35 3200 [Note] InnoDB: The InnoDB memory heap is disabled
2014-04-18 10:26:35 3200 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-04-18 10:26:35 3200 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-04-18 10:26:35 3200 [Note] InnoDB: Not using CPU crc32 instructions
2014-04-18 10:26:35 3200 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-04-18 10:26:35 3200 [Note] InnoDB: Completed initialization of buffer pool
2014-04-18 10:26:43 3200 [Note] InnoDB: Highest supported file format is Barracuda.
2014-04-18 10:26:45 bb4 InnoDB: Operating system error number 1117 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
2014-04-18 10:26:45 3200 [ERROR] InnoDB: File D:\xampp\mysql\data\ib_logfile0: 'Windows aio' returned OS error 1217. Cannot continue operation
What can i do to fix it? I don't want to lose the data I have in my MySQL server.
please test this method,copy mysql/data/ibdata1 to another place, if windows couldnt copy that file, this means file crashed with Unwanted windows shutdown.so ibdata1 i/o error Happened. you simlpy must run windows drive error checking on xampp drive. windows automaticaly recover your ibdata1 file.
Related
Right now I am learning how to code HTML and PHP and use SQL. I am using XAMPP for mysql. Whenever I try to start mysql I always get an error. This is the error log.
2018-02-24 17:22:30 f04 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-02-24 17:22:30 3844 [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-02-24 17:22:31 3844 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-02-24 17:22:31 3844 [Note] InnoDB: The InnoDB memory heap is disabled
2018-02-24 17:22:31 3844 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-02-24 17:22:31 3844 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-02-24 17:22:31 3844 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-02-24 17:22:31 3844 [Note] InnoDB: Using generic crc32 instructions
2018-02-24 17:22:31 3844 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-02-24 17:22:31 3844 [Note] InnoDB: Completed initialization of buffer pool
2018-02-24 17:22:31 3844 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2018-02-24 17:22:31 3844 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2018-02-24 17:22:31 3844 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2018-02-24 17:22:31 3844 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2018-02-24 17:22:31 f04 InnoDB: Error: Write to file C:\xampp\mysql\data\ib_logfile101 failed at offset 0.
InnoDB: 512 bytes should have been written, only 0 were written.
InnoDB: Operating system error number 87.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk quota exceeded.
InnoDB: FormatMessage: Error number 87 means 'The parameter is incorrect.
'.
InnoDB: Error number 87 means 'Unknown error'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2018-02-24 17:22:31 f04 InnoDB: Operating system error number 87 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 os_file_write_func to file D:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 5097
2018-02-24 17:22:31 3844 [ERROR] InnoDB: File C:\xampp\mysql\data\ib_logfile101: 'os_file_write_func' returned OS error 287. Cannot continue operation
180224 17:22:31 [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.30-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 = 787129 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!?compare_ulonglong##YAHPB_K0#Z()
mysqld.exe!no_key()
mysqld.exe!no_key()
mysqld.exe!no_key()
mysqld.exe!no_key()
mysqld.exe!no_key()
mysqld.exe!no_key()
mysqld.exe!no_key()
mysqld.exe!?compare_ulonglong##YAHPB_K0#Z()
mysqld.exe!?compare_ulonglong##YAHPB_K0#Z()
mysqld.exe!?str_result#Item##UAEPAVString##PAV2##Z()
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!RtlGetAppContainerNamedObjectPath()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
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.
I have tried deleting the ibdata1, ib_logfile1 and ib_logfile0 and the mysql_error in the C:\xampp\mysql\data folder but it hasn't helped. I dont know what to do and how to fix it. I have read other questions on this website and topic but none of the solutions given help me. Please help!
I've installed Windows 10 Enterprise 64bit on machine and attempting to install Apache, PHP and MySQL on my machine to use for web development. In short I keep running into an error "MySQL shutdown unexpectedly". I've attempted to install using WAMP and XAMPP on my machine and still run into the same error. Apache connects and works on both WAMP and XAMPP however I get the same MySQL error.
So far from all the research I've done please find a synopsis of my situation and the solutions I've tried. I'm thinking this is to do with Windows 10. Also as a side note I'm using bootcamp on my MacBook 12 inch so not sure if this adding to the problem but I would not have thought so.
Apache running on port 80:433 for both XAMPP and WAMP
WAMP - Mysql -> service, start/resume service is green. When I click on it nothing happens. XAMP I get:
8:50:59 AM [mysql] Error: MySQL shutdown unexpectedly.
8:50:59 AM [mysql] This may be due to a blocked port, missing dependencies,
8:50:59 AM [mysql] improper privileges, a crash, or a shutdown by another method.
8:50:59 AM [mysql] Press the Logs button to view error logs and check
8:50:59 AM [mysql] the Windows Event Viewer for more clues
8:50:59 AM [mysql] If you need more help, copy and post this
8:50:59 AM [mysql] entire log window on the forums
Turned off windows firewall, same errors
4.I've checked for skype but it is actually not installed on my machine.Also checked control panel -> view local services, skype is not there nor running Tried netstat-b in the command prompt and I can't see anything with port 80. Also tried netstat -aon | findstr :80, only TCP 192.168.0.10:49556 23.205.116.42:80 ESTABLISHED 1884. Note: If the port was an issue Apache should not be working
I checked the control panel -> view local services there is no World Wide Web Publishing Service.
Followed solution in Xamp-Mysql Shutdown which included deleting ib_logfile1, ib_logfile and ibdata1. As well as appending my.ini with innodb_force_recovery = 1. I get a slightly different error which I put below.
I'm pretty much out of options and about to give into the fact that MySQL may not work on my windows 10 machine. But before I do any help would be appreciated.
Error Logs:
2015-08-08 08:31:08 7024 [Note] Plugin 'FEDERATED' is disabled.
2015-08-08 08:31:08 18ec 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-08-08 08:31:08 7024 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-08-08 08:31:08 7024 [Note] InnoDB: The InnoDB memory heap is disabled
2015-08-08 08:31:08 7024 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-08-08 08:31:08 7024 [Note] InnoDB: Memory barrier is not used
2015-08-08 08:31:08 7024 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-08-08 08:31:08 7024 [Note] InnoDB: Not using CPU crc32 instructions
2015-08-08 08:31:08 7024 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-08-08 08:31:08 7024 [Note] InnoDB: Completed initialization of buffer pool
2015-08-08 08:31:08 7024 [Note] InnoDB: Highest supported file format is Barracuda.
2015-08-08 08:31:08 18ec InnoDB: Operating system error number 87 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
2015-08-08 08:31:08 7024 [ERROR] InnoDB: File C:\wamp\mysql\data\ib_logfile0: 'aio read' returned
Error Log # innodb_force_recovery = 1
2015-08-08 09:32:05 3804 [Note] Plugin 'FEDERATED' is disabled.
2015-08-08 09:32:05 1bf8 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-08-08 09:32:05 3804 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-08-08 09:32:05 3804 [Note] InnoDB: The InnoDB memory heap is disabled
2015-08-08 09:32:05 3804 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-08-08 09:32:05 3804 [Note] InnoDB: Memory barrier is not used
2015-08-08 09:32:05 3804 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-08-08 09:32:05 3804 [Note] InnoDB: Not using CPU crc32 instructions
2015-08-08 09:32:05 3804 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-08-08 09:32:05 3804 [Note] InnoDB: Completed initialization of buffer pool
2015-08-08 09:32:05 3804 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2015-08-08 09:32:05 3804 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2015-08-08 09:32:05 3804 [Note] InnoDB: Database physically writes the file full: wait...
2015-08-08 09:32:05 3804 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2015-08-08 09:32:05 3804 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2015-08-08 09:32:05 1bf8 InnoDB: Operating system error number 87 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
2015-08-08 09:32:05 3804 [ERROR] InnoDB: File C:\xampp\mysql\data\ib_logfile101: 'aio write' returned OS error 187. Cannot continue operation
This solution worked for me.
Uninstall XAMPP and WAMP
Installed WAMP 64bit
Added the following line to my.ini
innodb_flush_method=normal
Closed WAMP and restarted. Logo W is green and working.
Thank you to: Error 187
I need some help with MySql in xampp 3.2.1. The MySql Service won't start and I couldn't find the reason why because the error log file reports that it cannot read from an 'unknown file' and only returns the error 0.
I don't know what that means since it's basically saying that there is 0 error when it tries to read the unknown file.
Here's the error log:
2015-01-20 10:36:12 760 [Note] Plugin 'FEDERATED' is disabled.
2015-01-20 10:36:12 574 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-01-20 10:36:12 760 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-01-20 10:36:12 760 [Note] InnoDB: The InnoDB memory heap is disabled
2015-01-20 10:36:12 760 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-01-20 10:36:12 760 [Note] InnoDB: Memory barrier is not used
2015-01-20 10:36:12 760 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-01-20 10:36:12 760 [Note] InnoDB: Not using CPU crc32 instructions
2015-01-20 10:36:12 760 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-01-20 10:36:12 760 [Note] InnoDB: Completed initialization of buffer pool
2015-01-20 10:36:12 760 [Note] InnoDB: Highest supported file format is Barracuda.
2015-01-20 10:36:12 760 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 131153885 in the ib_logfiles!
2015-01-20 10:36:12 760 [Note] InnoDB: Database was not shutdown normally!
2015-01-20 10:36:12 760 [Note] InnoDB: Starting crash recovery.
2015-01-20 10:36:12 760 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-01-20 10:36:12 760 [ERROR] InnoDB: File (unknown): 'read' returned OS error 0. Cannot continue operation
Please Help.
This is for a different error code but see if it works.
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.
https://community.apachefriends.org/f/viewtopic.php?f=16&t=72437
I have had the exact same issue - running the same version of XAMPP and it just started happening around the same time as your issue.
Try this. Open up your XAMPP directory and go to XAMPP/mysql/Data
cut all of the files (ibdata*, auto.cnf, mysql.pid) and put them somewhere else.
Try to start up Mysql - if that works great, if not, what you may have to do, is look in your log which DB is giving you an issue - and move that corresponding folder as well.
with luck, that will fix your problem - well it worked for me!
Restarted my server
getting no where with this error
tried changing port numbers
trid changing permissions on the specific it asked.
any help with this will be greatly appreciated.
I'm using XIBO on xamppp and the MYSQL database wont start so now i cant configure the XIBO, but when XAMPP is running without MYSQL i can view the content.
Below are the logs of the problem i am having.
Again thanking you in advance regarding this.
2013-11-27 09:29:11 848 [Note] Plugin 'FEDERATED' is disabled.
2013-11-27 09:29:11 ea0 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.
2013-11-27 09:29:11 848 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-27 09:29:11 848 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-11-27 09:29:11 848 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-27 09:29:11 848 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-27 09:29:11 848 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-11-27 09:29:11 848 [Note] InnoDB: Completed initialization of buffer pool
2013-11-27 09:29:11 848 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-27 09:29:11 848 [Note] InnoDB: The log sequence numbers 3140458 and 3140458 in ibdata files do not match the log sequence number 3747628 in the ib_logfiles!
2013-11-27 09:29:11 848 [Note] InnoDB: Database was not shutdown normally!
2013-11-27 09:29:11 848 [Note] InnoDB: Starting crash recovery.
2013-11-27 09:29:11 848 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-11-27 09:29:11 848 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd. Cannot open tablespace xibo/bandwidth which uses space ID: 1 at filepath: .\xibo\bandwidth.ibd
InnoDB: Error: could not open single-table tablespace file .\xibo\bandwidth.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
If your computer running "skype", just quit it then start MySQL. Because they both may use same port number
i installed apache and mysql 5.5 on windows 7 64 bit. it worked but today mysql can not start and windows give me this error "Can't start MySQL Error 1067" when i try to start mysql manually.
.
i see this lines in error log :
120616 16:35:47 [Note] Plugin 'FEDERATED' is disabled.
120616 16:35:48 InnoDB: The InnoDB memory heap is disabled
120616 16:35:48 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120616 16:35:48 InnoDB: Compressed tables use zlib 1.2.3
120616 16:35:48 InnoDB: Initializing buffer pool, size = 103.0M
120616 16:35:48 InnoDB: Completed initialization of buffer pool
120616 16:35:48 InnoDB: highest supported file format is Barracuda.
120616 16:35:50 InnoDB: **Operating system error number 1117 in a file operation.**
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
InnoDB: File name .\ib_logfile0
InnoDB: File operation call: 'Windows aio'.
InnoDB: Cannot continue operation.
what is problem and InnoDB: Operating system error number 1117 in a file operation.
?
what can i do?
i find this link. i removed the ib_logfile0 or ib_logfile1 in the data folder and it works.