Here is the error log. Memory shouldn't be an issue, the box has 30GB, innodb allocate 12GB only.
120731 12:30:05 - 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.
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.
key_buffer_size=4294967296
read_buffer_size=1048576
max_used_connections=10
max_threads=300
threads_connected=3
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4811753 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x7f2ee40008c0
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 = 0x7f332c22fe58 thread_stack 0x40000
/usr/local/mysql/libexec/mysqld(my_print_stacktrace+0x29) [0x83b379]
/usr/local/mysql/libexec/mysqld(handle_segfault+0x3db) [0x5a8afb]
/lib64/libpthread.so.0() [0x314c60f4a0]
/lib64/libc.so.6() [0x314bf2ff7f]
/usr/local/mysql/libexec/mysqld(String::append(char const*)+0x30) [0x5a60f0]
/usr/local/mysql/libexec/mysqld() [0x6a385c]
/usr/local/mysql/libexec/mysqld(mysql_load(THD*, sql_exchange*, TABLE_LIST*, List<Item>&, List<Item>&, List<Item>&, enum_duplicates, bool, bool)+0x16c2) [0x6a6542]
/usr/local/mysql/libexec/mysqld(Load_log_event::do_apply_event(st_net*, Relay_log_info const*, bool)+0x70e) [0x66358e]
/usr/local/mysql/libexec/mysqld(Execute_load_log_event::do_apply_event(Relay_log_info const*)+0x3c0) [0x668690]
/usr/local/mysql/libexec/mysqld(apply_event_and_update_pos(Log_event*, THD*, Relay_log_info*)+0xf5) [0x6c9ec5]
/usr/local/mysql/libexec/mysqld(handle_slave_sql+0x6a2) [0x6cab42]
/lib64/libpthread.so.0() [0x314c6077f1]
/lib64/libc.so.6(clone+0x6d) [0x314bee5ccd]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x7f2ee46beb68 is an invalid pointer
thd->thread_id=62607
thd->killed=NOT_KILLED
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.
120731 12:30:05 mysqld_safe Number of processes running now: 0
120731 12:30:05 mysqld_safe mysqld restarted
120731 12:30:05 [Warning] 'for replication startup options' is deprecated and will be removed in a future release. Please use ''CHANGE MASTER'' instead.
120731 12:30:05 [Warning] '--log_slow_queries' is deprecated and will be removed in a future release. Please use ''--slow_query_log'/'--slow_query_log_file'' instead.
120731 12:30:05 [Warning] '--log-long-format' is deprecated and will be removed in a future release. Please use '--log-short-format' instead.
120731 12:30:05 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
120731 12:30:05 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=mysqld-bin' to avoid this problem.
120731 12:30:06 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
120731 12:30:07 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 15811387353
120731 12:30:08 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 15811388239
120731 12:30:09 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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: In a MySQL replication slave the last master binlog file
InnoDB: position 0 74737409, file name besdb11-bin.039574
InnoDB: Last MySQL binlog file position 0 106, file name ./mysqld-bin.000010
120731 12:30:13 InnoDB Plugin 1.0.6 started; log sequence number 15811388239
120731 12:30:13 [Note] Recovering after a crash using mysqld-bin
120731 12:30:13 [Note] Starting crash recovery...
120731 12:30:13 [Note] Crash recovery finished.
120731 12:30:13 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=mysqld-relay-bin' to avoid this problem.
120731 12:30:13 [Note] Event Scheduler: Loaded 0 events
120731 12:30:13 [Note] /usr/local/mysql/libexec/mysqld: ready for connections.
Version: '5.1.45-log' socket: '/var/tmp/mysql.sock' port: 30306 Source distribution
120731 12:36:33 [Note] Slave SQL thread initialized, starting replication in log 'besdb11-bin.041473' at position 99144547, relay log './mysqld-relay-bin.003815' position: 101666003
120731 12:36:33 [ERROR] Slave SQL: Error 'Table 'tmpdb.genares_image_20120731123005' doesn't exist' running LOAD DATA INFILE on table 'genares_image_20120731123005'. Default database: '', Error_code: 1146
120731 12:36:33 [Warning] Slave: Table 'tmpdb.genares_image_20120731123005' doesn't exist Error_code: 1146
120731 12:36:33 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'besdb11-bin.041473' position 99144547