140519 14:54:05 [ERROR] mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

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: 5.5.33a-MariaDB-1~precise-log
key_buffer_size=104857600
read_buffer_size=131072
max_used_connections=4
max_threads=5002
thread_count=2
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 11076066 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x7fdc03772000
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 = 0x7fdc4d0f8e10 thread_stack 0x48000
??:0(??)[0x7fdc4db39f2b]
??:0(??)[0x7fdc4d7600f1]
??:0(??)[0x7fdc4c608cb0]
??:0(??)[0x7fdc4d6c136b]
??:0(??)[0x7fdc4d5fc5c3]
??:0(??)[0x7fdc4d5fcc5d]
??:0(??)[0x7fdc4d612cb7]
??:0(??)[0x7fdc4d664225]
??:0(??)[0x7fdc4d668fab]
??:0(??)[0x7fdc4d66d873]
??:0(??)[0x7fdc4d6153d2]
??:0(??)[0x7fdc4d61de49]
??:0(??)[0x7fdc4d622fc7]
??:0(??)[0x7fdc4d625abe]
??:0(??)[0x7fdc4d6e2753]
??:0(??)[0x7fdc4d6e28b1]
??:0(??)[0x7fdc4c600e9a]
??:0(??)[0x7fdc4b6f8ccd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7fdbfe41f018): is an invalid pointer
Connection ID (thread ID): 23
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=off

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.
140519 14:54:05 mysqld_safe Number of processes running now: 0
140519 14:54:05 mysqld_safe mysqld restarted
140519 14:54:05 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
/usr/sbin/mysqld: Query cache is disabled (resize or similar command in progress); repeat this command later
140519 14:54:05 [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.
140519 14:54:05 InnoDB: The InnoDB memory heap is disabled
140519 14:54:05 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140519 14:54:05 InnoDB: Compressed tables use zlib 1.2.3.4
140519 14:54:05 InnoDB: Using Linux native AIO
140519 14:54:05 InnoDB: Initializing buffer pool, size = 500.0M
140519 14:54:05 InnoDB: Completed initialization of buffer pool
140519 14:54:05 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 5387850678166
140519 14:54:05  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 5387850705697
140519 14:54:06  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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 45029, file name /home/workbooks/database_backups/replication/mysql-bin.000096
140519 14:54:06  InnoDB: Waiting for the background threads to start
140519 14:54:07 Percona XtraDB (http://www.percona.com) 5.5.33a-MariaDB-31.1 started; log sequence number 5387850705697
140519 14:54:07 [Note] Recovering after a crash using /home/workbooks/database_backups/replication/mysql-bin
140519 14:54:07 [Note] Starting crash recovery...
140519 14:54:07 [Note] Crash recovery finished.
140519 14:54:07 [Note] Server socket created on IP: '0.0.0.0'.
140519 14:54:07 [Warning] 'user' entry 'root@test07' ignored in --skip-name-resolve mode.
140519 14:54:07 [Warning] 'user' entry 'root@sandbox1a.svc.workbooks.com.svc.workbooks.com' ignored in --skip-name-resolve mode.
140519 14:54:07 [Warning] 'user' entry 'root@172.16.7.131
127.0.0.1' ignored in --skip-name-resolve mode.
140519 14:54:07 [Warning] 'proxies_priv' entry '@ root@test07' ignored in --skip-name-resolve mode.
140519 14:54:07 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.33a-MariaDB-1~precise-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution