MySQL crash

130712  6:44:35 [Note] Event Scheduler: Loaded 2 events
130712  6:44:35 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.30-cll'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL)
10:44:35 UTC - 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=805306368
read_buffer_size=268435456
max_used_connections=1
max_threads=500
thread_count=1
connection_count=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 262936275 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x80d59c0
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 = 7f2afb00de58 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7a1af5]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x67e9d4]
/lib64/libpthread.so.0[0x3d6660f500]
/lib64/libc.so.6[0x3d65f27a9a]
/usr/sbin/mysqld[0x8b7a6f]
/usr/sbin/mysqld[0x8ad6cd]
/usr/sbin/mysqld[0x8a7b74]
/usr/sbin/mysqld[0x81259b]
/usr/sbin/mysqld(_ZN7handler7ha_openEP5TABLEPKcii+0x3e)[0x680ede]
/usr/sbin/mysqld(_Z21open_table_from_shareP3THDP11TABLE_SHAREPKcjjjP5TABLEb+0x58c)[0x5fe0bc]
/usr/sbin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP11st_mem_rootP18Open_table_context+0xc53)[0x552a53]
/usr/sbin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0x48d)[0x55389d]
/usr/sbin/mysqld(_Z20open_and_lock_tablesP3THDP10TABLE_LISTbjP19Prelocking_strategy+0x44)[0x5542e4]
/usr/sbin/mysqld[0x581c54]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1216)[0x585b06]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x330)[0x5894c0]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x137d)[0x58a8dd]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0xd7)[0x6230a7]
/usr/sbin/mysqld(handle_one_connection+0x51)[0x6231e1]
/lib64/libpthread.so.0[0x3d66607851]
/lib64/libc.so.6(clone+0x6d)[0x3d65ee890d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (82e9eb0): SELECT COUNT(*) AS id FROM jobposts WHERE  jobtitle LIKE '%coordinatori%'  AND city LIKE '%sassari%'
Connection ID (thread ID): 1
Status: 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.
130712 06:44:35 mysqld_safe Number of processes running now: 0
130712 06:44:35 mysqld_safe mysqld restarted
130712  6:44:35 [Note] Plugin 'FEDERATED' is disabled.
130712  6:44:35 InnoDB: The InnoDB memory heap is disabled
130712  6:44:35 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130712  6:44:35 InnoDB: Compressed tables use zlib 1.2.3
130712  6:44:35 InnoDB: Using Linux native AIO
130712  6:44:35 InnoDB: Initializing buffer pool, size = 128.0M
130712  6:44:35 InnoDB: Completed initialization of buffer pool
130712  6:44:35 InnoDB: highest supported file format is Barracuda.
130712  6:44:35  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
130712  6:44:35  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './bloodi5_BiPWiki/mw_change_tag.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.