Seafile don't start anymore after simple shutdown

Hello, I had to shutdown my seafile server (version 6.0.5) running on a raspberry, when I restart it, seafile didn’t start. I started to look at the logs and here is what I see in the mysql log:

170413 19:06:03 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
170413 19:06:03 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Plea
se use the full name instead.
170413 19:06:03 [Note] /usr/sbin/mysqld (mysqld 5.5.52-0+deb8u1) starting as process 7653 …
170413 19:06:03 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future re
lease. Please use the full name instead.
170413 19:06:03 [Note] Plugin ‘FEDERATED’ is disabled.
170413 19:06:03 InnoDB: The InnoDB memory heap is disabled
170413 19:06:03 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170413 19:06:03 InnoDB: Compressed tables use zlib 1.2.8
170413 19:06:03 InnoDB: Using Linux native AIO
170413 19:06:03 InnoDB: Initializing buffer pool, size = 128.0M
170413 19:06:03 InnoDB: Completed initialization of buffer pool
19:06:03 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=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346093 K bytes of memory
Hope that’s ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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 = 0 thread_stack 0x30000
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.
170413 19:06:03 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

The problem is that for some reason mysql is no more starting… I tried to google and to understand what’s going on but I didn’t find any hint or useful suggestion… any idea on what’s going on? Suggestions on how to fix the problem?

Thanks

Attilio