InnoDB crashes frequently - mysql

My Innodb Engine is getting crashed frequently.
I could not find the reason behind this.
This is the error log:
140129 9:22:49 [Note] Plugin 'FEDERATED' is disabled.
140129 9:22:49 InnoDB: The InnoDB memory heap is disabled
140129 9:22:49 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140129 9:22:49 InnoDB: Compressed tables use zlib 1.2.3.4
140129 9:22:50 InnoDB: Initializing buffer pool, size = 128.0M
140129 9:22:50 InnoDB: Completed initialization of buffer pool
140129 9:22:50 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 275341002
140129 9:22:50 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...
InnoDB: Doing recovery: scanned up to log sequence number 275341421
InnoDB: 3 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 15 row operations to undo
InnoDB: Trx id counter is 294A00
140129 9:22:51 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Starting in background the rollback of uncommitted transactions
140129 9:22:51 InnoDB: Rolling back trx with id 2948FA, 6 rows to undo
140129 9:22:51 InnoDB: Waiting for the background threads to start
InnoDB: Rolling back of trx id 2948FA completed
140129 9:22:51 InnoDB: Rolling back trx with id 2948F9, 5 rows to undo
InnoDB: Rolling back of trx id 2948F9 completed
140129 9:22:51 InnoDB: Rolling back trx with id 2948D6, 4 rows to undo
InnoDB: Rolling back of trx id 2948D6 completed
140129 9:22:51 InnoDB: Rollback of non-prepared transactions completed
140129 9:22:52 InnoDB: 1.1.8 started; log sequence number 275341421
140129 9:22:52 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
140129 9:22:52 [Note] - '0.0.0.0' resolves to '0.0.0.0';
140129 9:22:52 [Note] Server socket created on IP: '0.0.0.0'.
140129 9:22:52 [ERROR] /usr/sbin/mysqld: Table './mysql/user' is marked as crashed and should be repaired
140129 9:22:52 [Warning] Checking table: './mysql/user'
140129 9:22:52 [ERROR] 1 client is using or hasn't closed the table properly
140129 9:22:52 [Note] Event Scheduler: Loaded 0 events
140129 9:22:52 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.5.29-0ubuntu0.12.04.2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
140129 9:22:56 [ERROR] /usr/sbin/mysqld: Table './sarojini/wp_options' is marked as crashed and should be repaired
140129 9:22:56 [Warning] Checking table: './sarojini/wp_options'
140129 9:22:57 [ERROR] /usr/sbin/mysqld: Table './sysvine/wp_sysvinewpoptions' is marked as crashed and should be repaired
140129 9:22:57 [Warning] Checking table: './sysvine/wp_sysvinewpoptions'
140129 13:00:37 [Note] /usr/sbin/mysqld: Normal shutdown
140129 13:00:37 [Note] Event Scheduler: Purging the queue. 0 events'
140129 13:00:39 InnoDB: Starting shutdown...
140129 13:00:40 InnoDB: Waiting for 20 pages to be flushed
140129 13:00:40 InnoDB: Shutdown completed; log sequence number 277454104
140129 13:00:41 [Note] /usr/sbin/mysqld: Shutdown complete
140129 13:01:52 [Note] Plugin 'FEDERATED' is disabled.
140129 13:01:52 InnoDB: The InnoDB memory heap is disabled
140129 13:01:52 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140129 13:01:52 InnoDB: Compressed tables use zlib 1.2.3.4
140129 13:01:52 InnoDB: Initializing buffer pool, size = 128.0M
140129 13:01:53 InnoDB: Completed initialization of buffer pool
140129 13:01:53 InnoDB: highest supported file format is Barracuda.
140129 13:01:53 InnoDB: Waiting for the background threads to start
140129 13:01:54 InnoDB: 1.1.8 started; log sequence number 277454104
140129 13:01:54 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
140129 13:01:54 [Note] - '0.0.0.0' resolves to '0.0.0.0';
140129 13:01:54 [Note] Server socket created on IP: '0.0.0.0'.
140129 13:01:55 [Note] Event Scheduler: Loaded 0 events
140129 13:01:55 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.5.29-0ubuntu0.12.04.2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
140129 13:19:51 [Note] /usr/sbin/mysqld: Normal shutdown
140129 13:19:51 [Note] Event Scheduler: Purging the queue. 0 events
140129 13:19:53 [Warning] /usr/sbin/mysqld: Forcing close of thread 105 user: 'redmine'
140129 13:19:53 InnoDB: Starting shutdown...
140129 13:19:54 InnoDB: Shutdown completed; log sequence number 277619754
140129 13:19:54 [Note] /usr/sbin/mysqld: Shutdown complete
Can anybody help me to stop this unwanted Innodb crash.
Thanks in Advance...

The log indicates that MySQL was not shut down properly, but that it recovered just fine (at 9:22:52). It was later shut down properly (at 13:00:37 and 13:19:51). What makes you think that it is crashing?

There was a crash, and then there was a normal shutdown.
Probably it allocates too much memory. Probably SELinux, or App Armor, shutdown MySQL.

Related

ERROR 2006 (HY000): MySQL server has gone away (In some cases)

I have a problem: I can't do anything in a database.
It will return the following directly to me when any action is currently performed, But this error seems to be only targeted at one of my databases:
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id: 8
Current database: gomeet
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/home/mysql/software/mysql.sock' (111)
ERROR:
Can't connect to the server
It seems that I send any instruction in the gomeet database and dataserver.err will return me a similar error:
InnoDB: Error: trying to access page number 0 in space 3090,
InnoDB: space name gomeet/api_worker_face_back,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
2021-05-18 17:04:07 7f0fe3206700 InnoDB: Assertion failure in thread 139706211788544 in file fil0fil.cc line 5603
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
09:04:07 UTC - mysqld got signal 6 ;
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=8388608
read_buffer_size=131072
max_used_connections=40
max_threads=1500
thread_count=40
connection_count=40
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 604688 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x177301d0
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 = 7f0fe3205ea0 thread_stack 0x40000
/home/mysql/software/bin/mysqld(my_print_stacktrace+0x2c)[0x8f016c]
/home/mysql/software/bin/mysqld(handle_fatal_signal+0x364)[0x66cb64]
/lib64/libpthread.so.0(+0xf5f0)[0x7f13417d25f0]
/lib64/libc.so.6(gsignal+0x37)[0x7f13407d1337]
/lib64/libc.so.6(abort+0x148)[0x7f13407d2a28]
/home/mysql/software/bin/mysqld[0xaa1074]
/home/mysql/software/bin/mysqld[0xa6d899]
/home/mysql/software/bin/mysqld[0xa565b1]
/home/mysql/software/bin/mysqld[0xa3e751]
/home/mysql/software/bin/mysqld[0x9ee9b6]
/home/mysql/software/bin/mysqld[0x952b18]
/home/mysql/software/bin/mysqld[0x959e20]
/home/mysql/software/bin/mysqld(_ZN7handler7ha_openEP5TABLEPKcii+0x33)[0x5aa5c3]
/home/mysql/software/bin/mysqld(_Z21open_table_from_shareP3THDP11TABLE_SHAREPKcjjjP5TABLEb+0x61c)[0x7705cc]
/home/mysql/software/bin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP18Open_table_context+0xc8b)[0x69fc0b]
/home/mysql/software/bin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0x839)[0x6a7d09]
/home/mysql/software/bin/mysqld(_Z30open_normal_and_derived_tablesP3THDP10TABLE_LISTj+0x4a)[0x6a878a]
/home/mysql/software/bin/mysqld(_Z18mysqld_list_fieldsP3THDP10TABLE_LISTPKc+0x25)[0x7222d5]
/home/mysql/software/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x2103)[0x6f66f3]
/home/mysql/software/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x1ed)[0x6be7dd]
/home/mysql/software/bin/mysqld(handle_one_connection+0x39)[0x6be829]
/home/mysql/software/bin/mysqld(pfs_spawn_thread+0x140)[0x9374d0]
/lib64/libpthread.so.0(+0x7e65)[0x7f13417cae65]
/lib64/libc.so.6(clone+0x6d)[0x7f134089988d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f0f6000c078): is an invalid pointer
Connection ID (thread ID): 21
Status: NOT_KILLED
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.
210518 17:04:07 mysqld_safe Number of processes running now: 0
210518 17:04:07 mysqld_safe mysqld restarted
2021-05-18 17:04:07 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2021-05-18 17:04:07 3479 [Note] Plugin 'FEDERATED' is disabled.
2021-05-18 17:04:07 3479 [Note] InnoDB: Using atomics to ref count buffer pool pages
2021-05-18 17:04:07 3479 [Note] InnoDB: The InnoDB memory heap is disabled
2021-05-18 17:04:07 3479 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-05-18 17:04:07 3479 [Note] InnoDB: Compressed tables use zlib 1.2.3
2021-05-18 17:04:07 3479 [Note] InnoDB: Using CPU crc32 instructions
2021-05-18 17:04:07 3479 [Note] InnoDB: Initializing buffer pool, size = 12.0G
2021-05-18 17:04:08 3479 [Note] InnoDB: Completed initialization of buffer pool
2021-05-18 17:04:08 3479 [Note] InnoDB: Highest supported file format is Barracuda.
2021-05-18 17:04:08 3479 [Note] InnoDB: Log scan progressed past the checkpoint lsn 474510929998
2021-05-18 17:04:08 3479 [Note] InnoDB: Database was not shutdown normally!
2021-05-18 17:04:08 3479 [Note] InnoDB: Starting crash recovery.
2021-05-18 17:04:08 3479 [Note] InnoDB: Reading tablespace information from the .ibd files...
2021-05-18 17:04:08 3479 [Note] InnoDB: Restoring possible half-written data pages
2021-05-18 17:04:08 3479 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 474516172800
InnoDB: Doing recovery: scanned up to log sequence number 474519100469
2021-05-18 17:04:08 3479 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 8103845, file name mysql-bin.002311
2021-05-18 17:04:09 3479 [Note] InnoDB: 128 rollback segment(s) are active.
2021-05-18 17:04:10 3479 [Note] InnoDB: Waiting for purge to start
2021-05-18 17:04:10 3479 [Note] InnoDB: 5.6.16 started; log sequence number 474519100469
2021-05-18 17:04:10 3479 [Note] Recovering after a crash using mysql-bin
2021-05-18 17:04:10 3479 [Note] Starting crash recovery...
2021-05-18 17:04:10 3479 [Note] Crash recovery finished.
2021-05-18 17:04:10 3479 [Note] Server hostname (bind-address): '*'; port: 3306
2021-05-18 17:04:10 3479 [Note] IPv6 is available.
2021-05-18 17:04:10 3479 [Note] - '::' resolves to '::';
2021-05-18 17:04:10 3479 [Note] Server socket created on IP: '::'.
2021-05-18 17:04:10 3479 [Note] Event Scheduler: Loaded 0 events
2021-05-18 17:04:10 3479 [Note] /home/mysql/software/bin/mysqld: ready for connections.
Version: '5.6.16-log' socket: '/home/mysql/software/mysql.sock' port: 3306 Source distribution
my.cnf:
[mysqld]
# Remove leading # and set to the amount of RAM for the most important data
# cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%.
innodb_buffer_pool_size = 12G
#innodb_additional_mem_pool_size=128M
# Remove leading # to turn on a very important data integrity option: logging
# changes to the binary log between backups.
# log_bin
# These are commonly set, remove the # and set as required.
# basedir = .....
datadir = /home/mysql/mysqldb
# port = .....
server_id = 94
log-bin=mysql-bin
expire_logs_days = 60
binlog-do-db=gomeet
binlog-do-db=gomeetLog
binlog_format=mixed
#innodb_file_per_table=1
#thread_concurrency=8
back_log=600
#innodb_force_recovery = 1
#innodb_file_format=Barracuda
#innodb_log_file_size=1024M
#innodb_strict_mode=0
#innodb_page_size=32K
#sort_buffer_size=8M
#read_buffer_size=8M
#read_rnd_buffer_size=8M
#table_open_cache=2048
max_allowed_packet=64M
#tmp_table_size=2G
#innodb_log_file_size=148M
# socket = .....
max_connections=1500
wait_timeout = 600
interactive_timeout = 600
# Remove leading # to set options mainly useful for reporting servers.
# The server defaults are faster for transactions and fast SELECTs.
# Adjust sizes as needed, experiment to find the optimal values# join_buffer_size = 128M
# join_buffer_size = 8M
# read_rnd_buffer_size = 2M
sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES
If I operate in the program api_worker_face_back MySQL will be triggered to restart once.
2021-05-18 03:16:10 5328 [ERROR] InnoDB: The OS said file flush did not succeed
2021-05-18 03:16:10 7f6a83305700 InnoDB: Operating system error number 5 in a file operation.
InnoDB: Error number 5 means 'Input/output error'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2021-05-18 03:16:10 5328 [ERROR] InnoDB: File (unknown): 'flush' returned OS error 105. Cannot continue operation
210518 03:16:11 mysqld_safe Number of processes running now: 0
210518 03:16:11 mysqld_safe mysqld restarted
2021-05-18 03:16:11 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2021-05-18 03:16:11 5389 [Note] Plugin 'FEDERATED' is disabled.
2021-05-18 03:16:11 7f2d6eefe740 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.
2021-05-18 03:16:11 5389 [Note] InnoDB: Using atomics to ref count buffer pool pages
2021-05-18 03:16:11 5389 [Note] InnoDB: The InnoDB memory heap is disabled
2021-05-18 03:16:11 5389 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-05-18 03:16:11 5389 [Note] InnoDB: Compressed tables use zlib 1.2.3
2021-05-18 03:16:11 5389 [Note] InnoDB: Using CPU crc32 instructions
2021-05-18 03:16:11 5389 [Note] InnoDB: Initializing buffer pool, size = 12.0G
2021-05-18 03:16:11 5389 [Note] InnoDB: Completed initialization of buffer pool
2021-05-18 03:16:11 5389 [Note] InnoDB: Highest supported file format is Barracuda.
2021-05-18 03:16:11 5389 [Note] InnoDB: Log scan progressed past the checkpoint lsn 474072587915
2021-05-18 03:16:11 5389 [Note] InnoDB: Database was not shutdown normally!
2021-05-18 03:16:11 5389 [Note] InnoDB: Starting crash recovery.
2021-05-18 03:16:11 5389 [Note] InnoDB: Reading tablespace information from the .ibd files...
2021-05-18 03:16:11 5389 [Note] InnoDB: Restoring possible half-written data pages
2021-05-18 03:16:11 5389 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 474077830656
InnoDB: Doing recovery: scanned up to log sequence number 474083073536
InnoDB: Doing recovery: scanned up to log sequence number 474084218025
InnoDB: Transaction 7266397060 was in the XA prepared state.
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 0 row operations to undo
InnoDB: Trx id counter is 7266397440
2021-05-18 03:16:11 5389 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 8891015, file name mysql-bin.000851
2021-05-18 03:16:13 5389 [Note] InnoDB: 128 rollback segment(s) are active.
InnoDB: Starting in background the rollback of uncommitted transactions
2021-05-18 03:16:13 7f2a0da01700 InnoDB: Rollback of non-prepared transactions completed
2021-05-18 03:16:13 5389 [Note] InnoDB: Waiting for purge to start
2021-05-18 03:16:13 5389 [Note] InnoDB: 5.6.16 started; log sequence number 474084218025
2021-05-18 03:16:13 5389 [Note] Recovering after a crash using mysql-bin
2021-05-18 03:16:13 5389 [Note] Starting crash recovery...
2021-05-18 03:16:13 7f2d6eefe740 InnoDB: Starting recovery for XA transactions...
2021-05-18 03:16:13 7f2d6eefe740 InnoDB: Transaction 7266397060 in prepared state after recovery
2021-05-18 03:16:13 7f2d6eefe740 InnoDB: Transaction contains changes to 1 rows
2021-05-18 03:16:13 7f2d6eefe740 InnoDB: 1 transactions in prepared state after recovery
2021-05-18 03:16:13 5389 [Note] Found 1 prepared transaction(s) in InnoDB
2021-05-18 03:16:13 5389 [Note] Crash recovery finished.
2021-05-18 03:16:13 5389 [Note] Server hostname (bind-address): '*'; port: 3306
2021-05-18 03:16:13 5389 [Note] IPv6 is available.
2021-05-18 03:16:13 5389 [Note] - '::' resolves to '::';
2021-05-18 03:16:13 5389 [Note] Server socket created on IP: '::'.
2021-05-18 03:16:13 5389 [Note] Event Scheduler: Loaded 0 events
2021-05-18 03:16:13 5389 [Note] /home/mysql/software/bin/mysqld: ready for connections.
Version: '5.6.16-log' socket: '/home/mysql/software/mysql.sock' port: 3306 Source distribution
max_allowed_packet=64M
Adding this line into my.cnf file solves your problem.
This is useful when the columns have large values, which cause the issues, you can find the explanation here.
On Windows this file is located at: "C:\ProgramData\MySQL\MySQL Server 5.6"
On Linux (Ubuntu): /etc/mysql
Check this out: https://dev.mysql.com/doc/refman/8.0/en/replication-features-max-allowed-packet.html

MySQL unexpectedly crashes

I'm running Ubuntu 14.04 and I've got a few WordPress installations on my server.
Without warning, MySQL crashes every day on my server and I've yet to find the reason.
You can find the error.log below.
160721 9:25:44 [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.
160721 9:25:44 [Note] Plugin 'FEDERATED' is disabled.
160721 9:25:44 InnoDB: The InnoDB memory heap is disabled
160721 9:25:44 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160721 9:25:44 InnoDB: Compressed tables use zlib 1.2.8
160721 9:25:44 InnoDB: Using Linux native AIO
160721 9:25:44 InnoDB: Initializing buffer pool, size = 128.0M
160721 9:25:44 InnoDB: Completed initialization of buffer pool
160721 9:25:44 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 40817296
160721 9:25:44 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...
InnoDB: Doing recovery: scanned up to log sequence number 41068976
160721 9:25:45 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
160721 9:25:45 InnoDB: Waiting for the background threads to start
160721 9:25:46 InnoDB: 5.5.47 started; log sequence number 41068976
160721 9:25:46 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
160721 9:25:46 [Note] - '127.0.0.1' resolves to '127.0.0.1';
160721 9:25:46 [Note] Server socket created on IP: '127.0.0.1'.
160721 9:25:46 [Note] Event Scheduler: Loaded 0 events
160721 9:25:46 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.47-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
160721 17:50:13 [Note] /usr/sbin/mysqld: Normal shutdown
160721 17:50:13 [Note] Event Scheduler: Purging the queue. 0 events
160721 17:50:13 InnoDB: Starting shutdown...
160721 17:50:14 InnoDB: Shutdown completed; log sequence number 41400934
160721 17:50:14 [Note] /usr/sbin/mysqld: Shutdown complete
160721 17:50:15 [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.
160721 17:50:15 [Note] Plugin 'FEDERATED' is disabled.
160721 17:50:15 InnoDB: The InnoDB memory heap is disabled
160721 17:50:15 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160721 17:50:15 InnoDB: Compressed tables use zlib 1.2.8
160721 17:50:15 InnoDB: Using Linux native AIO
160721 17:50:15 InnoDB: Initializing buffer pool, size = 128.0M
160721 17:50:15 InnoDB: Completed initialization of buffer pool
160721 17:50:15 InnoDB: highest supported file format is Barracuda.
160721 17:50:15 InnoDB: Waiting for the background threads to start
160721 17:50:16 InnoDB: 5.5.47 started; log sequence number 41400934
160721 17:50:16 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
160721 17:50:16 [Note] - '127.0.0.1' resolves to '127.0.0.1';
160721 17:50:16 [Note] Server socket created on IP: '127.0.0.1'.
160721 17:50:16 [Note] Event Scheduler: Loaded 0 events
160721 17:50:16 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.47-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
160722 5:44:00 [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.
160722 5:44:00 [Note] Plugin 'FEDERATED' is disabled.
160722 5:44:00 InnoDB: The InnoDB memory heap is disabled
160722 5:44:00 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160722 5:44:00 InnoDB: Compressed tables use zlib 1.2.8
160722 5:44:00 InnoDB: Using Linux native AIO
160722 5:44:00 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
160722 5:44:00 InnoDB: Completed initialization of buffer pool
160722 5:44:00 InnoDB: Fatal error: cannot allocate memory for the buffer pool
160722 5:44:00 [ERROR] Plugin 'InnoDB' init function returned error.
160722 5:44:00 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
160722 5:44:00 [ERROR] Unknown/unsupported storage engine: InnoDB
160722 5:44:00 [ERROR] Aborting
160722 5:44:00 [Note] /usr/sbin/mysqld: Shutdown complete
160722 5:44:01 [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.
160722 5:44:01 [Note] Plugin 'FEDERATED' is disabled.
160722 5:44:01 InnoDB: The InnoDB memory heap is disabled
160722 5:44:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160722 5:44:01 InnoDB: Compressed tables use zlib 1.2.8
160722 5:44:01 InnoDB: Using Linux native AIO
160722 5:44:01 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
160722 5:44:01 InnoDB: Completed initialization of buffer pool
160722 5:44:01 InnoDB: Fatal error: cannot allocate memory for the buffer pool
160722 5:44:01 [ERROR] Plugin 'InnoDB' init function returned error.
160722 5:44:01 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
160722 5:44:01 [ERROR] Unknown/unsupported storage engine: InnoDB
160722 5:44:01 [ERROR] Aborting
160722 5:44:01 [Note] /usr/sbin/mysqld: Shutdown complete
160722 5:50:30 [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.
160722 5:50:30 [Note] Plugin 'FEDERATED' is disabled.
160722 5:50:30 InnoDB: The InnoDB memory heap is disabled
160722 5:50:30 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160722 5:50:30 InnoDB: Compressed tables use zlib 1.2.8
160722 5:50:30 InnoDB: Using Linux native AIO
160722 5:50:30 InnoDB: Initializing buffer pool, size = 128.0M
160722 5:50:30 InnoDB: Completed initialization of buffer pool
160722 5:50:31 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 41616363
160722 5:50:31 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...
InnoDB: Doing recovery: scanned up to log sequence number 46858752
InnoDB: Doing recovery: scanned up to log sequence number 48741839
160722 5:50:31 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
160722 5:50:32 InnoDB: Waiting for the background threads to start
160722 5:50:33 InnoDB: 5.5.47 started; log sequence number 48741839
160722 5:50:33 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
160722 5:50:33 [Note] - '127.0.0.1' resolves to '127.0.0.1';
160722 5:50:33 [Note] Server socket created on IP: '127.0.0.1'.
160722 5:50:33 [Note] Event Scheduler: Loaded 0 events
160722 5:50:33 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.47-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306
InnoDB: mmap(137363456 bytes) failed; errno 12
Case 1: You have a tiny 1G server (or VM). If so, lower innodb_buffer_pool_size to, say, 32M.
Case 2: You have increased various other mysql settings to unreasonably high values. Undo.
Case 3: You have lots of applications in your small server; they are consuming most of RAM. Find and fix.
If you need further assistance, tell us how much RAM you have, what else is running and provide my.cnf.
Or you could get more RAM.

MySQL 5.6 crashes often after upgrade

I noticed in WHM that MySQL 5.5 has an EOL December of 15' and I upgraded to 5.6 and now MySQL crashes at least twice a day, but it restarts after failing.
Here is a sampling of the error log.
Any idea what is going on?
Thank you.
8/23/15
Here is another sampling of the error log.
InnoDB: Doing recovery: scanned up to log sequence number 579981897
2015-08-21 20:58:00 9080 [Note] InnoDB: 128 rollback segment(s) are active.
2015-08-21 20:58:00 9080 [Note] InnoDB: Waiting for purge to start
2015-08-21 20:58:00 9080 [Note] InnoDB: 5.6.23 started; log sequence number 579981897
2015-08-21 20:58:00 9080 [Note] Server hostname (bind-address): '*'; port: 3306
2015-08-21 20:58:00 9080 [Note] IPv6 is not available.
2015-08-21 20:58:00 9080 [Note] - '0.0.0.0' resolves to '0.0.0.0';
2015-08-21 20:58:00 9080 [Note] Server socket created on IP: '0.0.0.0'.
2015-08-21 20:58:00 9080 [Note] Event Scheduler: Loaded 0 events
2015-08-21 20:58:00 9080 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.6.23' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
150821 23:25:59 mysqld_safe Number of processes running now: 0
150821 23:25:59 mysqld_safe mysqld restarted
2015-08-21 23:25:59 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-08-21 23:25:59 13544 [Note] Plugin 'FEDERATED' is disabled.
2015-08-21 23:25:59 13544 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-08-21 23:25:59 13544 [Note] InnoDB: The InnoDB memory heap is disabled
2015-08-21 23:25:59 13544 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-08-21 23:25:59 13544 [Note] InnoDB: Memory barrier is not used
2015-08-21 23:25:59 13544 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-08-21 23:25:59 13544 [Note] InnoDB: Using Linux native AIO
2015-08-21 23:25:59 13544 [Note] InnoDB: Using CPU crc32 instructions
2015-08-21 23:25:59 13544 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-08-21 23:25:59 13544 [Note] InnoDB: Completed initialization of buffer pool
2015-08-21 23:25:59 13544 [Note] InnoDB: Highest supported file format is Barracuda.
2015-08-21 23:25:59 13544 [Note] InnoDB: Log scan progressed past the checkpoint lsn 581241150
2015-08-21 23:25:59 13544 [Note] InnoDB: Database was not shutdown normally!
2015-08-21 23:25:59 13544 [Note] InnoDB: Starting crash recovery.
2015-08-21 23:25:59 13544 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-08-21 23:25:59 13544 [Note] InnoDB: Restoring possible half-written data pages
2015-08-21 23:25:59 13544 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 581282693
2015-08-21 23:25:59 13544 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
2015-08-21 23:26:00 13544 [Note] InnoDB: 128 rollback segment(s) are active.
2015-08-21 23:26:00 13544 [Note] InnoDB: Waiting for purge to start
2015-08-21 23:26:00 13544 [Note] InnoDB: 5.6.23 started; log sequence number 581282693
2015-08-21 23:26:00 13544 [Note] Server hostname (bind-address): '*'; port: 3306
2015-08-21 23:26:00 13544 [Note] IPv6 is not available.
2015-08-21 23:26:00 13544 [Note] - '0.0.0.0' resolves to '0.0.0.0';
2015-08-21 23:26:00 13544 [Note] Server socket created on IP: '0.0.0.0'.
2015-08-21 23:26:00 13544 [Note] Event Scheduler: Loaded 0 events
2015-08-21 23:26:00 13544 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.6.23' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
2015-08-22 02:36:21 13544 [Warning] IP address '223.100.49.242' could not be resolved: Temporary failure in name resolution
2015-08-22 02:36:56 13544 [Warning] IP address '223.100.49.242' could not be resolved: Temporary failure in name resolution
2015-08-22 02:37:23 13544 [Warning] IP address '223.100.49.242' could not be resolved: Temporary failure in name resolution
2015-08-22 11:27:54 13544 [Warning] IP address '122.224.6.150' could not be resolved: Name or service not known
150822 20:54:11 mysqld_safe Number of processes running now: 0
150822 20:54:11 mysqld_safe mysqld restarted
2015-08-22 20:54:11 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-08-22 20:54:11 15947 [Note] Plugin 'FEDERATED' is disabled.
2015-08-22 20:54:11 15947 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-08-22 20:54:11 15947 [Note] InnoDB: The InnoDB memory heap is disabled
2015-08-22 20:54:11 15947 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-08-22 20:54:11 15947 [Note] InnoDB: Memory barrier is not used
2015-08-22 20:54:11 15947 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-08-22 20:54:11 15947 [Note] InnoDB: Using Linux native AIO
2015-08-22 20:54:11 15947 [Note] InnoDB: Using CPU crc32 instructions
2015-08-22 20:54:11 15947 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-08-22 20:54:11 15947 [Note] InnoDB: Completed initialization of buffer pool
2015-08-22 20:54:11 15947 [Note] InnoDB: Highest supported file format is Barracuda.
2015-08-22 20:54:11 15947 [Note] InnoDB: The log sequence numbers 506046855 and 506046855 in ibdata files do not match the log sequence number 589358444 in the ib_logfiles!
2015-08-22 20:54:11 15947 [Note] InnoDB: Database was not shutdown normally!
2015-08-22 20:54:11 15947 [Note] InnoDB: Starting crash recovery.
2015-08-22 20:54:11 15947 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-08-22 20:54:12 15947 [Note] InnoDB: Restoring possible half-written data pages
2015-08-22 20:54:12 15947 [Note] InnoDB: from the doublewrite buffer...
2015-08-22 20:54:13 15947 [Note] InnoDB: 128 rollback segment(s) are active.
2015-08-22 20:54:13 15947 [Note] InnoDB: Waiting for purge to start
2015-08-22 20:54:13 15947 [Note] InnoDB: 5.6.23 started; log sequence number 589358444
2015-08-22 20:54:13 15947 [Note] Server hostname (bind-address): '*'; port: 3306
2015-08-22 20:54:13 15947 [Note] IPv6 is not available.
2015-08-22 20:54:13 15947 [Note] - '0.0.0.0' resolves to '0.0.0.0';
2015-08-22 20:54:13 15947 [Note] Server socket created on IP: '0.0.0.0'.
2015-08-22 20:54:13 15947 [Note] Event Scheduler: Loaded 0 events
2015-08-22 20:54:13 15947 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.6.23' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
150822 20:54:13 mysqld_safe Number of processes running now: 0
150822 20:54:13 mysqld_safe mysqld restarted
2015-08-22 20:54:13 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-08-22 20:54:13 15983 [Note] Plugin 'FEDERATED' is disabled.
2015-08-22 20:54:13 15983 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-08-22 20:54:13 15983 [Note] InnoDB: The InnoDB memory heap is disabled
2015-08-22 20:54:13 15983 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-08-22 20:54:13 15983 [Note] InnoDB: Memory barrier is not used
2015-08-22 20:54:13 15983 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-08-22 20:54:13 15983 [Note] InnoDB: Using Linux native AIO
2015-08-22 20:54:13 15983 [Note] InnoDB: Using CPU crc32 instructions
2015-08-22 20:54:13 15983 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-08-22 20:54:13 15983 [Note] InnoDB: Completed initialization of buffer pool
2015-08-22 20:54:13 15983 [Note] InnoDB: Highest supported file format is Barracuda.
2015-08-22 20:54:13 15983 [Note] InnoDB: The log sequence numbers 506046855 and 506046855 in ibdata files do not match the log sequence number 589358444 in the ib_logfiles!
2015-08-22 20:54:13 15983 [Note] InnoDB: Database was not shutdown normally!
2015-08-22 20:54:13 15983 [Note] InnoDB: Starting crash recovery.
2015-08-22 20:54:13 15983 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-08-22 20:54:13 15983 [Note] InnoDB: Restoring possible half-written data pages
2015-08-22 20:54:13 15983 [Note] InnoDB: from the doublewrite buffer...
2015-08-22 20:54:14 15983 [Note] InnoDB: 128 rollback segment(s) are active.
2015-08-22 20:54:14 15983 [Note] InnoDB: Waiting for purge to start
2015-08-22 20:54:14 15983 [Note] InnoDB: 5.6.23 started; log sequence number 589358444
2015-08-22 20:54:14 15983 [Note] Server hostname (bind-address): '*'; port: 3306
2015-08-22 20:54:14 15983 [Note] IPv6 is not available.
2015-08-22 20:54:14 15983 [Note] - '0.0.0.0' resolves to '0.0.0.0';
2015-08-22 20:54:14 15983 [Note] Server socket created on IP: '0.0.0.0'.
2015-08-22 20:54:14 15983 [Note] Event Scheduler: Loaded 0 events
2015-08-22 20:54:14 15983 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.6.23' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
2015-08-22 21:28:15 15983 [Warning] IP address '221.229.162.143' could not be resolved: Name or service not known
150822 23:04:56 mysqld_safe Number of processes running now: 0
150822 23:04:56 mysqld_safe mysqld restarted
2015-08-22 23:04:56 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-08-22 23:04:56 19131 [Note] Plugin 'FEDERATED' is disabled.
2015-08-22 23:04:56 19131 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-08-22 23:04:56 19131 [Note] InnoDB: The InnoDB memory heap is disabled
2015-08-22 23:04:56 19131 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-08-22 23:04:56 19131 [Note] InnoDB: Memory barrier is not used
2015-08-22 23:04:56 19131 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-08-22 23:04:56 19131 [Note] InnoDB: Using Linux native AIO
2015-08-22 23:04:56 19131 [Note] InnoDB: Using CPU crc32 instructions
2015-08-22 23:04:56 19131 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-08-22 23:04:57 19131 [Note] InnoDB: Completed initialization of buffer pool
2015-08-22 23:04:57 19131 [Note] InnoDB: Highest supported file format is Barracuda.
2015-08-22 23:04:57 19131 [Note] InnoDB: Log scan progressed past the checkpoint lsn 590358682
2015-08-22 23:04:57 19131 [Note] InnoDB: Database was not shutdown normally!
2015-08-22 23:04:57 19131 [Note] InnoDB: Starting crash recovery.
2015-08-22 23:04:57 19131 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-08-22 23:04:57 19131 [Note] InnoDB: Restoring possible half-written data pages
2015-08-22 23:04:57 19131 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 590373690
2015-08-22 23:04:57 19131 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
2015-08-22 23:04:57 19131 [Note] InnoDB: 128 rollback segment(s) are active.
2015-08-22 23:04:57 19131 [Note] InnoDB: Waiting for purge to start
2015-08-22 23:04:57 19131 [Note] InnoDB: 5.6.23 started; log sequence number 590373690
2015-08-22 23:04:57 19131 [Note] Server hostname (bind-address): '*'; port: 3306
2015-08-22 23:04:57 19131 [Note] IPv6 is not available.
2015-08-22 23:04:57 19131 [Note] - '0.0.0.0' resolves to '0.0.0.0';
2015-08-22 23:04:57 19131 [Note] Server socket created on IP: '0.0.0.0'.
2015-08-22 23:04:57 19131 [Note] Event Scheduler: Loaded 0 events
2015-08-22 23:04:57 19131 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.6.23' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
2015-08-23 02:42:47 19131 [Warning] IP address '221.229.162.143' could not be resolved: Name or service not known
2015-08-23 10:27:43 19131 [Warning] Hostname 'unassigned.psychz.net' does not resolve to '45.34.1.137'.
2015-08-23 10:27:43 19131 [Note] Hostname 'unassigned.psychz.net' has the following IP addresses:
2015-08-23 10:27:43 19131 [Note] - 199.15.112.8
2015-08-23 20:42:45 19131 [Warning] IP address '60.191.129.138' could not be resolved: Name or service not known
150823 20:54:08 mysqld_safe Number of processes running now: 0
150823 20:54:08 mysqld_safe mysqld restarted
2015-08-23 20:54:08 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-08-23 20:54:08 9837 [Note] Plugin 'FEDERATED' is disabled.
2015-08-23 20:54:08 9837 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-08-23 20:54:08 9837 [Note] InnoDB: The InnoDB memory heap is disabled
2015-08-23 20:54:08 9837 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-08-23 20:54:08 9837 [Note] InnoDB: Memory barrier is not used
2015-08-23 20:54:08 9837 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-08-23 20:54:08 9837 [Note] InnoDB: Using Linux native AIO
2015-08-23 20:54:08 9837 [Note] InnoDB: Using CPU crc32 instructions
2015-08-23 20:54:08 9837 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-08-23 20:54:08 9837 [Note] InnoDB: Completed initialization of buffer pool
2015-08-23 20:54:08 9837 [Note] InnoDB: Highest supported file format is Barracuda.
2015-08-23 20:54:08 9837 [Note] InnoDB: The log sequence numbers 506046855 and 506046855 in ibdata files do not match the log sequence number 599201345 in the ib_logfiles!
2015-08-23 20:54:08 9837 [Note] InnoDB: Database was not shutdown normally!
2015-08-23 20:54:08 9837 [Note] InnoDB: Starting crash recovery.
2015-08-23 20:54:08 9837 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-08-23 20:54:08 9837 [Note] InnoDB: Restoring possible half-written data pages
2015-08-23 20:54:08 9837 [Note] InnoDB: from the doublewrite buffer...
150823 20:54:08 mysqld_safe mysqld from pid file /var/lib/mysql/{hostname}.pid ended
150823 20:57:33 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2015-08-23 20:57:34 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-08-23 20:57:34 10285 [Note] Plugin 'FEDERATED' is disabled.
2015-08-23 20:57:34 10285 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-08-23 20:57:34 10285 [Note] InnoDB: The InnoDB memory heap is disabled
2015-08-23 20:57:34 10285 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-08-23 20:57:34 10285 [Note] InnoDB: Memory barrier is not used
2015-08-23 20:57:34 10285 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-08-23 20:57:34 10285 [Note] InnoDB: Using Linux native AIO
2015-08-23 20:57:34 10285 [Note] InnoDB: Using CPU crc32 instructions
2015-08-23 20:57:34 10285 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-08-23 20:57:34 10285 [Note] InnoDB: Completed initialization of buffer pool
2015-08-23 20:57:34 10285 [Note] InnoDB: Highest supported file format is Barracuda.
2015-08-23 20:57:34 10285 [Note] InnoDB: The log sequence numbers 506046855 and 506046855 in ibdata files do not match the log sequence number 599201345 in the ib_logfiles!
2015-08-23 20:57:34 10285 [Note] InnoDB: Database was not shutdown normally!
2015-08-23 20:57:34 10285 [Note] InnoDB: Starting crash recovery.
2015-08-23 20:57:34 10285 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-08-23 20:57:34 10285 [Note] InnoDB: Restoring possible half-written data pages
2015-08-23 20:57:34 10285 [Note] InnoDB: from the doublewrite buffer...
2015-08-23 20:57:34 10285 [Note] InnoDB: 128 rollback segment(s) are active.
2015-08-23 20:57:34 10285 [Note] InnoDB: Waiting for purge to start
2015-08-23 20:57:34 10285 [Note] InnoDB: 5.6.23 started; log sequence number 599201345
2015-08-23 20:57:34 10285 [Note] Server hostname (bind-address): '*'; port: 3306
2015-08-23 20:57:34 10285 [Note] IPv6 is not available.
2015-08-23 20:57:34 10285 [Note] - '0.0.0.0' resolves to '0.0.0.0';
2015-08-23 20:57:34 10285 [Note] Server socket created on IP: '0.0.0.0'.
2015-08-23 20:57:34 10285 [Note] Event Scheduler: Loaded 0 events
2015-08-23 20:57:34 10285 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.6.23' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
MySQL 5.6 is not supposed to use 5.5 unmodified data files - the format changes in every version and, sometimes, it changes even for patch versions.
After an upgrade you should run mysql_upgrade. Then, you can use your database normally.
First item of action would be to disconnect from your website immediately to prevent further corruption. One way to do this is to just alter the credentials of your application.
You'll need to perform a repair of the data to fix the inconsistencies in the binary logs.
Please refer to this article from MySql, which provides steps to repair. The tool mysqlcheck should be available in the command line.

Database connection error in wordpress

My site is on Wordpress and is hosted on a VPS server. The traffic is not much but the database connect error is displayed many times, and then I had to restart MySQL.
I've checked the MySQL error file log. Here is a certain portion of the log.
140310 01:13:26 mysqld_safe mysqld from pid file /var/lib/mysql/server.gosoftnep.com.pid ended
140310 01:13:26 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140310 1:13:26 [Note] Plugin 'FEDERATED' is disabled.
140310 1:13:26 InnoDB: The InnoDB memory heap is disabled
140310 1:13:26 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140310 1:13:26 InnoDB: Compressed tables use zlib 1.2.3
140310 1:13:26 InnoDB: Using Linux native AIO
140310 1:13:26 InnoDB: Initializing buffer pool, size = 128.0M
140310 1:13:26 InnoDB: Completed initialization of buffer pool
140310 1:13:26 InnoDB: highest supported file format is Barracuda.
140310 1:13:26 InnoDB: Waiting for the background threads to start
140310 1:13:27 InnoDB: 5.5.36 started; log sequence number 12082242998
140310 1:13:27 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
140310 1:13:27 [Note] - '0.0.0.0' resolves to '0.0.0.0';
140310 1:13:27 [Note] Server socket created on IP: '0.0.0.0'.
140310 1:13:27 [Note] Event Scheduler: Loaded 0 events
140310 1:13:27 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.36-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
140310 01:13:32 mysqld_safe A mysqld process already exists
140310 5:52:48 [Warning] IP address '58.118.152.8' could not be resolved: Temporary failure in name resolution
140310 12:27:37 mysqld_safe Number of processes running now: 0
140310 12:27:38 mysqld_safe mysqld restarted
140310 12:27:44 [Note] Plugin 'FEDERATED' is disabled.
140310 12:27:45 InnoDB: The InnoDB memory heap is disabled
140310 12:27:45 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140310 12:27:45 InnoDB: Compressed tables use zlib 1.2.3
140310 12:27:45 InnoDB: Using Linux native AIO
140310 12:27:47 InnoDB: Initializing buffer pool, size = 128.0M
140310 12:27:49 InnoDB: Completed initialization of buffer pool
140310 12:27:50 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 12354557593
140310 12:27:52 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...
InnoDB: Doing recovery: scanned up to log sequence number 12354588661
140310 12:28:05 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
140310 12:28:07 InnoDB: Waiting for the background threads to start
140310 12:28:08 InnoDB: 5.5.36 started; log sequence number 12354588661
140310 12:28:08 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
140310 12:28:08 [Note] - '0.0.0.0' resolves to '0.0.0.0';
140310 12:28:08 [Note] Server socket created on IP: '0.0.0.0'.
140310 12:28:12 [Note] Event Scheduler: Loaded 0 events
140310 12:28:12 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.36-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
140311 11:51:59 [Warning] IP address '61.160.249.239' could not be resolved: Name or service not known
140312 9:23:21 [Warning] IP address '183.60.107.205' could not be resolved: Name or service not known
140313 0:33:47 [Warning] IP address '221.228.231.59' could not be resolved: Name or service not known
140313 7:33:05 [Warning] IP address '61.147.103.160' could not be resolved: Name or service not known
140313 20:42:42 [Warning] IP address '124.89.32.242' could not be resolved: Name or service not known
140313 23:33:38 mysqld_safe Number of processes running now: 0
140313 23:33:38 mysqld_safe mysqld restarted
140313 23:34:09 [Note] Plugin 'FEDERATED' is disabled.
140313 23:34:14 InnoDB: The InnoDB memory heap is disabled
140313 23:34:14 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140313 23:34:14 InnoDB: Compressed tables use zlib 1.2.3
140313 23:34:14 InnoDB: Using Linux native AIO
140313 23:34:17 InnoDB: Initializing buffer pool, size = 128.0M
140313 23:34:20 InnoDB: Completed initialization of buffer pool
140313 23:34:30 mysqld_safe mysqld from pid file /var/lib/mysql/server.gosoftnep.com.pid ended
140314 02:55:09 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140314 2:55:10 [Note] Plugin 'FEDERATED' is disabled.
140314 2:55:10 InnoDB: The InnoDB memory heap is disabled
140314 2:55:10 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140314 2:55:10 InnoDB: Compressed tables use zlib 1.2.3
140314 2:55:10 InnoDB: Using Linux native AIO
140314 2:55:10 InnoDB: Initializing buffer pool, size = 128.0M
140314 2:55:10 InnoDB: Completed initialization of buffer pool
140314 2:55:10 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 14587500130
140314 2:55:10 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...
InnoDB: Doing recovery: scanned up to log sequence number 14587535674
140314 2:55:11 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
140314 2:55:11 InnoDB: Waiting for the background threads to start
140314 2:55:12 InnoDB: 5.5.36 started; log sequence number 14587535674
140314 2:55:12 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
140314 2:55:12 [Note] - '0.0.0.0' resolves to '0.0.0.0';
140314 2:55:12 [Note] Server socket created on IP: '0.0.0.0'.
140314 2:55:12 [Note] Event Scheduler: Loaded 0 events
140314 2:55:12 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.36-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
I do not understand anything about this. Could anyone explain the issue to me or suggest a fix?

MySQL Will Not Start - InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery

I am having some problems with MySQL - the service has stopped and will not restart.
I have an XAMPP stack running MediaWiki which is what uses the MySQL database. The server itself is a VM running Windows 2003 SP2 with 512MB RAM.
Below is an extract from the mysql_error.log
121120 16:11:46 [Note] Plugin 'FEDERATED' is disabled.
121120 16:11:46 InnoDB: The InnoDB memory heap is disabled
121120 16:11:46 InnoDB: Mutexes and rw_locks use Windows interlocked functions
121120 16:11:46 InnoDB: Compressed tables use zlib 1.2.3
121120 16:11:46 InnoDB: Initializing buffer pool, size = 16.0M
121120 16:11:46 InnoDB: Completed initialization of buffer pool
121120 16:11:46 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 28821623
121120 16:11:47 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...
InnoDB: Doing recovery: scanned up to log sequence number 28825154
121120 16:11:47 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
121120 16:11:48 InnoDB: Waiting for the background threads to start
121120 16:11:49 InnoDB: 1.1.8 started; log sequence number 28825154
121120 16:11:49 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
121120 16:11:49 [Note] - '0.0.0.0' resolves to '0.0.0.0';
121120 16:11:49 [Note] Server socket created on IP: '0.0.0.0'.
121120 16:11:49 [Note] Event Scheduler: Loaded 0 events
121120 16:11:49 [Note] d:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.25a' socket: '' port: 3306 MySQL Community Server (GPL)
121120 16:16:41 [Note] Plugin 'FEDERATED' is disabled.
121120 16:16:41 InnoDB: The InnoDB memory heap is disabled
121120 16:16:41 InnoDB: Mutexes and rw_locks use Windows interlocked functions
121120 16:16:41 InnoDB: Compressed tables use zlib 1.2.3
121120 16:16:41 InnoDB: Initializing buffer pool, size = 16.0M
121120 16:16:41 InnoDB: Completed initialization of buffer pool
121120 16:16:41 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!
121120 16:16:41 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...
121120 16:16:42 InnoDB: Waiting for the background threads to start
121120 16:16:43 InnoDB: 1.1.8 started; log sequence number 28841927
121120 16:16:43 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
121120 16:16:43 [Note] - '0.0.0.0' resolves to '0.0.0.0';
121120 16:16:43 [Note] Server socket created on IP: '0.0.0.0'.
121120 16:16:43 [Note] Event Scheduler: Loaded 0 events
121120 16:16:43 [Note] d:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.25a' socket: '' port: 3306 MySQL Community Server (GPL)
Fixes Attempted:
Tried starting from services - error 1067 - "The Process Terminated unexpectedly"
Tried restarting the server itself - no good
Tried moving the ib_logfile0 and ib_logfile1 files from directory and restarting server no good
Tried killing the PID of MySQL from command prompt in case it was still running but it was not running.
If anybody could point me in the right direction it would be much appreciated.
NB> I am also trying to get the RAM of the server increased in case that is the issue. At the moment of the 512MB only about 90MB is free.
thanks
Dwayne