140819  2:15:21 [Note] CONNECT: Version 1.03.0002 Aug 19 2014 01:59:23

2014-08-19 02:15:21 7f1757a32740 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.

140819  2:15:21 [Note] InnoDB: Using mutexes to ref count buffer pool pages

140819  2:15:21 [Note] InnoDB: The InnoDB memory heap is disabled

140819  2:15:21 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

140819  2:15:21 [Note] InnoDB: Compressed tables use zlib 1.2.8

140819  2:15:21 [Note] InnoDB: Using Linux native AIO

140819  2:15:21 [Note] InnoDB: Using CPU crc32 instructions

140819  2:15:21 [Note] InnoDB: Initializing buffer pool, size = 8.0G

140819  2:15:21 [Note] InnoDB: Completed initialization of buffer pool

140819  2:15:21 [Note] InnoDB: Highest supported file format is Barracuda.

140819  2:15:22 [Note] InnoDB: 128 rollback segment(s) are active.

140819  2:15:22 [Note] InnoDB: Waiting for purge to start

140819  2:15:22 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.19-67.0 started; log sequence number 845197876557

140819  2:15:22 [Note] Server socket created on IP: '0.0.0.0'.

140819  2:15:22 [Note] Event Scheduler: Loaded 0 events

140819  2:15:22 [Note] /usr/sbin/mysqld: ready for connections.

Version: '10.0.13-MariaDB-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Source distribution

140819  2:15:28 [Warning] IP address '192.168.200.2' could not be resolved: Name or service not known

2014-08-19 02:41:43 7f151bfff700 InnoDB: FTS Optimize Removing table emsow_demo4/files_text

2014-08-19 04:06:14 7f151bfff700 InnoDB: FTS Optimize Removing table emsow_demo4/inventory_files_text

2014-08-19 07:26:16 7f151bfff700 InnoDB: FTS Optimize Removing table emsow_demo4/vendor_files_text

Status information:

Current dir: /var/lib/mysql/

Running threads: 198  Stack size: 294912

Current locks:

lock: 0x7f150a216af0:

lock: 0x7f14f0b04968:

lock: 0x7f14f17a72d8:

lock: 0x7f14f103c0a8:

lock: 0x7f14f15e8298:

lock: 0x7f14f05a9398:

lock: 0x7f14f0a10ad8:

lock: 0x7f14f10f2c48:

lock: 0x7f1509cde6e8:

lock: 0x7f14f0e87fe8:

lock: 0x7f150b91b718:

lock: 0x7f14f0fd50f8:

lock: 0x7f14f018a368:

lock: 0x7f14f047dc88:

lock: 0x7f14f0df9598:

lock: 0x7f14f14da6e8:

lock: 0x7f14f02fc3e8:

lock: 0x7f150b5b7578:

lock: 0x7f150a1532c8:

lock: 0x7f15081b0fa8:

lock: 0x7f1508ef7788:

lock: 0x7f14f183bb48:

lock: 0x7f14f0409268:

lock: 0x7f14f1496758:

lock: 0x7f14f0f59938:

lock: 0x7f14f0355368:

lock: 0x7f14f0018538:

lock: 0x7f14f1480468:

lock: 0x7f14f04235a8:

lock: 0x7f14f07c8768:

lock: 0x7f14f13eaf58:

lock: 0x7f14f0089e98:

lock: 0x7f14f039cac8:

lock: 0x7f14f141fc68:

lock: 0x7f14f140b788:

lock: 0x7f14f141e8a8:

lock: 0x7f14f0f71fd8:

lock: 0x7f14f07ff708:

lock: 0x7f14f064bd68:

lock: 0x7f14f05c2a78:

lock: 0x7f14f1394aa8:

lock: 0x7f14f0c91cf8:

lock: 0x7f150a782ba8:

lock: 0x7f14f1781348:

lock: 0x7f15096f5588:

lock: 0x7f1508acdce8:

lock: 0x7f1509f19858:

lock: 0x7f150b412ab8:

lock: 0x7f15084141e8:

lock: 0x7f1509019f18:

lock: 0x7f14f0c77168:

lock: 0x7f14f073b7a8:

lock: 0x7f150a6f4238:

lock: 0x7f15099acc58:

lock: 0x7f150a005568:

lock: 0x7f150ad29ae8:

lock: 0x7f1508bcfbc8:

lock: 0x7f1508ae88c8:

lock: 0x7f1509fdb778:

lock: 0x7f1508ba6108:

lock: 0x7f150aecccf8:

lock: 0x7f1509787ff8:

lock: 0x7f150a253648:

lock: 0x7f150a580648:

lock: 0x7f150ae67088:

lock: 0x7f1509596588:

lock: 0x7f150aee98a8:

lock: 0x7f150b24df28:

lock: 0x7f1509b5b248:

lock: 0x7f150b93fdc8:

lock: 0x7f1508fc3068:

lock: 0x7f15083cc988:

lock: 0x7f150b5ad828:

lock: 0x7f150a634cf8:

lock: 0x7f150892d1e8:

lock: 0x7f1508738ad8:

lock: 0x7f150a7565f8:

lock: 0x7f150bac1ae8:

lock: 0x7f1508cb1f38:

lock: 0x7f150aa24c78:

lock: 0x7f15094db5f8:

lock: 0x7f1509825a18:

lock: 0x7f150a4229b8:

lock: 0x7f150923f0b8:

lock: 0x7f150a4bf738:

lock: 0x7f1509c7dcb8:

lock: 0x7f14f0fd1d88:

lock: 0x7f14f0170e98:

lock: 0x7f1508338068:

lock: 0x7f1508d19768:

lock: 0x7f1508d3aad8:

lock: 0x7f1509cd95c8:

lock: 0x7f1508071918:

lock: 0x7f150a0d6bb8:

lock: 0x7f15091988a8:

lock: 0x7f150a560098:

lock: 0x7f1508d1aab8:

lock: 0x7f150b5a12f8:

lock: 0x7f1509711f68:

lock: 0x7f150a1a9d68:

lock: 0x7f15082e8b58:

lock: 0x7f150bd7d478:

lock: 0x7f1508c4d0c8:

lock: 0x7f15087983e8:

lock: 0x7f150852e308:

lock: 0x7f15090cd7e8:

lock: 0x7f150a9c3088:

lock: 0x7f150ac90df8:

lock: 0x7f150a375058:

lock: 0x7f1508014538:

lock: 0x7f150a7d7108:

lock: 0x7f15086852d8:

lock: 0x7f14f15bbad8:

lock: 0x7f14f0ae7c68:

lock: 0x7f150b7bfb48:

lock: 0x7f15087e0528:

lock: 0x132df60:

lock: 0x132de80:

lock: 0x132cec0:

lock: 0x132cde0:

lock: 0x132cd00:

lock: 0x132d080:

lock: 0x132b2c0:

lock: 0x132dda0:

lock: 0x132b9c0:

lock: 0x132bc60:

lock: 0x132b8e0:

lock: 0x132bb80:

lock: 0x132b800:

lock: 0x132baa0:

lock: 0x132bfe0:

lock: 0x132c0c0:

lock: 0x132c1a0:

lock: 0x132b720:

lock: 0x132b480:

lock: 0x132b640:

lock: 0x132b3a0:

lock: 0x132b560:

lock: 0x132bd40:

lock: 0x132be20:

lock: 0x132bf00:

lock: 0x132da20:

lock: 0x132dcc0:

lock: 0x132dbe0:

lock: 0x132db00:

lock: 0x132d6a0:

lock: 0x132d5c0:

lock: 0x132d4e0:

lock: 0x132d400:

lock: 0x132d320:

lock: 0x132d860:

lock: 0x132d240:

lock: 0x132d160:

lock: 0x132d940:

lock: 0x132cfa0:

lock: 0x132cb40:

lock: 0x132cc20:

lock: 0x132ca60:

lock: 0x132c980:

lock: 0x132c600:

lock: 0x132c8a0:

lock: 0x132c7c0:

lock: 0x132c520:

lock: 0x132c6e0:

lock: 0x132c280:

lock: 0x132c360:

lock: 0x132c440:

lock: 0x132d780:

Key caches:

default

Buffer_size:      16777216

Block_size:           1024

Division_limit:        100

Age_threshold:         300

Partitions:              0

blocks used:         11443

not flushed:             0

w_requests:           2646

writes:               2385

r_requests:          86404

reads:               39484

handler status:

read_key:   2715553269

read_next:  8256147764

read_rnd     430526522

read_first:     240910

write:        54075782

delete           91743

update:         662231

Table status:

Opened tables:   67820861

Open tables:           64

Open files:            12

Open streams:           0

Alarm status:

Active alarms:   0

Max used alarms: 0

Next alarm time: 0

Memory status:

Non-mmapped space allocated from system: 597786624

Number of free chunks:			 20928

Number of fastbin blocks:		 360

Number of mmapped regions:		 12

Space in mmapped regions:		 372092928

Maximum total allocated space:		 0

Space available in freed fastbin blocks: 25712

Total allocated space:			 380009568

Total free space:			 217777056

Top-most, releasable space:		 7471824

Estimated memory (with thread stack):    1027977216

Events status:

LLA = Last Locked At  LUA = Last Unlocked At

WOC = Waiting On Condition  DL = Data Locked

Event scheduler status:

State      : INITIALIZED

Thread id  : 0

LLA        : n/a:0

LUA        : n/a:0

WOC        : NO

Workers    : 0

Executed   : 0

Data locked: NO

Event queue status:

Element count   : 0

Data locked     : NO

Attempting lock : NO

LLA             : init_queue:139

LUA             : init_queue:149

WOC             : NO

Next activation : never

2014-08-20 12:59:23 7f151b16f700  InnoDB: MySQL and InnoDB data dictionaries are out of sync.

InnoDB: Unable to find the AUTOINC column vid in the InnoDB table `�߈�.

InnoDB: We set the next AUTOINC column value to 0,

InnoDB: in effect disabling the AUTOINC next value generation.

InnoDB: You can either set the next AUTOINC value explicitly using ALTER TABLE

InnoDB: or fix the data dictionary by recreating the table.

InnoDB: Warning: Index PRIMARY points to table `�߈� and ib_table emsow_mart/pacs_ae#P#del statistics is initialized 1  but index table `�߈� initialized 0  mysql table is pacs_ae. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html

2014-08-20 12:59:23 7f151b16f700  InnoDB: Assertion failure in thread 139728625530624 in file dict0stats.cc line 3199

InnoDB: Failing assertion: strchr(table->name, '/') != NULL

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.

InnoDB: [Error] Index for key no 0 mysql name PRIMARY , InnoDB name pcq_status for table emsow_wellness/sysvars#P#ndel

InnoDB: [Note] Index for key no 0 mysql name PRIMARY , InnoDB name pcq_status for table emsow_wellness/sysvars#P#ndel

InnoDB: [Note] Index for key no 0 mysql name PRIMARY , InnoDB name dusr for table emsow_wellness/sysvars#P#ndel

InnoDB: [Note] Index for key no 0 mysql name PRIMARY , InnoDB name pcq_priority_pcq_queued_ts_pcq_id for table emsow_wellness/sysvars#P#ndel

InnoDB: [Note] Index for key no 0 mysql name PRIMARY , InnoDB name pacsfile_series_number for table emsow_wellness/sysvars#P#ndel

InnoDB: [Note] Index for key no 0 mysql name PRIMARY , InnoDB name dusr for table emsow_wellness/sysvars#P#ndel

InnoDB: [Note] Index for key no 0 mysql name PRIMARY , InnoDB name (null) for table emsow_wellness/sysvars#P#ndel

InnoDB: [Note] Index for key no 0 mysql name PRIMARY , InnoDB name pcq_queued_user for table emsow_wellness/sysvars#P#ndel

2014-08-20 12:59:23 7f151a92a700  InnoDB: Assertion failure in thread 139728616859392 in file ha_innodb.cc line 8619

InnoDB: Failing assertion: ut_strcmp(index->name, key->name) == 0

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.

140820 12:59:23 [ERROR] 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.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

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.

Server version: 10.0.13-MariaDB-log

key_buffer_size=16777216

read_buffer_size=262144

max_used_connections=287

max_threads=502

thread_count=266

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 412288 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x12e2a9b8

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...

140820 13:01:27 [Note] CONNECT: Version 1.03.0002 Aug 19 2014 01:59:23

2014-08-20 13:01:27 7fbea6e7a740 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.

140820 13:01:27 [Note] InnoDB: Using mutexes to ref count buffer pool pages

140820 13:01:27 [Note] InnoDB: The InnoDB memory heap is disabled

140820 13:01:27 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

140820 13:01:27 [Note] InnoDB: Compressed tables use zlib 1.2.8

140820 13:01:27 [Note] InnoDB: Using Linux native AIO

140820 13:01:27 [Note] InnoDB: Using CPU crc32 instructions

140820 13:01:27 [Note] InnoDB: Initializing buffer pool, size = 8.0G

140820 13:01:28 [Note] InnoDB: Completed initialization of buffer pool

140820 13:01:28 [Note] InnoDB: Highest supported file format is Barracuda.

140820 13:01:28 [Note] InnoDB: Log scan progressed past the checkpoint lsn 868957090106

140820 13:01:28 [Note] InnoDB: Database was not shutdown normally!

140820 13:01:28 [Note] InnoDB: Starting crash recovery.

140820 13:01:28 [Note] InnoDB: Reading tablespace information from the .ibd files...

140820 13:01:40 [Note] InnoDB: Restoring possible half-written data pages 

140820 13:01:40 [Note] InnoDB: from the doublewrite buffer...

InnoDB: Doing recovery: scanned up to log sequence number 868962332672

InnoDB: Doing recovery: scanned up to log sequence number 868967575552

InnoDB: Doing recovery: scanned up to log sequence number 868972818432

InnoDB: Doing recovery: scanned up to log sequence number 868978061312

InnoDB: Doing recovery: scanned up to log sequence number 868983304192

InnoDB: Doing recovery: scanned up to log sequence number 868988547072

InnoDB: Doing recovery: scanned up to log sequence number 868993789952

InnoDB: Doing recovery: scanned up to log sequence number 868999032832

InnoDB: Doing recovery: scanned up to log sequence number 869004275712

InnoDB: Doing recovery: scanned up to log sequence number 869009518592

InnoDB: Doing recovery: scanned up to log sequence number 869014761472

InnoDB: Doing recovery: scanned up to log sequence number 869020004352

InnoDB: Doing recovery: scanned up to log sequence number 869025247232

InnoDB: Doing recovery: scanned up to log sequence number 869030490112

InnoDB: Doing recovery: scanned up to log sequence number 869035732992

InnoDB: Doing recovery: scanned up to log sequence number 869040975872

InnoDB: Doing recovery: scanned up to log sequence number 869046218752

InnoDB: Doing recovery: scanned up to log sequence number 869051461632

InnoDB: Doing recovery: scanned up to log sequence number 869055136193

140820 13:01:45 [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 47871805, file name ./emsow-bin.000028

140820 13:01:50 [Note] InnoDB: 128 rollback segment(s) are active.

140820 13:02:42 [Note] InnoDB: Waiting for purge to start

140820 13:02:42 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.19-67.0 started; log sequence number 869055136193

140820 13:02:42 [Note] Recovering after a crash using emsow-bin

140820 13:02:43 [Note] Starting crash recovery...

140820 13:02:43 [Note] Crash recovery finished.

140820 13:02:43 [Note] Server socket created on IP: '0.0.0.0'.

140820 13:02:43 [Note] Event Scheduler: Loaded 0 events

140820 13:02:43 [Note] /usr/sbin/mysqld: ready for connections.

Version: '10.0.13-MariaDB-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Source distribution

140820 13:02:44 [Warning] IP address '192.168.200.2' could not be resolved: Name or service not known

2014-08-20 13:16:51 7fbc71ffb700 InnoDB: FTS Optimize Removing table emsow_aus/files_text

2014-08-20 13:16:54 7fbc71ffb700 InnoDB: FTS Optimize Removing table emsow_aus/inventory_files_text

140822  5:07:55 [Note] /usr/sbin/mysqld: Normal shutdown

140822  5:07:56 [Note] Event Scheduler: Purging the queue. 0 events

140822  5:08:42 [Note] InnoDB: FTS optimize thread exiting.

140822  5:08:42 [Note] InnoDB: Starting shutdown...

140822  5:09:24 [Note] InnoDB: Shutdown completed; log sequence number 876823105755

140822  5:09:24 [Note] /usr/sbin/mysqld: Shutdown complete

140822  5:09:25 [Note] CONNECT: Version 1.03.0002 Aug 19 2014 01:59:23

2014-08-22 05:09:25 7f748e511740 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.

140822  5:09:25 [Note] InnoDB: Using mutexes to ref count buffer pool pages

140822  5:09:25 [Note] InnoDB: The InnoDB memory heap is disabled

140822  5:09:25 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

140822  5:09:25 [Note] InnoDB: Compressed tables use zlib 1.2.8

140822  5:09:25 [Note] InnoDB: Using Linux native AIO

140822  5:09:25 [Note] InnoDB: Using CPU crc32 instructions

140822  5:09:25 [Note] InnoDB: Initializing buffer pool, size = 8.0G

140822  5:09:25 [Note] InnoDB: Completed initialization of buffer pool

140822  5:09:25 [Note] InnoDB: Highest supported file format is Barracuda.

140822  5:09:28 [Note] InnoDB: 128 rollback segment(s) are active.

140822  5:09:28 [Note] InnoDB: Waiting for purge to start

140822  5:09:28 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.19-67.0 started; log sequence number 876823105755

140822  5:09:28 [Note] Server socket created on IP: '0.0.0.0'.

140822  5:09:28 [Note] Event Scheduler: Loaded 0 events

140822  5:09:28 [Note] /usr/sbin/mysqld: ready for connections.

Version: '10.0.13-MariaDB-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Source distribution

140822  5:09:36 [Warning] IP address '192.168.200.2' could not be resolved: Name or service not known

2014-08-24 06:22:11 7f7256d71700 InnoDB: FTS Optimize Removing table emsow_demo4/files_text

2014-08-24 07:36:52 7f7256d71700 InnoDB: FTS Optimize Removing table emsow_demo4/inventory_files_text

InnoDB: [Error] Index for key no 0 mysql name PRIMARY , InnoDB name pacspkg_id for table emsow_pus/rdoctors#P#del

InnoDB: [Note] Index for key no 0 mysql name PRIMARY , InnoDB name pacspkg_id for table emsow_pus/rdoctors#P#del

InnoDB: [Note] Index for key no 0 mysql name PRIMARY , InnoDB name rdoctor_id for table emsow_pus/rdoctors#P#del

InnoDB: [Note] Index for key no 0 mysql name PRIMARY , InnoDB name cts for table emsow_pus/rdoctors#P#del

InnoDB: [Note] Index for key no 0 mysql name PRIMARY , InnoDB name dts for table emsow_pus/rdoctors#P#del

InnoDB: [Note] Index for key no 0 mysql name PRIMARY , InnoDB name cusr for table emsow_pus/rdoctors#P#del

InnoDB: [Note] Index for key no 0 mysql name PRIMARY , InnoDB name dusr for table emsow_pus/rdoctors#P#del

2014-08-24 07:37:33 7f715e60c700  InnoDB: Assertion failure in thread 140124891432704 in file ha_innodb.cc line 8619

InnoDB: Failing assertion: ut_strcmp(index->name, key->name) == 0

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.

140824  7:37:33 [ERROR] 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.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

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.

Server version: 10.0.13-MariaDB-log

key_buffer_size=16777216

read_buffer_size=262144

max_used_connections=304

max_threads=502

thread_count=204

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 412288 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x12aaaeb8

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 = 0x7f715e60be68 thread_stack 0x48000

/usr/sbin/mysqld(my_print_stacktrace+0x26)[0xb24a16]

/usr/sbin/mysqld(handle_fatal_signal+0x398)[0x6f2888]

/lib64/libpthread.so.0(+0x10c20)[0x7f748d847c20]

/lib64/libc.so.6(gsignal+0x35)[0x7f748c463265]

/lib64/libc.so.6(abort+0x17b)[0x7f748c4646db]

/usr/sbin/mysqld[0x97986a]

/usr/sbin/mysqld[0x979cb2]

/usr/sbin/mysqld[0x982824]

/usr/sbin/mysqld(_ZN7handler7ha_openEP5TABLEPKcij+0x3f)[0x6f64df]

/usr/sbin/mysqld[0xb0389d]

/usr/sbin/mysqld(_ZN7handler7ha_openEP5TABLEPKcij+0x3f)[0x6f64df]

/usr/sbin/mysqld(_Z21open_table_from_shareP3THDP11TABLE_SHAREPKcjjjP5TABLEb+0x86c)[0x64fa1c]

/usr/sbin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP11st_mem_rootP18Open_table_context+0x6c1)[0x58b521]

/usr/sbin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0xd0f)[0x58c74f]

/usr/sbin/mysqld(_Z20open_and_lock_tablesP3THDP10TABLE_LISTbjP19Prelocking_strategy+0x49)[0x58c969]

/usr/sbin/mysqld[0x5bbadd]

/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x50ce)[0x5c681e]

/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x1fc)[0x5c905c]

/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x15dd)[0x5ca68d]

/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x19d)[0x6726ad]

/usr/sbin/mysqld(handle_one_connection+0x40)[0x672770]

/lib64/libpthread.so.0(+0x8eb7)[0x7f748d83feb7]

/lib64/libc.so.6(clone+0x6d)[0x7f748c51aa7d]

Trying to get some variables.

Some pointers may be invalid and cause the dump to abort.

Query (0x7f715aa48220): is an invalid pointer

Connection ID (thread ID): 127000

Status: NOT_KILLED

Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on

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.

140824 12:07:53 [Note] CONNECT: Version 1.03.0002 Aug 19 2014 01:59:23

2014-08-24 12:07:53 7f8e484ad740 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.

140824 12:07:53 [Note] InnoDB: Using mutexes to ref count buffer pool pages

140824 12:07:53 [Note] InnoDB: The InnoDB memory heap is disabled

140824 12:07:53 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

140824 12:07:53 [Note] InnoDB: Compressed tables use zlib 1.2.8

140824 12:07:53 [Note] InnoDB: Using Linux native AIO

140824 12:07:53 [Note] InnoDB: Using CPU crc32 instructions

140824 12:07:53 [Note] InnoDB: Initializing buffer pool, size = 8.0G

140824 12:07:54 [Note] InnoDB: Completed initialization of buffer pool

140824 12:07:54 [Note] InnoDB: Highest supported file format is Barracuda.

140824 12:07:54 [Note] InnoDB: Log scan progressed past the checkpoint lsn 894383990245

140824 12:07:54 [Note] InnoDB: Database was not shutdown normally!

140824 12:07:54 [Note] InnoDB: Starting crash recovery.

140824 12:07:54 [Note] InnoDB: Reading tablespace information from the .ibd files...

140824 12:08:03 [Note] InnoDB: Restoring possible half-written data pages 

140824 12:08:03 [Note] InnoDB: from the doublewrite buffer...

InnoDB: Doing recovery: scanned up to log sequence number 894389232640

InnoDB: Doing recovery: scanned up to log sequence number 894394475520

InnoDB: Doing recovery: scanned up to log sequence number 894399718400

InnoDB: Doing recovery: scanned up to log sequence number 894404961280

InnoDB: Doing recovery: scanned up to log sequence number 894410204160

InnoDB: Doing recovery: scanned up to log sequence number 894415447040

InnoDB: Doing recovery: scanned up to log sequence number 894420689920

InnoDB: Doing recovery: scanned up to log sequence number 894425932800

InnoDB: Doing recovery: scanned up to log sequence number 894431175680

InnoDB: Doing recovery: scanned up to log sequence number 894436418560

InnoDB: Doing recovery: scanned up to log sequence number 894441661440

InnoDB: Doing recovery: scanned up to log sequence number 894446904320

InnoDB: Doing recovery: scanned up to log sequence number 894452147200

InnoDB: Doing recovery: scanned up to log sequence number 894457390080

InnoDB: Doing recovery: scanned up to log sequence number 894462632960

InnoDB: Doing recovery: scanned up to log sequence number 894467875840

InnoDB: Doing recovery: scanned up to log sequence number 894473118720

InnoDB: Doing recovery: scanned up to log sequence number 894478361600

InnoDB: Doing recovery: scanned up to log sequence number 894483604480

InnoDB: Doing recovery: scanned up to log sequence number 894488847360

InnoDB: Doing recovery: scanned up to log sequence number 894494090240

InnoDB: Doing recovery: scanned up to log sequence number 894499333120

InnoDB: Doing recovery: scanned up to log sequence number 894504576000

InnoDB: Doing recovery: scanned up to log sequence number 894509818880

InnoDB: Doing recovery: scanned up to log sequence number 894515061760

InnoDB: Doing recovery: scanned up to log sequence number 894520304640

InnoDB: Doing recovery: scanned up to log sequence number 894525547520

InnoDB: Doing recovery: scanned up to log sequence number 894530790400

InnoDB: Doing recovery: scanned up to log sequence number 894536033280

InnoDB: Doing recovery: scanned up to log sequence number 894541276160

InnoDB: Doing recovery: scanned up to log sequence number 894546519040

InnoDB: Doing recovery: scanned up to log sequence number 894551761920

InnoDB: Doing recovery: scanned up to log sequence number 894557004800

InnoDB: Doing recovery: scanned up to log sequence number 894562247680

InnoDB: Doing recovery: scanned up to log sequence number 894567490560

InnoDB: Doing recovery: scanned up to log sequence number 894572733440

InnoDB: Doing recovery: scanned up to log sequence number 894577976320

InnoDB: Doing recovery: scanned up to log sequence number 894583219200

InnoDB: Doing recovery: scanned up to log sequence number 894588462080

InnoDB: Doing recovery: scanned up to log sequence number 894593704960

InnoDB: Doing recovery: scanned up to log sequence number 894598947840

InnoDB: Doing recovery: scanned up to log sequence number 894604190720

InnoDB: Doing recovery: scanned up to log sequence number 894609433600

InnoDB: Doing recovery: scanned up to log sequence number 894614676480

InnoDB: Doing recovery: scanned up to log sequence number 894619919360

InnoDB: Doing recovery: scanned up to log sequence number 894625162240

InnoDB: Doing recovery: scanned up to log sequence number 894630405120

InnoDB: Doing recovery: scanned up to log sequence number 894635648000

InnoDB: Doing recovery: scanned up to log sequence number 894640890880

InnoDB: Doing recovery: scanned up to log sequence number 894646133760

InnoDB: Doing recovery: scanned up to log sequence number 894651376640

InnoDB: Doing recovery: scanned up to log sequence number 894656619520

InnoDB: Doing recovery: scanned up to log sequence number 894661862400

InnoDB: Doing recovery: scanned up to log sequence number 894667105280

InnoDB: Doing recovery: scanned up to log sequence number 894672348160

InnoDB: Doing recovery: scanned up to log sequence number 894677591040

InnoDB: Doing recovery: scanned up to log sequence number 894682833920

InnoDB: Doing recovery: scanned up to log sequence number 894688076800

InnoDB: Doing recovery: scanned up to log sequence number 894693319680

InnoDB: Doing recovery: scanned up to log sequence number 894698562560

InnoDB: Doing recovery: scanned up to log sequence number 894703805440

InnoDB: Doing recovery: scanned up to log sequence number 894709048320

InnoDB: Doing recovery: scanned up to log sequence number 894714291200

InnoDB: Doing recovery: scanned up to log sequence number 894719534080

InnoDB: Doing recovery: scanned up to log sequence number 894724776960

InnoDB: Doing recovery: scanned up to log sequence number 894730019840

InnoDB: Doing recovery: scanned up to log sequence number 894735262720

InnoDB: Doing recovery: scanned up to log sequence number 894740505600

InnoDB: Doing recovery: scanned up to log sequence number 894745748480

InnoDB: Doing recovery: scanned up to log sequence number 894750991360

InnoDB: Doing recovery: scanned up to log sequence number 894756234240

InnoDB: Doing recovery: scanned up to log sequence number 894761477120

InnoDB: Doing recovery: scanned up to log sequence number 894766720000

InnoDB: Doing recovery: scanned up to log sequence number 894771962880

140824 12:08:11 [Note] CONNECT: Version 1.03.0002 Aug 19 2014 01:59:23

140824 12:08:11 [ERROR] mysqld: Can't lock aria control file '/var/lib/mysql/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds

InnoDB: Doing recovery: scanned up to log sequence number 894777205760

InnoDB: Doing recovery: scanned up to log sequence number 894782448640

InnoDB: Doing recovery: scanned up to log sequence number 894787691520

InnoDB: Doing recovery: scanned up to log sequence number 894792934400

InnoDB: Doing recovery: scanned up to log sequence number 894798177280

InnoDB: Doing recovery: scanned up to log sequence number 894803420160

InnoDB: Doing recovery: scanned up to log sequence number 894808663040

InnoDB: Doing recovery: scanned up to log sequence number 894813905920

InnoDB: Doing recovery: scanned up to log sequence number 894819148800

InnoDB: Doing recovery: scanned up to log sequence number 894824391680

InnoDB: Doing recovery: scanned up to log sequence number 894829634560

InnoDB: Doing recovery: scanned up to log sequence number 894834877440

InnoDB: Doing recovery: scanned up to log sequence number 894840120320

InnoDB: Doing recovery: scanned up to log sequence number 894845363200

InnoDB: Doing recovery: scanned up to log sequence number 894850606080

InnoDB: Doing recovery: scanned up to log sequence number 894855848960

InnoDB: Doing recovery: scanned up to log sequence number 894861091840

InnoDB: Doing recovery: scanned up to log sequence number 894866334720

InnoDB: Doing recovery: scanned up to log sequence number 894871577600

InnoDB: Doing recovery: scanned up to log sequence number 894876820480

InnoDB: Doing recovery: scanned up to log sequence number 894882063360

InnoDB: Doing recovery: scanned up to log sequence number 894887306240

InnoDB: Doing recovery: scanned up to log sequence number 894892549120

InnoDB: Doing recovery: scanned up to log sequence number 894897792000

InnoDB: Doing recovery: scanned up to log sequence number 894903034880

InnoDB: Doing recovery: scanned up to log sequence number 894908277760

InnoDB: Doing recovery: scanned up to log sequence number 894913520640

InnoDB: Doing recovery: scanned up to log sequence number 894918763520

InnoDB: Doing recovery: scanned up to log sequence number 894924006400

InnoDB: Doing recovery: scanned up to log sequence number 894929249280

InnoDB: Doing recovery: scanned up to log sequence number 894934492160

InnoDB: Doing recovery: scanned up to log sequence number 894939735040

InnoDB: Doing recovery: scanned up to log sequence number 894944977920

InnoDB: Doing recovery: scanned up to log sequence number 894950220800

InnoDB: Doing recovery: scanned up to log sequence number 894955463680

InnoDB: Doing recovery: scanned up to log sequence number 894960706560

InnoDB: Doing recovery: scanned up to log sequence number 894965949440

InnoDB: Doing recovery: scanned up to log sequence number 894971192320

InnoDB: Doing recovery: scanned up to log sequence number 894976435200

InnoDB: Doing recovery: scanned up to log sequence number 894981678080

InnoDB: Doing recovery: scanned up to log sequence number 894986920960

InnoDB: Doing recovery: scanned up to log sequence number 894992163840

InnoDB: Doing recovery: scanned up to log sequence number 894997406720

InnoDB: Doing recovery: scanned up to log sequence number 895002649600

InnoDB: Doing recovery: scanned up to log sequence number 895007892480

InnoDB: Doing recovery: scanned up to log sequence number 895013135360

InnoDB: Doing recovery: scanned up to log sequence number 895018378240

InnoDB: Doing recovery: scanned up to log sequence number 895023621120

InnoDB: Doing recovery: scanned up to log sequence number 895028864000

InnoDB: Doing recovery: scanned up to log sequence number 895034106880

InnoDB: Doing recovery: scanned up to log sequence number 895039349760

InnoDB: Doing recovery: scanned up to log sequence number 895044592640

InnoDB: Doing recovery: scanned up to log sequence number 895049835520

InnoDB: Doing recovery: scanned up to log sequence number 895055078400

InnoDB: Doing recovery: scanned up to log sequence number 895060321280

InnoDB: Doing recovery: scanned up to log sequence number 895065564160

InnoDB: Doing recovery: scanned up to log sequence number 895070807040

InnoDB: Doing recovery: scanned up to log sequence number 895076049920

InnoDB: Doing recovery: scanned up to log sequence number 895081292800

InnoDB: Doing recovery: scanned up to log sequence number 895086535680

InnoDB: Doing recovery: scanned up to log sequence number 895091778560

InnoDB: Doing recovery: scanned up to log sequence number 895097021440

InnoDB: Doing recovery: scanned up to log sequence number 895102264320

InnoDB: Doing recovery: scanned up to log sequence number 895107507200

InnoDB: Doing recovery: scanned up to log sequence number 895112750080

InnoDB: Doing recovery: scanned up to log sequence number 895117992960

InnoDB: Doing recovery: scanned up to log sequence number 895123235840

InnoDB: Doing recovery: scanned up to log sequence number 895128478720

InnoDB: Doing recovery: scanned up to log sequence number 895133721600

InnoDB: Doing recovery: scanned up to log sequence number 895138964480

InnoDB: Doing recovery: scanned up to log sequence number 895141020708

140824 12:08:20 [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 245441500, file name ./emsow-bin.000030

140824 12:08:27 [Note] InnoDB: 128 rollback segment(s) are active.

140824 12:08:42 [ERROR] mysqld: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/var/lib/mysql/aria_log_control'

140824 12:08:42 [ERROR] Plugin 'Aria' init function returned error.

140824 12:08:42 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.

2014-08-24 12:08:42 7ff98841f740 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.

140824 12:08:42 [Note] InnoDB: Using mutexes to ref count buffer pool pages

140824 12:08:42 [Note] InnoDB: The InnoDB memory heap is disabled

140824 12:08:42 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

140824 12:08:42 [Note] InnoDB: Compressed tables use zlib 1.2.8

140824 12:08:42 [Note] InnoDB: Using Linux native AIO

140824 12:08:42 [Note] InnoDB: Using CPU crc32 instructions

140824 12:08:42 [Note] InnoDB: Initializing buffer pool, size = 8.0G

140824 12:08:42 [Note] InnoDB: Completed initialization of buffer pool

140824 12:08:43 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:08:43 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:08:43 [Note] InnoDB: Retrying to lock the first data file

140824 12:08:44 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:08:44 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:08:45 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:08:45 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:08:46 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:08:46 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:08:47 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:08:47 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:08:48 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:08:48 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:08:49 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:08:49 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:08:50 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:08:50 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:08:51 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:08:51 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:08:52 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:08:52 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:08:53 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:08:53 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:08:54 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:08:54 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:08:55 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:08:55 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:08:56 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:08:56 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:08:57 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:08:57 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:08:58 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:08:58 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:08:59 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:08:59 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:00 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:00 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:01 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:01 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:02 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:02 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:03 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:03 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:04 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:04 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:05 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:05 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:06 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:06 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:07 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:07 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:08 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:08 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:09 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:09 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:10 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:10 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:11 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:11 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:12 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:12 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:13 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:13 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:14 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:14 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:15 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:15 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:16 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:16 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:17 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:17 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:18 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:18 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:19 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:19 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:20 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:20 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:21 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:21 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:22 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:22 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:23 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:23 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:24 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:24 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:25 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:25 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:26 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:26 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:27 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:27 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:28 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:28 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:29 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:29 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:30 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:30 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:31 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:31 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:32 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:32 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:33 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:33 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:34 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:34 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:35 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:35 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:36 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:36 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:37 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:37 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:38 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:38 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:39 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:39 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:40 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:40 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:41 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:41 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:42 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:42 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:43 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:43 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:44 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:44 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:45 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:45 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:46 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:46 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:47 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:47 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:48 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:48 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:49 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:49 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:50 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:50 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:51 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:51 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:52 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:52 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:53 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:53 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:54 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:54 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:55 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:55 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:56 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:56 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:57 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:57 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:58 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:58 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:09:59 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:09:59 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:00 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:10:00 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:01 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:10:01 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:02 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:10:02 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:03 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:10:03 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:04 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:10:04 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:05 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:10:05 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:06 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:10:06 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:07 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:10:07 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:08 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:10:08 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:09 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:10:09 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:10 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:10:10 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:11 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:10:11 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:12 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:10:12 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:13 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:10:13 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:14 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:10:14 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:15 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:10:15 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:16 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:10:16 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:17 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:10:17 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:18 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:10:18 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:19 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:10:19 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:20 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:10:20 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:21 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:10:21 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:22 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:10:22 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:23 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:10:23 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:10:23 [Note] InnoDB: Unable to open the first data file

2014-08-24 12:10:23 7ff98841f740  InnoDB: Operating system error number 11 in a file operation.

InnoDB: Error number 11 means 'Resource temporarily unavailable'.

InnoDB: Some operating system error numbers are described at

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html

140824 12:10:23 [ERROR] InnoDB: Can't open './ibdata1'

140824 12:10:23 [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!

140824 12:10:23 [ERROR] Plugin 'InnoDB' init function returned error.

140824 12:10:23 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

140824 12:10:23 [ERROR] Unknown/unsupported storage engine: InnoDB

140824 12:10:23 [ERROR] Aborting

140824 12:10:23 [Note] /usr/sbin/mysqld: Shutdown complete

140824 12:11:31 [Note] CONNECT: Version 1.03.0002 Aug 19 2014 01:59:23

140824 12:11:31 [ERROR] mysqld: Can't lock aria control file '/var/lib/mysql/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds

140824 12:12:02 [ERROR] mysqld: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/var/lib/mysql/aria_log_control'

140824 12:12:02 [ERROR] Plugin 'Aria' init function returned error.

140824 12:12:02 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.

2014-08-24 12:12:02 7f03aa6f3740 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.

140824 12:12:02 [Note] InnoDB: Using mutexes to ref count buffer pool pages

140824 12:12:02 [Note] InnoDB: The InnoDB memory heap is disabled

140824 12:12:02 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

140824 12:12:02 [Note] InnoDB: Compressed tables use zlib 1.2.8

140824 12:12:02 [Note] InnoDB: Using Linux native AIO

140824 12:12:02 [Note] InnoDB: Using CPU crc32 instructions

140824 12:12:02 [Note] InnoDB: Initializing buffer pool, size = 8.0G

140824 12:12:03 [Note] InnoDB: Completed initialization of buffer pool

140824 12:12:03 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:03 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:03 [Note] InnoDB: Retrying to lock the first data file

140824 12:12:04 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:04 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:05 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:05 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:06 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:06 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:07 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:07 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:08 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:08 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:09 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:09 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:10 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:10 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:11 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:11 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:12 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:12 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:13 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:13 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:14 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:14 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:15 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:15 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:16 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:16 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:17 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:17 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:18 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:18 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:19 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:19 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:20 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:20 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:21 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:21 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:22 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:22 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:23 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:23 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:24 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:24 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:25 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:25 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:26 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:26 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:27 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:27 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:28 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:28 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:29 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:29 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:30 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:30 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:31 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:31 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:32 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:32 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:33 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:33 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:34 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:34 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:35 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:35 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:36 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:36 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:37 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:37 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:38 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:38 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:39 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:39 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:40 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:40 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:41 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:41 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:42 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:42 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:43 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:43 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:44 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:44 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:45 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:45 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:46 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:46 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:47 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:47 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:48 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:48 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:49 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:49 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:50 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:50 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:51 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:51 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:52 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:52 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:53 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:53 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:54 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:54 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:55 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:55 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:56 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:56 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:57 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:57 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:58 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:58 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:12:59 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:12:59 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:00 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:00 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:01 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:01 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:02 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:02 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:03 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:03 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:04 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:04 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:05 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:05 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:06 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:06 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:07 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:07 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:08 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:08 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:09 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:09 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:10 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:10 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:11 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:11 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:12 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:12 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:13 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:13 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:14 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:14 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:15 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:15 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:16 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:16 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:17 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:17 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:18 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:18 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:19 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:19 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:20 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:20 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:21 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:21 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:22 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:22 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:23 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:23 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:24 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:24 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:25 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:25 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:13:26 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

140824 12:13:26 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

140824 12:15:11 [Note] CONNECT: Version 1.03.0002 Aug 19 2014 01:59:23

2014-08-24 12:15:11 7f83b6dc4740 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.

140824 12:15:11 [Note] InnoDB: Using mutexes to ref count buffer pool pages

140824 12:15:11 [Note] InnoDB: The InnoDB memory heap is disabled

140824 12:15:11 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

140824 12:15:11 [Note] InnoDB: Compressed tables use zlib 1.2.8

140824 12:15:11 [Note] InnoDB: Using Linux native AIO

140824 12:15:11 [Note] InnoDB: Using CPU crc32 instructions

140824 12:15:11 [Note] InnoDB: Initializing buffer pool, size = 8.0G

140824 12:15:11 [Note] InnoDB: Completed initialization of buffer pool

140824 12:15:11 [Note] InnoDB: Highest supported file format is Barracuda.

140824 12:15:11 [Note] InnoDB: Log scan progressed past the checkpoint lsn 894383990245

140824 12:15:11 [Note] InnoDB: Database was not shutdown normally!

140824 12:15:11 [Note] InnoDB: Starting crash recovery.

140824 12:15:11 [Note] InnoDB: Reading tablespace information from the .ibd files...

140824 12:15:27 [Note] InnoDB: Restoring possible half-written data pages 

140824 12:15:27 [Note] InnoDB: from the doublewrite buffer...

InnoDB: Doing recovery: scanned up to log sequence number 894389232640

InnoDB: Doing recovery: scanned up to log sequence number 894394475520

InnoDB: Doing recovery: scanned up to log sequence number 894399718400

InnoDB: Doing recovery: scanned up to log sequence number 894404961280

InnoDB: Doing recovery: scanned up to log sequence number 894410204160

InnoDB: Doing recovery: scanned up to log sequence number 894415447040

InnoDB: Doing recovery: scanned up to log sequence number 894420689920

InnoDB: Doing recovery: scanned up to log sequence number 894425932800

InnoDB: Doing recovery: scanned up to log sequence number 894431175680

InnoDB: Doing recovery: scanned up to log sequence number 894436418560

InnoDB: Doing recovery: scanned up to log sequence number 894441661440

InnoDB: Doing recovery: scanned up to log sequence number 894446904320

InnoDB: Doing recovery: scanned up to log sequence number 894452147200

InnoDB: Doing recovery: scanned up to log sequence number 894457390080

InnoDB: Doing recovery: scanned up to log sequence number 894462632960

InnoDB: Doing recovery: scanned up to log sequence number 894467875840

InnoDB: Doing recovery: scanned up to log sequence number 894473118720

InnoDB: Doing recovery: scanned up to log sequence number 894478361600

InnoDB: Doing recovery: scanned up to log sequence number 894483604480

InnoDB: Doing recovery: scanned up to log sequence number 894488847360

InnoDB: Doing recovery: scanned up to log sequence number 894494090240

InnoDB: Doing recovery: scanned up to log sequence number 894499333120

InnoDB: Doing recovery: scanned up to log sequence number 894504576000

InnoDB: Doing recovery: scanned up to log sequence number 894509818880

InnoDB: Doing recovery: scanned up to log sequence number 894515061760

InnoDB: Doing recovery: scanned up to log sequence number 894520304640

InnoDB: Doing recovery: scanned up to log sequence number 894525547520

InnoDB: Doing recovery: scanned up to log sequence number 894530790400

InnoDB: Doing recovery: scanned up to log sequence number 894536033280

InnoDB: Doing recovery: scanned up to log sequence number 894541276160

InnoDB: Doing recovery: scanned up to log sequence number 894546519040

InnoDB: Doing recovery: scanned up to log sequence number 894551761920

InnoDB: Doing recovery: scanned up to log sequence number 894557004800

InnoDB: Doing recovery: scanned up to log sequence number 894562247680

InnoDB: Doing recovery: scanned up to log sequence number 894567490560

InnoDB: Doing recovery: scanned up to log sequence number 894572733440

InnoDB: Doing recovery: scanned up to log sequence number 894577976320

InnoDB: Doing recovery: scanned up to log sequence number 894583219200

InnoDB: Doing recovery: scanned up to log sequence number 894588462080

InnoDB: Doing recovery: scanned up to log sequence number 894593704960

InnoDB: Doing recovery: scanned up to log sequence number 894598947840

InnoDB: Doing recovery: scanned up to log sequence number 894604190720

InnoDB: Doing recovery: scanned up to log sequence number 894609433600

InnoDB: Doing recovery: scanned up to log sequence number 894614676480

InnoDB: Doing recovery: scanned up to log sequence number 894619919360

InnoDB: Doing recovery: scanned up to log sequence number 894625162240

InnoDB: Doing recovery: scanned up to log sequence number 894630405120

InnoDB: Doing recovery: scanned up to log sequence number 894635648000

InnoDB: Doing recovery: scanned up to log sequence number 894640890880

InnoDB: Doing recovery: scanned up to log sequence number 894646133760

InnoDB: Doing recovery: scanned up to log sequence number 894651376640

InnoDB: Doing recovery: scanned up to log sequence number 894656619520

InnoDB: Doing recovery: scanned up to log sequence number 894661862400

InnoDB: Doing recovery: scanned up to log sequence number 894667105280

InnoDB: Doing recovery: scanned up to log sequence number 894672348160

InnoDB: Doing recovery: scanned up to log sequence number 894677591040

InnoDB: Doing recovery: scanned up to log sequence number 894682833920

InnoDB: Doing recovery: scanned up to log sequence number 894688076800

InnoDB: Doing recovery: scanned up to log sequence number 894693319680

InnoDB: Doing recovery: scanned up to log sequence number 894698562560

InnoDB: Doing recovery: scanned up to log sequence number 894703805440

InnoDB: Doing recovery: scanned up to log sequence number 894709048320

InnoDB: Doing recovery: scanned up to log sequence number 894714291200

InnoDB: Doing recovery: scanned up to log sequence number 894719534080

InnoDB: Doing recovery: scanned up to log sequence number 894724776960

InnoDB: Doing recovery: scanned up to log sequence number 894730019840

InnoDB: Doing recovery: scanned up to log sequence number 894735262720

InnoDB: Doing recovery: scanned up to log sequence number 894740505600

InnoDB: Doing recovery: scanned up to log sequence number 894745748480

InnoDB: Doing recovery: scanned up to log sequence number 894750991360

InnoDB: Doing recovery: scanned up to log sequence number 894756234240

InnoDB: Doing recovery: scanned up to log sequence number 894761477120

InnoDB: Doing recovery: scanned up to log sequence number 894766720000

InnoDB: Doing recovery: scanned up to log sequence number 894771962880

InnoDB: Doing recovery: scanned up to log sequence number 894777205760

InnoDB: Doing recovery: scanned up to log sequence number 894782448640

InnoDB: Doing recovery: scanned up to log sequence number 894787691520

InnoDB: Doing recovery: scanned up to log sequence number 894792934400

InnoDB: Doing recovery: scanned up to log sequence number 894798177280

InnoDB: Doing recovery: scanned up to log sequence number 894803420160

InnoDB: Doing recovery: scanned up to log sequence number 894808663040

InnoDB: Doing recovery: scanned up to log sequence number 894813905920

InnoDB: Doing recovery: scanned up to log sequence number 894819148800

InnoDB: Doing recovery: scanned up to log sequence number 894824391680

InnoDB: Doing recovery: scanned up to log sequence number 894829634560

InnoDB: Doing recovery: scanned up to log sequence number 894834877440

InnoDB: Doing recovery: scanned up to log sequence number 894840120320

InnoDB: Doing recovery: scanned up to log sequence number 894845363200

InnoDB: Doing recovery: scanned up to log sequence number 894850606080

InnoDB: Doing recovery: scanned up to log sequence number 894855848960

InnoDB: Doing recovery: scanned up to log sequence number 894861091840

InnoDB: Doing recovery: scanned up to log sequence number 894866334720

InnoDB: Doing recovery: scanned up to log sequence number 894871577600

InnoDB: Doing recovery: scanned up to log sequence number 894876820480

InnoDB: Doing recovery: scanned up to log sequence number 894882063360

InnoDB: Doing recovery: scanned up to log sequence number 894887306240

InnoDB: Doing recovery: scanned up to log sequence number 894892549120

InnoDB: Doing recovery: scanned up to log sequence number 894897792000

InnoDB: Doing recovery: scanned up to log sequence number 894903034880

InnoDB: Doing recovery: scanned up to log sequence number 894908277760

InnoDB: Doing recovery: scanned up to log sequence number 894913520640

InnoDB: Doing recovery: scanned up to log sequence number 894918763520

InnoDB: Doing recovery: scanned up to log sequence number 894924006400

InnoDB: Doing recovery: scanned up to log sequence number 894929249280

InnoDB: Doing recovery: scanned up to log sequence number 894934492160

InnoDB: Doing recovery: scanned up to log sequence number 894939735040

InnoDB: Doing recovery: scanned up to log sequence number 894944977920

InnoDB: Doing recovery: scanned up to log sequence number 894950220800

InnoDB: Doing recovery: scanned up to log sequence number 894955463680

InnoDB: Doing recovery: scanned up to log sequence number 894960706560

InnoDB: Doing recovery: scanned up to log sequence number 894965949440

InnoDB: Doing recovery: scanned up to log sequence number 894971192320

InnoDB: Doing recovery: scanned up to log sequence number 894976435200

InnoDB: Doing recovery: scanned up to log sequence number 894981678080

InnoDB: Doing recovery: scanned up to log sequence number 894986920960

InnoDB: Doing recovery: scanned up to log sequence number 894992163840

InnoDB: Doing recovery: scanned up to log sequence number 894997406720

InnoDB: Doing recovery: scanned up to log sequence number 895002649600

InnoDB: Doing recovery: scanned up to log sequence number 895007892480

InnoDB: Doing recovery: scanned up to log sequence number 895013135360

InnoDB: Doing recovery: scanned up to log sequence number 895018378240

InnoDB: Doing recovery: scanned up to log sequence number 895023621120

InnoDB: Doing recovery: scanned up to log sequence number 895028864000

InnoDB: Doing recovery: scanned up to log sequence number 895034106880

InnoDB: Doing recovery: scanned up to log sequence number 895039349760

InnoDB: Doing recovery: scanned up to log sequence number 895044592640

InnoDB: Doing recovery: scanned up to log sequence number 895049835520

InnoDB: Doing recovery: scanned up to log sequence number 895055078400

InnoDB: Doing recovery: scanned up to log sequence number 895060321280

InnoDB: Doing recovery: scanned up to log sequence number 895065564160

InnoDB: Doing recovery: scanned up to log sequence number 895070807040

InnoDB: Doing recovery: scanned up to log sequence number 895076049920

InnoDB: Doing recovery: scanned up to log sequence number 895081292800

InnoDB: Doing recovery: scanned up to log sequence number 895086535680

InnoDB: Doing recovery: scanned up to log sequence number 895091778560

InnoDB: Doing recovery: scanned up to log sequence number 895097021440

InnoDB: Doing recovery: scanned up to log sequence number 895102264320

InnoDB: Doing recovery: scanned up to log sequence number 895107507200

InnoDB: Doing recovery: scanned up to log sequence number 895112750080

InnoDB: Doing recovery: scanned up to log sequence number 895117992960

InnoDB: Doing recovery: scanned up to log sequence number 895123235840

InnoDB: Doing recovery: scanned up to log sequence number 895128478720

InnoDB: Doing recovery: scanned up to log sequence number 895133721600

InnoDB: Doing recovery: scanned up to log sequence number 895138964480

InnoDB: Doing recovery: scanned up to log sequence number 895141020718

140824 12:15:45 [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 245441500, file name ./emsow-bin.000030

140824 12:16:09 [Note] InnoDB: 128 rollback segment(s) are active.

140824 12:18:38 [Note] InnoDB: Waiting for purge to start

140824 12:18:38 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.19-67.0 started; log sequence number 895141020718

140824 12:18:38 [Note] Recovering after a crash using emsow-bin

140824 12:18:44 [Note] Starting crash recovery...

140824 12:18:44 [Note] Crash recovery finished.