130614 15:25:16  InnoDB: Assertion failure in thread 47611033717056 in file buf0buf.c line 4173

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.

130614 15:25:16 [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.29-MariaDB-log

key_buffer_size=16777216

read_buffer_size=262144

max_used_connections=394

max_threads=1002

thread_count=49

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2339107 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 0x30000

(my_addr_resolve failure: fork)

/usr/sbin/mysqld(my_print_stacktrace+0x2e) [0xa931de]

/usr/sbin/mysqld(handle_fatal_signal+0x44c) [0x6d0bbc]

/lib64/libpthread.so.0 [0x2b42429abca0]

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

/lib64/libc.so.6(abort+0x110) [0x2b42439c9d70]

/usr/sbin/mysqld [0x8cc398]

/usr/sbin/mysqld [0x902f5d]

/usr/sbin/mysqld [0x87d53e]

/lib64/libpthread.so.0 [0x2b42429a383d]

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

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.

130614 15:25:21 mysqld_safe Number of processes running now: 0

130614 15:25:21 mysqld_safe mysqld restarted