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
Related
I have AMPPS installed on my Windows 10.
I was unable to start MySQL. I have searched through this error and tried different things to recover my data.
This was the error log:
2016-02-03 10:19:54 6448 [Warning] You need to use --log-bin to make --binlog-format work.
2016-02-03 10:19:54 6448 [Note] Plugin 'FEDERATED' is disabled.
2016-02-03 10:19:54 6448 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-02-03 10:19:54 6448 [Note] InnoDB: The InnoDB memory heap is disabled
2016-02-03 10:19:54 6448 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-02-03 10:19:54 6448 [Note] InnoDB: Memory barrier is not used
2016-02-03 10:19:54 6448 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-02-03 10:19:54 6448 [Note] InnoDB: Not using CPU crc32 instructions
2016-02-03 10:19:54 6448 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-02-03 10:19:54 6448 [Note] InnoDB: Completed initialization of buffer pool
2016-02-03 10:19:54 6448 [Note] InnoDB: Highest supported file format is Barracuda.
2016-02-03 10:19:54 6448 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 132125643 in the ib_logfiles!
2016-02-03 10:19:54 6448 [Note] InnoDB: Database was not shutdown normally!
2016-02-03 10:19:54 6448 [Note] InnoDB: Starting crash recovery.
2016-02-03 10:19:54 6448 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-02-03 10:19:54 6448 [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 scrapers/openpasts_records which uses space ID: 1 at filepath: .\scrapers\openpasts_records.ibd
InnoDB: Error: could not open single-table tablespace file .\scrapers\openpasts_records.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.
I have tried setting innodb_force_recovery = 1 in my.cnf
Also I have tried removing ibdata1 file as well.
After removing ibdata1, MySQL started perfectly.
and my table shows in PHPmyADMIN, but when I click on it it says table does not exists even it exists
In my D:\Ampps\mysql\data\scrapers directory, I can see records.ibd file and records.frm file as well. That means table physically exists but is corrupted.
Does someone know how do I recover that table?
set value of
innodb_force_recovery = 1
or 2 or 3 or 4
in my.ini file under [mysql]
try this hopefully it will solve your problem.
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!
I have I problem with starting mysql using AMPPS. I'm Using OS X Maverics and last version of Ammps. After little system crash and restart I can`t start mysql.
mysql.err
2014-01-22 18:12:41 398 [Note] Plugin 'FEDERATED' is disabled.
2014-01-22 18:12:41 398 [Note] InnoDB: The InnoDB memory heap is disabled
2014-01-22 18:12:41 398 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-01-22 18:12:41 398 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-01-22 18:12:41 398 [Note] InnoDB: Not using CPU crc32 instructions
2014-01-22 18:12:41 398 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-01-22 18:12:41 398 [Note] InnoDB: Completed initialization of buffer pool
2014-01-22 18:12:41 398 [Note] InnoDB: Highest supported file format is Barracuda.
2014-01-22 18:12:41 398 [Note] InnoDB: The log sequence numbers 1252002624 and 1252002624 in ibdata files do not match the log sequence number 1252003161 in the ib_logfiles!
2014-01-22 18:12:41 398 [Note] InnoDB: Database was not shutdown normally!
2014-01-22 18:12:41 398 [Note] InnoDB: Starting crash recovery.
2014-01-22 18:12:41 398 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-01-22 18:12:41 398 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace analytics/backlinks uses space ID: 1 at filepath: ./analytics/backlinks.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd
2014-01-22 18:12:41 a08901a8 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./mysql/innodb_table_stats.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.
Help me please. I have very important files in DB.
Solve!
Open AMPPS Application -> MySQL Tab -> Configuration.
In [mysqld] section, add the following line:
innodb_force_recovery = 1
Save the file and try starting MySQL
Remove that line which you just added and Save.
So I was facing a similar issue and what I tried was following:-
find / -name mysql
From the output of above command remove all the search results.Then do following:-
brew uninstall mysql
brew clean
Then reboot your machine once and then install once again using following:-
brew install mysql
P.S: I was getting this error error so I could not take backup of my db but I had not so much important data in DB so I removed it anyways
When I try running MySQL in XAMPP it gives me an error but everything else works fine. I already tried changing the ports on my.ini and I also tried Disabling two services but they were already disabled and enabled but MySQL still refuses to start.
Error:
2013-10-22 17:24:42 5276 [Note] Plugin 'FEDERATED' is disabled.
2013-10-22 17:24:42 8d8 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-10-22 17:24:42 5276 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-22 17:24:42 5276 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-22 17:24:42 5276 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-22 17:24:42 5276 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-22 17:24:42 5276 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-22 17:24:42 5276 [Note] InnoDB: Completed initialization of buffer pool
2013-10-22 17:24:42 5276 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-22 17:24:42 5276 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1600614 in the ib_logfiles!
2013-10-22 17:24:42 5276 [Note] InnoDB: Database was not shutdown normally!
2013-10-22 17:24:42 5276 [Note] InnoDB: Starting crash recovery.
2013-10-22 17:24:42 5276 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-22 17:24:42 5276 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace lg/users uses space ID: 5 at filepath: .\lg\users.ibd. Cannot open tablespace mysql/slave_worker_info which uses space ID: 5 at filepath: .\mysql\slave_worker_info.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\slave_worker_info.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.
I already looked for answers here (Everything that I mentioned I have tried was from here).
Thanks
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 8 years ago.
Improve this question
I am using xampp package on windows 8. When I am starting mysql I am getting this issue in error log.
2013-09-02 12:17:16 4320 [Note] Plugin 'FEDERATED' is disabled.
2013-09-02 12:17:16 1030 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-09-02 12:17:16 4320 [Note] InnoDB: The InnoDB memory heap is disabled
2013-09-02 12:17:16 4320 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-02 12:17:16 4320 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-02 12:17:16 4320 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-02 12:17:16 4320 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-02 12:17:16 4320 [Note] InnoDB: Completed initialization of buffer pool
2013-09-02 12:17:16 4320 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-02 12:17:16 4320 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 7359127 in the ib_logfiles!
2013-09-02 12:17:16 4320 [Note] InnoDB: Database was not shutdown normally!
2013-09-02 12:17:16 4320 [Note] InnoDB: Starting crash recovery.
2013-09-02 12:17:16 4320 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-02 12:17:17 4320 [ERROR] InnoDB: Attempted to open a
previously opened tablespace. Previous tablespace
mysql/slave_worker_info uses space ID: 5 at filepath:
.\mysql\slave_worker_info.ibd. Cannot open tablespace
pos/adminnotification_inbox which uses space ID: 5 at filepath:
.\pos\adminnotification_inbox.ibd InnoDB: Error: could not open
single-table tablespace file .\pos\adminnotification_inbox.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.
Please Reinstall it. this is mainly for missing and currepted files..