I am running 2 locally hosted wp sites for testing on my Win 7 pc. Unfortunately windows update did a update install and reboot last night while wamp was online.
Usually I can fix this myself, but I am having no luck. After about 6 hours of search for a resolution I turn to you wonderful people.
PROBLEM: Orange Icon.
PhpMyAdmin error #2002
Here is my error log:
2014-02-25 13:12:44 4420 [Note] Plugin 'FEDERATED' is disabled
2014-02-25 13:12:44 4420 [Note] InnoDB: The InnoDB memory heap is disabled
2014-02-25 13:12:44 4420 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-02-25 13:12:44 4420 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-02-25 13:12:44 4420 [Note] InnoDB: Not using CPU crc32 instructions
2014-02-25 13:12:44 4420 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-02-25 13:12:44 4420 [Note] InnoDB: Completed initialization of buffer pool
2014-02-25 13:12:44 4420 [Note] InnoDB: Highest supported file format is Barracuda.
2014-02-25 13:12:44 4420 [Note] InnoDB: The log sequence numbers 12054850 and 12054850 in ibdata files do not match the log sequence number 12746597 in the ib_logfiles!
2014-02-25 13:12:44 4420 [Note] InnoDB: Database was not shutdown normally!
2014-02-25 13:12:44 4420 [Note] InnoDB: Starting crash recovery.
2014-02-25 13:12:44 4420 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-02-25 13:12:44 4420 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace dlkei4n83xuf/rvcommentmeta uses space ID: 11 at filepath: .\dlkei4n83xuf\rvcommentmeta.ibd. Cannot open tablespace test/rvscommentmeta which uses space ID: 11 at filepath: .\test\rvscommentmeta.ibd
InnoDB: Error: could not open single-table tablespace file .\test\rvscommentmeta.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.
Related
this is my issue please help me to solve this problem ...
6:25:59 AM [mysql] Error: MySQL shutdown unexpectedly.
6:25:59 AM [mysql] This may be due to a blocked port, missing dependencies,
6:25:59 AM [mysql] improper privileges, a crash, or a shutdown by another method.
6:25:59 AM [mysql] Press the Logs button to view error logs and check
6:25:59 AM [mysql] the Windows Event Viewer for more clues
6:25:59 AM [mysql] If you need more help, copy and post this
6:25:59 AM [mysql] entire log window on the forums
in the error log file is show me this .....
InnoDB: using atomic writes.
2021-05-03 6:25:51 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2021-05-03 6:25:51 0 [Note] InnoDB: Uses event mutexes
2021-05-03 6:25:51 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-05-03 6:25:51 0 [Note] InnoDB: Number of pools: 1
2021-05-03 6:25:51 0 [Note] InnoDB: Using SSE2 crc32 instructions
2021-05-03 6:25:51 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk
size = 16M
2021-05-03 6:25:51 0 [Note] InnoDB: Completed initialization of buffer pool
2021-05-03 6:25:51 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2021-05-03 6:25:51 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2021-05-03 6:25:51 0 [Note] InnoDB: Setting file 'C:\xamppnew\mysql\data\ibtmp1' size to 12 MB.
Physically writing the file full; Please wait ...
2021-05-03 6:25:51 0 [Note] InnoDB: File 'C:\xamppnew\mysql\data\ibtmp1' size is now 12 MB.
2021-05-03 6:25:51 0 [Note] InnoDB: Waiting for purge to start
2021-05-03 6:25:51 0 [Note] InnoDB: 10.4.16 started; log sequence number 47090; transaction id 8
2021-05-03 6:25:51 0 [Note] InnoDB: Loading buffer pool(s) from
C:\xamppnew\mysql\data\ib_buffer_pool
2021-05-03 6:25:51 0 [Note] Plugin 'FEEDBACK' is disabled.
2021-05-03 6:25:51 0 [Note] InnoDB: Buffer pool(s) load completed at 210503 6:25:51
2021-05-03 6:25:51 0 [Note] Server socket created on IP: '::'.
I believe there is a duplicate for this question.
Please refer to the link below as there is answer available for it.
MySql shuts down unexpectedly
I'm trying to use mysql with xampp on windows 7 and I'm getting lot of errors.
I am able to run mysql through the command prompt just fine, so long as it is not running in xampp. here are the things I've done so far:
changed skype port settings
changed the password that xampp uses to match my mysql password
changed environment variables and PATH variable in windows 7
removed all oracle database related things in environment variables and PATH
Of note is that I can't use xampp and mysql while mysql server is listening on port 3036. I installed MySQL server 5.7.
Here is an image of my xampp dashboard:
http://i.imgur.com/g9gVV6w.png
Below is my mysql_error file contents:
2016-12-05 21:40:28 f1c 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.
2016-12-05 21:40:28 3868 [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.
2016-12-05 21:40:28 3868 [Note] InnoDB: Using mutexes to ref count
buffer pool pages
2016-12-05 21:40:28 3868 [Note] InnoDB: The InnoDB memory heap is
disabled
2016-12-05 21:40:28 3868 [Note] InnoDB: Mutexes and rw_locks use
Windows interlocked functions
2016-12-05 21:40:28 3868 [Note] InnoDB: _mm_lfence() and _mm_sfence()
are used for memory barrier
2016-12-05 21:40:28 3868 [Note] InnoDB: Compressed tables use zlib
1.2.3
2016-12-05 21:40:28 3868 [Note] InnoDB: Using generic crc32
instructions
2016-12-05 21:40:28 3868 [Note] InnoDB: Initializing buffer pool, size
= 16.0M
2016-12-05 21:40:28 3868 [Note] InnoDB: Completed initialization of
buffer pool
2016-12-05 21:40:28 3868 [Note] InnoDB: Highest supported file format
is Barracuda.
2016-12-05 21:40:29 3868 [Note] InnoDB: 128 rollback segment(s) are
active.
2016-12-05 21:40:29 3868 [Note] InnoDB: Waiting for purge to start
2016-12-05 21:40:29 3868 [Note] InnoDB: Percona XtraDB
(http://www.percona.com)
5.6.32-79.0 started; log sequence number 1840435
2016-12-05 21:40:29 6480 [Note] InnoDB: Dumping buffer pool(s) not yet
started
2016-12-05 21:40:29 3868 [Note] Plugin 'FEEDBACK' is disabled.
2016-12-05 21:40:29 3868 [Note] Server socket created on IP: '::'.
2016-12-05 21:40:29 3868 [Note] c:\xampp\mysql\bin\mysqld.exe: ready
for connections.
Version: '10.1.19-MariaDB' socket: '' port: 3306 mariadb.org binary
distribution
I'm nonplussed.
I configured mysql to login as user root with a password. However it worked when I tried to login with no password.
I tried shutting down XAMPP and deleting the ibdata1 already. Yesterday the server did still work, but when starting up today it didn't start anymore. I'm using the server for a PHP project using PHPMyAdmin.
This is the error log from XAMPP:
2016-05-26 09:07:29 15a0 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.
160526 9:07:29 [Note] InnoDB: Using mutexes to ref count buffer pool pages
160526 9:07:29 [Note] InnoDB: The InnoDB memory heap is disabled
160526 9:07:29 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
160526 9:07:29 [Note] InnoDB: Memory barrier is not used
160526 9:07:29 [Note] InnoDB: Compressed tables use zlib 1.2.3
160526 9:07:29 [Note] InnoDB: Not using CPU crc32 instructions
160526 9:07:29 [Note] InnoDB: Initializing buffer pool, size = 16.0M
160526 9:07:29 [Note] InnoDB: Completed initialization of buffer pool
160526 9:07:29 [Note] InnoDB: Restoring page 0 of tablespace 0
160526 9:07:29 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
160526 9:07:29 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\xampp\mysql\data\ibdata1
160526 9:07:29 [ERROR] InnoDB: Could not open or create the system tablespace.
If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt.
InnoDB only wrote those files full of zeros, but did not yet use them in any way.
But be careful: do not remove old data files which contain your precious data!
160526 9:07:29 [ERROR] Plugin 'InnoDB' init function returned error.
160526 9:07:29 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
160526 9:07:29 [Note] Plugin 'FEEDBACK' is disabled.
160526 9:07:29 [ERROR] Unknown/unsupported storage engine: InnoDB
160526 9:07:29 [ERROR] Aborting
160526 9:07:29 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete`
I don't know what's happening to mysql , it doesn't start up. IT was working fine yesterday but today it won't start. I haven't installed any program nor messed up with any settings's. Tried changing ports but won't help
below is the log report and i have no idea whats it is about. Please help me i have a project to submit and mysql won't start up.
160112 17:31:16 [Note] InnoDB: Using mutexes to ref count buffer pool pages
160112 17:31:16 [Note] InnoDB: The InnoDB memory heap is disabled
160112 17:31:16 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
160112 17:31:16 [Note] InnoDB: Memory barrier is not used
160112 17:31:16 [Note] InnoDB: Compressed tables use zlib 1.2.3
160112 17:31:16 [Note] InnoDB: Not using CPU crc32 instructions
160112 17:31:16 [Note] InnoDB: Initializing buffer pool, size = 16.0M
160112 17:31:16 [Note] InnoDB: Completed initialization of buffer pool
160112 17:31:17 [Note] InnoDB: Highest supported file format is Barracuda.
160112 17:31:17 [Note] InnoDB: The log sequence numbers 33725452 and 33725452 in ibdata files do not match the log sequence number 42635885 in the ib_logfiles!
160112 17:31:17 [Note] InnoDB: Database was not shutdown normally!
160112 17:31:17 [Note] InnoDB: Starting crash recovery.
160112 17:31:17 [Note] InnoDB: Reading tablespace information from the .ibd files...
160112 17:31:17 [Note] InnoDB: Restoring possible half-written data pages
160112 17:31:17 [Note] InnoDB: from the doublewrite buffer...
160112 17:31:18 [Note] InnoDB: 128 rollback segment(s) are active.
160112 17:31:18 [Note] InnoDB: Waiting for purge to start
160112 17:31:18 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.22-72.0 started; log sequence number 42635885
160112 17:31:18 [Note] Plugin 'FEEDBACK' is disabled.
160112 17:31:18 [Note] Server socket created on IP: '::'.
XAMPP MySQL shuts down unexpectedly. I was trying to enable the configuration storage settings earlier, turned my PC off, and returned to this. I have uninstalled and reinstalled XAMPP within the past couple of days, changed port numbers to apache and setup a password.
I've deleted the ibdata1, ib_logfile0, and the ib_logfile1 files, and changes the port numbers to the my.ini and php.ini files.
Help would be appreciated.
2015-11-10 17:40:54 418 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.
151110 17:40:54 [Note] InnoDB: Using mutexes to ref count buffer pool pages
151110 17:40:54 [Note] InnoDB: The InnoDB memory heap is disabled
151110 17:40:54 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
151110 17:40:54 [Note] InnoDB: Memory barrier is not used
151110 17:40:54 [Note] InnoDB: Compressed tables use zlib 1.2.3
151110 17:40:54 [Note] InnoDB: Not using CPU crc32 instructions
151110 17:40:54 [Note] InnoDB: Initializing buffer pool, size = 16.0M
151110 17:40:54 [Note] InnoDB: Completed initialization of buffer pool
151110 17:40:54 [Note] InnoDB: Restoring page 0 of tablespace 0
151110 17:40:54 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
151110 17:40:54 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\xampp\mysql\data\ibdata1
151110 17:40:54 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
151110 17:40:54 [ERROR] Plugin 'InnoDB' init function returned error.
151110 17:40:54 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151110 17:40:54 [Note] Plugin 'FEEDBACK' is disabled.
151110 17:40:54 [ERROR] Unknown/unsupported storage engine: InnoDB
151110 17:40:54 [ERROR] Aborting
151110 17:40:54 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete