Sep  7 10:03:56 TR-IT-SERVER mysqld: 150907 10:03:56  InnoDB: Database was not shut down normally!
Sep  7 10:03:56 TR-IT-SERVER mysqld: InnoDB: Starting crash recovery.
Sep  7 10:03:56 TR-IT-SERVER mysqld: InnoDB: Reading tablespace information from the .ibd files...
Sep  7 10:03:56 TR-IT-SERVER mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite
Sep  7 10:03:56 TR-IT-SERVER mysqld: InnoDB: buffer...
Sep  7 10:03:56 TR-IT-SERVER mysqld: InnoDB: Doing recovery: scanned up to log sequence number 5814639152
Sep  7 10:03:56 TR-IT-SERVER mysqld: 150907 10:03:56  InnoDB: Starting an apply batch of log records to the database...
Sep  7 10:03:56 TR-IT-SERVER mysqld: InnoDB: Progress in percents: 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
Sep  7 10:03:56 TR-IT-SERVER mysqld: InnoDB: Apply batch completed
Sep  7 10:03:56 TR-IT-SERVER mysqld: 150907 10:03:56  InnoDB: Waiting for the background threads to start
Sep  7 10:03:57 TR-IT-SERVER mysqld: 150907 10:03:57 InnoDB: 5.5.41 started; log sequence number 5814639152
Sep  7 10:03:57 TR-IT-SERVER mysqld: 150907 10:03:57 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
Sep  7 10:03:57 TR-IT-SERVER mysqld: 150907 10:03:57 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
Sep  7 10:03:57 TR-IT-SERVER mysqld: 150907 10:03:57 [Note] Server socket created on IP: '127.0.0.1'.
Sep  7 10:03:57 TR-IT-SERVER mysqld: 150907 10:03:57  InnoDB: Assertion failure in thread 140200057038592 in file trx0purge.c line 840
Sep  7 10:03:57 TR-IT-SERVER mysqld: InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no
Sep  7 10:03:57 TR-IT-SERVER mysqld: InnoDB: We intentionally generate a memory trap.
Sep  7 10:03:57 TR-IT-SERVER mysqld: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
Sep  7 10:03:57 TR-IT-SERVER mysqld: InnoDB: If you get repeated assertion failures or crashes, even
Sep  7 10:03:57 TR-IT-SERVER mysqld: InnoDB: immediately after the mysqld startup, there may be
Sep  7 10:03:57 TR-IT-SERVER mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to
Sep  7 10:03:57 TR-IT-SERVER mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
Sep  7 10:03:57 TR-IT-SERVER mysqld: InnoDB: about forcing recovery.
Sep  7 10:03:57 TR-IT-SERVER mysqld: 10:03:57 UTC - mysqld got signal 6 ;
Sep  7 10:03:57 TR-IT-SERVER mysqld: This could be because you hit a bug. It is also possible that this binary
Sep  7 10:03:57 TR-IT-SERVER mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Sep  7 10:03:57 TR-IT-SERVER mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Sep  7 10:03:57 TR-IT-SERVER mysqld: We will try our best to scrape up some info that will hopefully help
Sep  7 10:03:57 TR-IT-SERVER mysqld: diagnose the problem, but since we have already crashed,
Sep  7 10:03:57 TR-IT-SERVER mysqld: something is definitely wrong and this may fail.
Sep  7 10:03:57 TR-IT-SERVER mysqld:
Sep  7 10:03:57 TR-IT-SERVER mysqld: key_buffer_size=16777216
Sep  7 10:03:57 TR-IT-SERVER mysqld: read_buffer_size=131072
Sep  7 10:03:57 TR-IT-SERVER mysqld: max_used_connections=0
Sep  7 10:03:57 TR-IT-SERVER mysqld: max_threads=151
Sep  7 10:03:57 TR-IT-SERVER mysqld: thread_count=0
Sep  7 10:03:57 TR-IT-SERVER mysqld: connection_count=0
Sep  7 10:03:57 TR-IT-SERVER mysqld: It is possible that mysqld could use up to
Sep  7 10:03:57 TR-IT-SERVER mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346700 K  bytes of memory
Sep  7 10:03:57 TR-IT-SERVER mysqld: Hope that's ok; if not, decrease some variables in the equation.
Sep  7 10:03:57 TR-IT-SERVER mysqld:
Sep  7 10:03:57 TR-IT-SERVER mysqld: Thread pointer: 0x0
Sep  7 10:03:57 TR-IT-SERVER mysqld: Attempting backtrace. You can use the following information to find out
Sep  7 10:03:57 TR-IT-SERVER mysqld: where mysqld died. If you see no messages after this, something went
Sep  7 10:03:57 TR-IT-SERVER mysqld: terribly wrong...
Sep  7 10:03:57 TR-IT-SERVER mysqld: stack_bottom = 0 thread_stack 0x30000
Sep  7 10:03:57 TR-IT-SERVER mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x29)[0x7f82f39826d9]
Sep  7 10:03:57 TR-IT-SERVER mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x3d8)[0x7f82f38699a8]
Sep  7 10:03:57 TR-IT-SERVER mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0xf0a0)[0x7f82f30170a0]
Sep  7 10:03:57 TR-IT-SERVER mysqld: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7f82f18a9165]
Sep  7 10:03:57 TR-IT-SERVER mysqld: /lib/x86_64-linux-gnu/libc.so.6(abort+0x180)[0x7f82f18ac3e0]
Sep  7 10:03:57 TR-IT-SERVER mysqld: /usr/sbin/mysqld(+0x5e4dc5)[0x7f82f3a2adc5]
Sep  7 10:03:57 TR-IT-SERVER mysqld: /usr/sbin/mysqld(+0x5e51c9)[0x7f82f3a2b1c9]
Sep  7 10:03:57 TR-IT-SERVER mysqld: /usr/sbin/mysqld(+0x6a791f)[0x7f82f3aed91f]
Sep  7 10:03:57 TR-IT-SERVER mysqld: /usr/sbin/mysqld(+0x69e43b)[0x7f82f3ae443b]
Sep  7 10:03:57 TR-IT-SERVER mysqld: /usr/sbin/mysqld(+0x5e6319)[0x7f82f3a2c319]
Sep  7 10:03:57 TR-IT-SERVER mysqld: /usr/sbin/mysqld(+0x5d7dec)[0x7f82f3a1ddec]
Sep  7 10:03:57 TR-IT-SERVER mysqld: /usr/sbin/mysqld(+0x5dbff3)[0x7f82f3a21ff3]
Sep  7 10:03:57 TR-IT-SERVER mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50)[0x7f82f300eb50]
Sep  7 10:03:57 TR-IT-SERVER mysqld: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f82f195295d]
Sep  7 10:03:57 TR-IT-SERVER mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Sep  7 10:03:57 TR-IT-SERVER mysqld: information that should help you find out what is causing the crash.