Dec  4 07:55:21 srv-svc03 mysqld_safe: Starting mysqld daemon with databases from /data/mysql
Dec  4 07:55:21 srv-svc03 mysqld: 181204  7:55:21 [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.
Dec  4 07:55:21 srv-svc03 mysqld: 181204  7:55:21 [Note] /usr/sbin/mysqld (mysqld 5.5.60-0+deb7u1) starting as process 3095 ...
Dec  4 07:55:21 srv-svc03 mysqld: 181204  7:55:21 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
Dec  4 07:55:21 srv-svc03 mysqld: 181204  7:55:21 [Note] Plugin 'FEDERATED' is disabled.
Dec  4 07:55:21 srv-svc03 mysqld: 181204  7:55:21 InnoDB: The InnoDB memory heap is disabled
Dec  4 07:55:21 srv-svc03 mysqld: 181204  7:55:21 InnoDB: Mutexes and rw_locks use GCC atomic builtins
Dec  4 07:55:21 srv-svc03 mysqld: 181204  7:55:21 InnoDB: Compressed tables use zlib 1.2.7
Dec  4 07:55:21 srv-svc03 mysqld: 181204  7:55:21 InnoDB: Using Linux native AIO
Dec  4 07:55:21 srv-svc03 mysqld: 181204  7:55:21 InnoDB: Initializing buffer pool, size = 128.0M
Dec  4 07:55:21 srv-svc03 mysqld: 181204  7:55:21 InnoDB: Completed initialization of buffer pool
Dec  4 07:55:21 srv-svc03 mysqld: 181204  7:55:21 InnoDB: highest supported file format is Barracuda.
Dec  4 07:55:21 srv-svc03 mysqld: InnoDB: Log scan progressed past the checkpoint lsn 9850189128906
Dec  4 07:55:21 srv-svc03 mysqld: 181204  7:55:21  InnoDB: Database was not shut down normally!
Dec  4 07:55:21 srv-svc03 mysqld: InnoDB: Starting crash recovery.
Dec  4 07:55:21 srv-svc03 mysqld: InnoDB: Reading tablespace information from the .ibd files...
Dec  4 07:55:21 srv-svc03 mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite
Dec  4 07:55:21 srv-svc03 mysqld: InnoDB: buffer...
Dec  4 07:55:22 srv-svc03 mysqld: InnoDB: Doing recovery: scanned up to log sequence number 9850190919680
Dec  4 07:55:22 srv-svc03 mysqld: 181204  7:55:22  InnoDB: Error: page 1 log sequence number 9850196018772
Dec  4 07:55:22 srv-svc03 mysqld: InnoDB: is in the future! Current system log sequence number 9850190919646.
Dec  4 07:55:22 srv-svc03 mysqld: InnoDB: Your database may be corrupt or you may have copied the InnoDB
Dec  4 07:55:22 srv-svc03 mysqld: InnoDB: tablespace but not the InnoDB log files. See
Dec  4 07:55:22 srv-svc03 mysqld: InnoDB:  http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html 
Dec  4 07:55:22 srv-svc03 mysqld: InnoDB: for more information.
Dec  4 07:55:23 srv-svc03 mysqld: 181204  7:55:23  InnoDB: Error: page 0 log sequence number 9850196018838
Dec  4 07:55:23 srv-svc03 mysqld: InnoDB: is in the future! Current system log sequence number 9850190919646.
Dec  4 07:55:23 srv-svc03 mysqld: InnoDB: Your database may be corrupt or you may have copied the InnoDB
Dec  4 07:55:23 srv-svc03 mysqld: InnoDB: tablespace but not the InnoDB log files. See
Dec  4 07:55:23 srv-svc03 mysqld: InnoDB:  http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html 
Dec  4 07:55:23 srv-svc03 mysqld: InnoDB: for more information.
Dec  4 07:55:23 srv-svc03 mysqld: 181204  7:55:23  InnoDB: Starting an apply batch of log records to the database...
Dec  4 07:55:23 srv-svc03 mysqld: InnoDB: Progress in percents: 04:55:23 UTC - mysqld got signal 11 ;
Dec  4 07:55:23 srv-svc03 mysqld: This could be because you hit a bug. It is also possible that this binary
Dec  4 07:55:23 srv-svc03 mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Dec  4 07:55:23 srv-svc03 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Dec  4 07:55:23 srv-svc03 mysqld: We will try our best to scrape up some info that will hopefully help
Dec  4 07:55:23 srv-svc03 mysqld: diagnose the problem, but since we have already crashed, 
Dec  4 07:55:23 srv-svc03 mysqld: something is definitely wrong and this may fail.
Dec  4 07:55:23 srv-svc03 mysqld: 
Dec  4 07:55:23 srv-svc03 mysqld: key_buffer_size=16777216
Dec  4 07:55:23 srv-svc03 mysqld: read_buffer_size=131072
Dec  4 07:55:23 srv-svc03 mysqld: max_used_connections=0
Dec  4 07:55:23 srv-svc03 mysqld: max_threads=151
Dec  4 07:55:23 srv-svc03 mysqld: thread_count=0
Dec  4 07:55:23 srv-svc03 mysqld: connection_count=0
Dec  4 07:55:23 srv-svc03 mysqld: It is possible that mysqld could use up to 
Dec  4 07:55:23 srv-svc03 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346701 K  bytes of memory
Dec  4 07:55:23 srv-svc03 mysqld: Hope that's ok; if not, decrease some variables in the equation.
Dec  4 07:55:23 srv-svc03 mysqld: 
Dec  4 07:55:23 srv-svc03 mysqld: 1 Thread pointer: 0x0
Dec  4 07:55:23 srv-svc03 mysqld: Attempting backtrace. You can use the following information to find out
Dec  4 07:55:23 srv-svc03 mysqld: where mysqld died. If you see no messages after this, something went
Dec  4 07:55:23 srv-svc03 mysqld: terribly wrong...
Dec  4 07:55:23 srv-svc03 kernel: [   20.226030] mysqld[3100]: segfault at fffffffffffffffb ip 00007f67234399a5 sp 00007f6714c40bd0 error 5 in mysqld[7f6722dbb000+a80000]
Dec  4 07:55:23 srv-svc03 mysqld: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 
Dec  4 07:55:23 srv-svc03 mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended