I have a Ubuntu micro instance with default settings. As a matter of fact, this instance is the same as 8 others I have created prior and since to host Wordpress websites.
This one belongs to a Church, and unfortunately, it keeps having its MySql server going to heaven! I am not sure how to sort this, as the mysql.err log shows:
160301 5:03:40 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in$
160301 5:03:40 [Note] Plugin 'FEDERATED' is disabled.
160301 5:03:40 InnoDB: The InnoDB memory heap is disabled
160301 5:03:40 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160301 5:03:40 InnoDB: Compressed tables use zlib 1.2.8
160301 5:03:40 InnoDB: Using Linux native AIO
160301 5:03:40 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
160301 5:03:40 InnoDB: Completed initialization of buffer pool
160301 5:03:40 InnoDB: Fatal error: cannot allocate memory for the buffer pool
160301 5:03:40 [ERROR] Plugin 'InnoDB' init function returned error.
160301 5:03:40 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
160301 5:03:40 [ERROR] Unknown/unsupported storage engine: InnoDB
160301 5:03:40 [ERROR] Aborting
160301 5:03:40 [Note] /usr/sbin/mysqld: Shutdown complete
This is telling me it could not allocate the 128MB required for the buffer pool.
But, my free -m shows there is plenty of memory for this (I also set up a 2GB swap).
ubuntu#ip-xxx-xxx-xxx-xxx:/var/log/mysql$ free -m
total used free shared buffers cached
Mem: 992 634 358 54 76 308
-/+ buffers/cache: 249 742
Swap: 2047 0 2047
Any suggestions are appreciated!
Looks like there is not enough memory left for allocation during the start process.
add this to your /etc/mysql/my.cnf
innodb_buffer_pool_size = 20M
Related
My disk still has a lot of space, so it's not the memory problem.
Filesystem Size Used Avail Use% Mounted on
/dev/vda1 55G 17G 36G 32% /
Here's the error log
190712 7:55:45 [Warning] Using unique option prefix myisam-recover
instead of myisam-recover-options is deprecated and will be removed in
a future release. Please use the full name instead.
190712 7:55:45 [Note] Plugin 'FEDERATED' is disabled.
190712 7:55:45 InnoDB: The InnoDB memory heap is disabled
190712 7:55:45 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190712 7:55:45 InnoDB: Compressed tables use zlib 1.2.8
190712 7:55:45 InnoDB: Using Linux native AIO
190712 7:55:45 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
190712 7:55:45 InnoDB: Completed initialization of buffer pool
190712 7:55:45 InnoDB: Fatal error: cannot allocate memory for the
buffer pool
190712 7:55:45 [ERROR] Plugin 'InnoDB' init function returned error.
190712 7:55:45 [ERROR] Plugin 'InnoDB' registration as a STORAGE
ENGINE failed.
190712 7:55:45 [ERROR] Unknown/unsupported storage engine: InnoDB
190712 7:55:45 [ERROR] Aborting
190712 7:55:45 [Note] /usr/sbin/mysqld: Shutdown complete
I have to restart MySQL manually
I have problem witch XAMPP. When I try to run MySQL, XAMPP shows this:
12:37:02 [mysql] Error: MySQL shutdown unexpectedly.
12:37:02 [mysql] This may be due to a blocked port, missing dependencies,
12:37:02 [mysql] improper privileges, a crash, or a shutdown by another method.
12:37:02 [mysql] Press the Logs button to view error logs and check
12:37:02 [mysql] the Windows Event Viewer for more clues
12:37:02 [mysql] If you need more help, copy and post this
12:37:02 [mysql] entire log window on the forums
I've changed ports to 3307 in
C:\xampp\mysql\bin\my.ini
and in C:\xampp\php\php.ini to mysql.default_port=3307
mysqli.default_port=3307.
I've also deleted ib_logfile1 in C:\xampp\mysql\data
, but it still doesn't work.
Error logs:
2017-08-17 12:27:00 2050 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.
2017-08-17 12:27:00 8272 [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. `
2017-08-17 12:27:00 8272 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-08-17 12:27:00 8272 [Note] InnoDB: The InnoDB memory heap is disabled
2017-08-17 12:27:00 8272 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-08-17 12:27:00 8272 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-08-17 12:27:00 8272 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-08-17 12:27:00 8272 [Note] InnoDB: Using generic crc32 instructions
2017-08-17 12:27:00 8272 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-08-17 12:27:00 8272 [Note] InnoDB: Completed initialization of buffer pool
2017-08-17 12:27:00 8272 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2017-08-17 12:27:00 8272 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2017-08-17 12:27:00 8272 [ERROR] InnoDB: Cannot create C:\xampp\mysql\data\ib_logfile101
2017-08-17 12:27:00 8272 [ERROR] Plugin 'InnoDB' init function returned error.
2017-08-17 12:27:00 8272 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-08-17 12:27:00 8272 [Note] Plugin 'FEEDBACK' is disabled.
2017-08-17 12:27:00 8272 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-08-17 12:27:00 8272 [ERROR] Aborting
Any help is appreciated. Thanks
MySQL is telling you exactly why it cannot start:
[ERROR] InnoDB: Cannot create C:\xampp\mysql\data\ib_logfile101
Hence I suggest the first thing you do is to check that c:\xampp\mysql\data exists and is writeable by the DBMS user.
First stop the service on the xampp control panel,
then click on the red cross on the left to install the service on your computer,
then the icon will become a green tick,
then start the service as administrator.
It should be working alright.
Open the XAMPP control panel and stop the actions.
Open services and go to MySql80.
Stop the service.
Start the service.
Recently My production server was corrupted due to maintenance shutdown by digital ocean. When we trying to recover our database we couldn't access our droplet. Somehow we managed to recover these (ibdata1, ib_logfile0, ib_logfile1 and some .frm) files. When i copied this files to my new mysql server(in another machine), I could't start the mysql server. I got this output
sudo service mysql restart
mysql stop/waiting
start: Job failed to start
I checked the log file and i got this error,
151019 8:55:27 [Warning] Using unique option prefix myisam-recover instead of $
151019 8:55:27 [Note] Plugin 'FEDERATED' is disabled.
151019 8:55:27 InnoDB: The InnoDB memory heap is disabled
151019 8:55:27 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151019 8:55:27 InnoDB: Compressed tables use zlib 1.2.8
151019 8:55:27 InnoDB: Using Linux native AIO
151019 8:55:27 InnoDB: Initializing buffer pool, size = 128.0M
151019 8:55:27 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 50331648 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
151019 8:55:27 [ERROR] Plugin 'InnoDB' init function returned error.
151019 8:55:27 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151019 8:55:27 [ERROR] Unknown/unsupported storage engine: InnoDB
151019 8:55:27 [ERROR] Aborting
151019 8:55:27 [Note] /usr/sbin/mysqld: Shutdown complete
151019 8:55:28 [Warning] Using unique option prefix myisam-recover instead of $
151019 8:55:28 [Note] Plugin 'FEDERATED' is disabled.
151019 8:55:28 InnoDB: The InnoDB memory heap is disabled
151019 8:55:28 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151019 8:55:28 InnoDB: Compressed tables use zlib 1.2.8
151019 8:55:28 InnoDB: Using Linux native AIO
151019 8:55:28 InnoDB: Initializing buffer pool, size = 128.0M
151019 8:55:28 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 50331648 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
151019 8:55:28 [ERROR] Plugin 'InnoDB' init function returned error.
151019 8:55:28 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151019 8:55:28 [ERROR] Unknown/unsupported storage engine: InnoDB
151019 8:55:28 [ERROR] Aborting
151019 8:55:28 [Note] /usr/sbin/mysqld: Shutdown complete
151019 8:55:29 [Warning] Using unique option prefix myisam-recover instead of $
151019 8:55:29 [Note] Plugin 'FEDERATED' is disabled.
151019 8:55:29 InnoDB: The InnoDB memory heap is disabled
151019 8:55:29 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151019 8:55:29 InnoDB: Compressed tables use zlib 1.2.8
151019 8:55:29 InnoDB: Using Linux native AIO
151019 8:55:29 InnoDB: Initializing buffer pool, size = 128.0M
151019 8:55:29 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 50331648 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
151019 8:55:29 [ERROR] Plugin 'InnoDB' init function returned error.
151019 8:55:29 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151019 8:55:29 [ERROR] Unknown/unsupported storage engine: InnoDB
151019 8:55:29 [ERROR] Aborting
151019 8:55:29 [Note] /usr/sbin/mysqld: Shutdown complete
I tried adding innodb_log_file_size= 50331648 as suggested by #akuzminsky
Then I got this error log.
151022 6:54:13 [Warning] Using unique option prefix myisam-recover instead of $
151022 6:54:13 [Note] Plugin 'FEDERATED' is disabled.
151022 6:54:13 InnoDB: The InnoDB memory heap is disabled
151022 6:54:13 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151022 6:54:13 InnoDB: Compressed tables use zlib 1.2.8
151022 6:54:13 InnoDB: Using Linux native AIO
151022 6:54:13 InnoDB: Initializing buffer pool, size = 128.0M
151022 6:54:13 InnoDB: Completed initialization of buffer pool
151022 6:54:13 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 15379293
151022 6:54:13 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Error: space header page consists of zero bytes in file ./toucan/ormcli$
InnoDB: Error: space header page consists of zero bytes in file ./toucan/catego$
InnoDB: Error: space header page consists of zero bytes in file ./toucan/survey$
InnoDB: Error: space header page consists of zero bytes in file ./toucan/compla$
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 15382291
InnoDB: Page directory corruption: infimum not pointed to
151022 6:54:13 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 10cfd0d80000000000000000000000000000000000e9e915000800000000001$
InnoDB: End of page dump
151022 6:54:13 InnoDB: Page checksum 282054872, prior-to-4.0.14-form checksum$
InnoDB: stored checksum 282054872, prior-to-4.0.14-form stored checksum 3468306$
InnoDB: Page lsn 0 15329557, low 4 bytes of lsn at page end 15329557
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a file space header page
10:54:13 UTC - mysqld got signal 11 ;
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.
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.
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346701 K $
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...
stack_bottom = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x20)[0x7fa4d90e2f10]
/usr/sbin/mysqld(handle_fatal_signal+0x3d5)[0x7fa4d8fcd175]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7fa4d7d5d340]
/usr/sbin/mysqld(+0x5f058a)[0x7fa4d91e258a]
/usr/sbin/mysqld(+0x56c44e)[0x7fa4d915e44e]
/usr/sbin/mysqld(+0x576137)[0x7fa4d9168137]
/usr/sbin/mysqld(+0x5a5632)[0x7fa4d9197632]
/usr/sbin/mysqld(+0x5a6699)[0x7fa4d9198699]
/usr/sbin/mysqld(+0x591ad3)[0x7fa4d9183ad3]
/usr/sbin/mysqld(+0x542a1a)[0x7fa4d9134a1a]
/usr/sbin/mysqld(+0x511d48)[0x7fa4d9103d48]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x7fa4d8fcf$
/usr/sbin/mysqld(+0x302221)[0x7fa4d8ef4221]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x92a)[0x7fa4d8ef821a]
/usr/sbin/mysqld(+0x28ac5b)[0x7fa4d8e7cc5b]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x45b)[0x7fa4d8e815db]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fa4d739fec5]
/usr/sbin/mysqld(+0x286b18)[0x7fa4d8e78b18]
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.
Please help me to resolve this.
Thanks in advance.
Note lines in the error log:
InnoDB: Error: log file ./ib_logfile0 is of different size 0 50331648 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
The actual size of the redo log file differs from the size in MySQL config.
Add this line to my.cnf
innodb_log_file_size= 50331648
If the tablespace is corrupted you'll still have to heal it. But at least MySQL won't stop at this step.
Hi all I have ubuntu installed on my server with apache2 and mysql; every now and then I get this message:
Warning: mysql_connect(): [2002] Connection refused
(trying to connect via unix:///var/run/mysqld/mysqld.sock) in /var/www/fanta-trade/wp-includes/wp-db.php on line 1142
Warning: mysql_connect(): Connection refused in /var/www/fanta-trade/wp-includes/wp-db.php on line 1142`
I do not think is a script error because if I restart apache it starts working again. How can I solve it?
I add also the mysql log:
150719 11:05:52 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
150719 11:05:52 [Note] Plugin 'FEDERATED' is disabled.
150719 11:05:52 InnoDB: The InnoDB memory heap is disabled
150719 11:05:52 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150719 11:05:52 InnoDB: Compressed tables use zlib 1.2.3.4
150719 11:05:52 InnoDB: Initializing buffer pool, size = 16.0M
InnoDB: mmap(17170432 bytes) failed; errno 12
150719 11:05:52 InnoDB: Completed initialization of buffer pool
150719 11:05:52 InnoDB: Fatal error: cannot allocate memory for the buffer pool
150719 11:05:52 [ERROR] Plugin 'InnoDB' init function returned error.
150719 11:05:52 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
150719 11:05:53 [ERROR] Unknown/unsupported storage engine: InnoDB
150719 11:05:53 [ERROR] Aborting
i setted
innodb_buffer_pool_size = 38M
I have a VPS, and today, the mysql service stopped, the error is
140821 2:35:21 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
140821 2:35:21 [Note] Plugin 'FEDERATED' is disabled.
140821 2:35:21 InnoDB: The InnoDB memory heap is disabled
140821 2:35:21 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140821 2:35:21 InnoDB: Compressed tables use zlib 1.2.8
140821 2:35:21 InnoDB: Using Linux native AIO
140821 2:35:21 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
140821 2:35:21 InnoDB: Completed initialization of buffer pool
140821 2:35:21 InnoDB: Fatal error: cannot allocate memory for the buffer pool
140821 2:35:21 [ERROR] Plugin 'InnoDB' init function returned error.
140821 2:35:21 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
140821 2:35:21 [ERROR] Unknown/unsupported storage engine: InnoDB
140821 2:35:21 [ERROR] Aborting
140821 2:35:21 [Note] /usr/sbin/mysqld: Shutdown complete
140821 2:35:22 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
140821 2:35:22 [Note] Plugin 'FEDERATED' is disabled.
140821 2:35:22 InnoDB: The InnoDB memory heap is disabled
140821 2:35:22 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140821 2:35:22 InnoDB: Compressed tables use zlib 1.2.8
140821 2:35:22 InnoDB: Using Linux native AIO
140821 2:35:22 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
140821 2:35:22 InnoDB: Completed initialization of buffer pool
140821 2:35:22 InnoDB: Fatal error: cannot allocate memory for the buffer pool
140821 2:35:22 [ERROR] Plugin 'InnoDB' init function returned error.
140821 2:35:22 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
140821 2:35:22 [ERROR] Unknown/unsupported storage engine: InnoDB
140821 2:35:22 [ERROR] Aborting
140821 2:35:22 [Note] /usr/sbin/mysqld: Shutdown complete
Any explanation for this?
Error arises because of your memory allocation limit. It can be referred to as an Out of memory exception. It can arise again in case of high memory usage.
As you can see, the InnoDB buffer pool size is set to 128MB.
Change your buffer pool size to avoid the error again;
add this to your my.cnf
innodb_buffer_pool_size=1G
restart your mysql to make it effect