So yesterday everything was working fine, but today when I wanted to continue mySQL wouldnt start. Also my laptop shutdown at night if that is relevant. I have tried changing the port to 3307 but it didnt work.
Anyway here is the log
2016-08-19 12:55:09 1b34 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.
160819 12:55:09 [Note] InnoDB: Using mutexes to ref count buffer pool pages
160819 12:55:09 [Note] InnoDB: The InnoDB memory heap is disabled
160819 12:55:09 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
160819 12:55:09 [Note] InnoDB: Memory barrier is not used
160819 12:55:09 [Note] InnoDB: Compressed tables use zlib 1.2.3
160819 12:55:09 [Note] InnoDB: Not using CPU crc32 instructions
160819 12:55:09 [Note] InnoDB: Initializing buffer pool, size = 16.0M
160819 12:55:09 [Note] InnoDB: Completed initialization of buffer pool
160819 12:55:09 [Note] InnoDB: Highest supported file format is Barracuda.
160819 12:55:09 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1778208 in the ib_logfiles!
160819 12:55:09 [Note] InnoDB: Database was not shutdown normally!
160819 12:55:09 [Note] InnoDB: Starting crash recovery.
160819 12:55:09 [Note] InnoDB: Reading tablespace information from the .ibd files...
160819 12:55:09 [Note] InnoDB: Restoring possible half-written data pages
160819 12:55:09 [Note] InnoDB: from the doublewrite buffer...
160819 12:55:09 [Note] InnoDB: 128 rollback segment(s) are active.
160819 12:55:09 [Note] InnoDB: Waiting for purge to start
160819 12:55:09 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.22-72.0 started; log sequence number 1778208
160819 12:55:09 [Note] Plugin 'FEEDBACK' is disabled.
160819 12:55:09 [Note] Server socket created on IP: '::'.
And this is what it said in when I tried connecting.
5:10:04 [mysql] Attempting to start MySQL app...
15:10:04 [mysql] Status change detected: running
15:10:04 [mysql] Status change detected: stopped
15:10:04 [mysql] Error: MySQL shutdown unexpectedly.
15:10:04 [mysql] This may be due to a blocked port, missing dependencies,
15:10:04 [mysql] improper privileges, a crash, or a shutdown by another method.
15:10:04 [mysql] Press the Logs button to view error logs and check
15:10:04 [mysql] the Windows Event Viewer for more clues
15:10:04 [mysql] If you need more help, copy and post this
15:10:04 [mysql] entire log window on the forums
Related
I have installed XAMPP on windows 10, and Apache is running just fine but have an issue running MySQL. This is the error I get on XAMPP window:
14:23:51 [mysql] Error: MySQL shutdown unexpectedly.
14:23:51 [mysql] This may be due to a blocked port, missing dependencies,
14:23:51 [mysql] improper privileges, a crash, or a shutdown by another method.
14:23:51 [mysql] Press the Logs button to view error logs and check
14:23:51 [mysql] the Windows Event Viewer for more clues
14:23:51 [mysql] If you need more help, copy and post this
14:23:51 [mysql] entire log window on the forums
and this is what I have in the mysql_error.log:
2019-09-21 14:21:30 2ca4 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.
2019-09-21 14:21:30 11428 [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.
2019-09-21 14:21:30 11428 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-09-21 14:21:30 11428 [Note] InnoDB: The InnoDB memory heap is disabled
2019-09-21 14:21:30 11428 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-09-21 14:21:30 11428 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2019-09-21 14:21:30 11428 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-09-21 14:21:30 11428 [Note] InnoDB: Using generic crc32 instructions
2019-09-21 14:21:30 11428 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2019-09-21 14:21:30 11428 [Note] InnoDB: Completed initialization of buffer pool
2019-09-21 14:21:30 11428 [Note] InnoDB: Highest supported file format is Barracuda.
2019-09-21 14:21:31 11428 [Note] InnoDB: 128 rollback segment(s) are active.
2019-09-21 14:21:31 11428 [Note] InnoDB: Waiting for purge to start
2019-09-21 14:21:31 11428 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.42-84.2 started; log sequence number 1835037
2019-09-21 14:21:31 8100 [Note] InnoDB: Dumping buffer pool(s) not yet started
2019-09-21 14:21:31 11428 [Note] Plugin 'FEEDBACK' is disabled.
2019-09-21 14:21:31 11428 [Note] Server socket created on IP: '::'.
2019-09-21 14:21:31 11428 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 10048: Only one usage of each socket address (protocol/network address/port) is normally permitted.
2019-09-21 14:21:31 11428 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2019-09-21 14:21:31 11428 [ERROR] Aborting
2019-09-21 14:23:47 2f80 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.
2019-09-21 14:23:47 12160 [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.
2019-09-21 14:23:47 12160 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-09-21 14:23:47 12160 [Note] InnoDB: The InnoDB memory heap is disabled
2019-09-21 14:23:47 12160 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-09-21 14:23:47 12160 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2019-09-21 14:23:47 12160 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-09-21 14:23:47 12160 [Note] InnoDB: Using generic crc32 instructions
2019-09-21 14:23:47 12160 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2019-09-21 14:23:47 12160 [Note] InnoDB: Completed initialization of buffer pool
2019-09-21 14:23:47 12160 [Note] InnoDB: Highest supported file format is Barracuda.
2019-09-21 14:23:48 12160 [Note] InnoDB: 128 rollback segment(s) are active.
2019-09-21 14:23:48 12160 [Note] InnoDB: Waiting for purge to start
2019-09-21 14:23:48 12160 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.42-84.2 started; log sequence number 1835047
2019-09-21 14:23:49 5728 [Note] InnoDB: Dumping buffer pool(s) not yet started
2019-09-21 14:23:49 12160 [Note] Plugin 'FEEDBACK' is disabled.
2019-09-21 14:23:49 12160 [Note] Server socket created on IP: '::'.
2019-09-21 14:23:49 12160 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 10048: Only one usage of each socket address (protocol/network address/port) is normally permitted.
2019-09-21 14:23:49 12160 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2019-09-21 14:23:49 12160 [ERROR] Aborting
Have no idea what is going on re-installed the MySQL server this time enabled the InnoDB cluster still same error, someone please help, I am building a website and cant really test anything.. SOS
Change port of MySQL in the configuraiton file to 3306
Check if there is another service using 10048
If 1 and 2 don't work, change your port to one of these list: https://mysqlserverteam.com/mysql-guide-to-ports/
I am using XAMPP on my windows machine for PHP and MySQL. Whenever I attempted to the start the MySQL server from the XAMPP Control Panel V3.2.1. Only Apache server is starting and MySQL stops with the following error.
Error: MySQL shutdown unexpectedly.
11:41:12 AM [mysql] This may be due to a blocked port, missing dependencies,
11:41:12 AM [mysql] improper privileges, a crash, or a shutdown by another method.
11:41:12 AM [mysql] Press the Logs button to view error logs and check
11:41:12 AM [mysql] the Windows Event Viewer for more clues
11:41:12 AM [mysql] If you need more help, copy and post this
11:41:12 AM [mysql] entire log window on the forums
Also when I checked my log. I found the following error
2017-05-15 11:48:08 bc8 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.
170515 11:48:08 [Note] InnoDB: Using mutexes to ref count buffer pool pages
170515 11:48:08 [Note] InnoDB: The InnoDB memory heap is disabled
170515 11:48:08 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
170515 11:48:08 [Note] InnoDB: Memory barrier is not used
170515 11:48:08 [Note] InnoDB: Compressed tables use zlib 1.2.3
170515 11:48:08 [Note] InnoDB: Not using CPU crc32 instructions
170515 11:48:08 [Note] InnoDB: Initializing buffer pool, size = 16.0M
170515 11:48:08 [Note] InnoDB: Completed initialization of buffer pool
170515 11:48:08 [Note] InnoDB: Highest supported file format is Barracuda.
170515 11:48:08 [Note] InnoDB: Log scan progressed past the checkpoint lsn 12638736
170515 11:48:08 [Note] InnoDB: Database was not shutdown normally!
170515 11:48:08 [Note] InnoDB: Starting crash recovery.
170515 11:48:08 [Note] InnoDB: Reading tablespace information from the .ibd files...
170515 11:48:08 [Note] InnoDB: Restoring possible half-written data pages
170515 11:48:08 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 12638756
170515 11:48:09 [Note] InnoDB: 128 rollback segment(s) are active.
170515 11:48:09 [Note] InnoDB: Waiting for purge to start
170515 11:48:09 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.22-72.0 started; log sequence number 12638756
170515 11:48:09 [Note] Plugin 'FEEDBACK' is disabled.
170515 11:48:09 [Note] Server socket created on IP: '::'.
i have been trying to turn on mysql on xampp but it wouldn't turn on. i went to mysql logs and to the errorlog file and here are the things they gave.
2015-11-23 10:54:20 d274 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.
151123 10:54:20 [Note] InnoDB: Using mutexes to ref count buffer pool pages
151123 10:54:20 [Note] InnoDB: The InnoDB memory heap is disabled
151123 10:54:20 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
151123 10:54:20 [Note] InnoDB: Memory barrier is not used
151123 10:54:20 [Note] InnoDB: Compressed tables use zlib 1.2.3
151123 10:54:20 [Note] InnoDB: Not using CPU crc32 instructions
151123 10:54:20 [Note] InnoDB: Initializing buffer pool, size = 16.0M
151123 10:54:20 [Note] InnoDB: Completed initialization of buffer pool
151123 10:54:20 [Note] InnoDB: Highest supported file format is Barracuda.
151123 10:54:20 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1735623
151123 10:54:20 [Note] InnoDB: Database was not shutdown normally!
151123 10:54:20 [Note] InnoDB: Starting crash recovery.
151123 10:54:20 [Note] InnoDB: Reading tablespace information from the .ibd files...
151123 10:54:20 [Note] InnoDB: Restoring possible half-written data pages
151123 10:54:20 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1735633
151123 10:54:20 [Note] InnoDB: 128 rollback segment(s) are active.
151123 10:54:20 [Note] InnoDB: Waiting for purge to start
151123 10:54:20 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.22-72.0 started; log sequence number 1735633
151123 10:54:20 [Note] Plugin 'FEEDBACK' is disabled.
151123 10:54:20 [Note] Server socket created on IP: '::'.
The log seems ok for me. Maybe you have permission problem, try (right click) run as Administrator the Xampp
try check your active port, maybe used by another program. Mysql use 3306 as default port. go to your xampp folder try find "portcheck.exe" or something like that. see if your mysql port used or free.
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?
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.