I am getting Error while starting mysql using xampp . I dont know how to fix this
Error: MySQL shutdown unexpectedly.
This may be due to a blocked port, missing dependencies,
improper privileges, a crash, or a shutdown by another method.
Press the Logs button to view error logs and check
the Windows Event Viewer for more clues
If you need more help, copy and post this
entire log window on the forums
log file says
2014-10-08 11:40:53 5788 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-10-08 11:40:53 5788 [Note] InnoDB: The InnoDB memory heap is disabled
2014-10-08 11:40:53 5788 [Note] InnoDB: Mutexes and rw_locks interlocked functions
2014-10-08 11:40:53 5788 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-10-08 11:40:53 5788 [Note] InnoDB: Not using CPU crc32 instructions
2014-10-08 11:40:53 5788 [Note] InnoDB: Initializing buffer pool, size = 1.0G
2014-10-08 11:40:53 5788 [Note] InnoDB: Completed initialization of buffer pool
2014-10-08 11:40:53 5788 [Note] InnoDB: Highest supported file format is Barracuda.
2014-10-08 11:40:53 5788 [Note] InnoDB: The log sequence numbers 115503975998 and 115503975998 in ibdata files do not match the log sequence number 189324800563 in the ib_logfiles!
2014-10-08 11:40:53 5788 [Note] InnoDB: Database was not shutdown normally!
2014-10-08 11:40:53 5788 [Note] InnoDB: Starting crash recovery.
2014-10-08 11:40:53 5788 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-10-08 11:40:53 11e8 InnoDB: Operating system error number 5 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory. It may also be you have created a subdirectory
InnoDB: of the same name as a data file.
InnoDB: Error: could not open single-table tablespace file .\trillium_data\insulist_id_exist.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.
what steps should i take?
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.
We have a MySQL database and last night there was a power outage which caused the machine it runs under to crash.
Now with the machine restarted, I am trying to run the MySQL service and I get the error:
"Error 1067: The process terminated unexpectedly"
Extract from the log:
2015-12-14 08:56:17 1248 [Note] Plugin 'FEDERATED' is disabled.
2015-12-14 08:56:17 1248 [Warning] option 'innodb-autoextend-increment': unsigned value 67108864 adjusted to 1000
2015-12-14 08:56:17 d64 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-12-14 08:56:17 1248 [Note] InnoDB: The InnoDB memory heap is disabled
2015-12-14 08:56:17 1248 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-12-14 08:56:17 1248 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-12-14 08:56:17 1248 [Note] InnoDB: Not using CPU crc32 instructions
2015-12-14 08:56:17 1248 [Note] InnoDB: Initializing buffer pool, size = 38.0M
2015-12-14 08:56:17 1248 [Note] InnoDB: Completed initialization of buffer pool
2015-12-14 08:56:17 1248 [Note] InnoDB: Highest supported file format is Barracuda.
2015-12-14 08:56:17 1248 [Note] InnoDB: The log sequence numbers 33664440039 and 33664440039 in ibdata files do not match the log sequence number 35948349561 in the ib_logfiles!
2015-12-14 08:56:17 1248 [Note] InnoDB: Database was not shutdown normally!
2015-12-14 08:56:17 1248 [Note] InnoDB: Starting crash recovery.
2015-12-14 08:56:17 1248 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-12-14 08:56:24 1248 [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 teamcity/action_history which uses space ID: 1 at filepath: .\teamcity\action_history.ibd
InnoDB: Error: could not open single-table tablespace file .\teamcity\action_history.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.
Anyone have a solution to this?
The solution, as the message indicates, is likely to be performing innodb_force_recovery > 0.
To do this, just edit my.cnf, search the file for innodb_force_recovery, it'll look like this:
#innodb_force_recovery = 0
Edit it thusly:
innodb_force_recovery = 2
Then restart the MySQL service. After stopping and restarting it, go back and replace the # in the my.cnf file, then restart the service again. Hopefully, you are able to access your tables. If not, try repeating the process, only set the value to 3 instead. Do not go higher than 3 without further researching innodb_force_recovery.
Best of luck, hope this helps.
Mysql craches almost every day and I need to restart MYSQL..
Own VPS 512MB ram, mysql logs :
131115 10:03:36 [Note] Plugin 'FEDERATED' is disabled.
131115 10:03:36 InnoDB: The InnoDB memory heap is disabled
131115 10:03:36 InnoDB: Mutexes and rw_locks use GCC atomic builtins
131115 10:03:36 InnoDB: Compressed tables use zlib 1.2.3.4
131115 10:03:36 InnoDB: Initializing buffer pool, size = 128.0M
131115 10:03:36 InnoDB: Completed initialization of buffer pool
131115 10:03:36 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
131115 10:03:36 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
Is this log about shutting down or starting?
I suppose your machine was abnormally shut down which caused damage of logs. So, your db files are inconsistent because of mysqld was not stopped gracefully and your log-files (durability records) are inconsistent too because of physical storage damage.
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
In my Moodle database, everytime I select the mdl_certificate table, the MySQL server goes down. I thought it could be a problem with the PHPMyAdmin, but I installed the MySQL Workbench and the same still happens.
So I tried the console. The problem persists. I got two prints:
I've never seen this. How can I solve it?
Thanks!
UPDATE:
This is the log around the time the error was showed:
130411 8:51:20 [Note] Plugin 'FEDERATED' is disabled.
130411 8:51:20 InnoDB: The InnoDB memory heap is disabled
130411 8:51:20 InnoDB: Mutexes and rw_locks use Windows interlocked functions
130411 8:51:20 InnoDB: Compressed tables use zlib 1.2.3
130411 8:51:20 InnoDB: Initializing buffer pool, size = 128.0M
130411 8:51:20 InnoDB: Completed initialization of buffer pool
130411 8:51:20 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
130411 8:51:20 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
130411 8:51:20 InnoDB: Operating system error number 1392 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 .\prestashopprod
InnoDB: File operation call: 'readdir_next_file'.
InnoDB: Error: os_file_readdir_next_file() returned -1 in
InnoDB: directory .\prestashopprod
InnoDB: Crash recovery may have failed for some .ibd files!
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Last MySQL binlog file position 0 4793, file name .\mysql-bin.000062
130411 8:51:33 InnoDB: Waiting for the background threads to start
130411 8:51:34 InnoDB: 1.1.8 started; log sequence number 795429719
130411 8:51:34 [Note] Recovering after a crash using mysql-bin
130411 8:51:34 [Note] Starting crash recovery...
130411 8:51:34 [Note] Crash recovery finished.
130411 8:51:34 [Note] Event Scheduler: Loaded 0 events
130411 8:51:34 [Note] wampmysqld: ready for connections.
Version: '5.5.20-log' socket: '' port: 3306 MySQL Community Server (GPL)
The solution was drop the tables and re-create them. Luckly, they were empty.