150914  5:35:19  InnoDB: Page checksum 1437545568 (32bit_calc: 4141665906), prior-to-4.0.14-form checksum 2372714266
InnoDB: stored checksum 4278203614, prior-to-4.0.14-form stored checksum 996399670
InnoDB: Page lsn 15 3199628717, low 4 bytes of lsn at page end 3199628717
InnoDB: Page number (if stored to page already) 421180,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an index page where index id is 213
InnoDB: (index "history_1" of table "zabbix"."history")
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 421180.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
150914  5:35:19  InnoDB: Assertion failure in thread 139866474014464 in file buf0buf.c line 4018
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
150914  5:35:19 [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: 5.5.33-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 136597 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0
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 = 0x0 thread_stack 0x48000
??:0(??)[0xa60126]
??:0(??)[0x6de3d5]
??:0(??)[0x7f35587ee1f0]
??:0(??)[0x7f3557822065]
??:0(??)[0x7f35578234e8]
??:0(??)[0x88c33c]
??:0(??)[0x89dcc0]
??:0(??)[0x89e7fc]
??:0(??)[0x8883a5]
??:0(??)[0x86c6d0]
??:0(??)[0x86d369]
??:0(??)[0x8248a6]
??:0(??)[0x93a145]
??:0(??)[0x93ae88]
??:0(??)[0x930758]
??:0(??)[0x845610]
??:0(??)[0x839f5c]
??:0(??)[0x7f35587e6e0f]
??:0(??)[0x7f35578d60dd]
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.
150914 05:35:19 mysqld_safe mysqld from pid file /var/run/mysql/mysqld.pid ended