The server quit without updating the PID file

Hello I get the following error when i try to start mysql ERROR! The server quit without updating PID file (/var/lib/mysql/hostname.pid). My log file
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 0x40000 /usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7ab955] /usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x686ee4] /lib64/libpthread.so.0(+0xf790)[0x7f450dffe790] The manual page at MySQL :: MySQL 5.7 Reference Manual :: B.5.3.3 What to Do If MySQL Keeps Crashing contains information that should help you find out what is causing the crash. 151224 10:09:11 mysqld_safe mysqld from pid file /var/lib/mysql/fst1.nfs.gr.pid ended 151224 10:13:42 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 151224 10:13:42 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release. 151224 10:13:42 [Note] /usr/sbin/mysqld (mysqld 5.5.46-cll) starting as process 10579 ... 151224 10:13:42 [Note] Plugin 'FEDERATED' is disabled. 151224 10:13:42 InnoDB: The InnoDB memory heap is disabled 151224 10:13:42 InnoDB: Mutexes and rw_locks use GCC atomic builtins 151224 10:13:42 InnoDB: Compressed tables use zlib 1.2.3 151224 10:13:42 InnoDB: Using Linux native AIO 151224 10:13:42 InnoDB: Initializing buffer pool, size = 128.0M 151224 10:13:42 InnoDB: Completed initialization of buffer pool 151224 10:13:42 InnoDB: highest supported file format is Barracuda. InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 151224 10:13:42 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: Last MySQL binlog file position 0 517005368, file name ./mysql-bin.000263 151224 10:13:42 InnoDB: Waiting for the background threads to start 151224 10:13:43 151224 10:13:43 mysqld_safe mysqld from pid file /var/lib/mysql/fst1.nfs.gr.pid ended 151224 10:18:49 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 151224 10:18:49 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release. 151224 10:18:49 [Note] /usr/sbin/mysqld (mysqld 5.5.46-cll) starting as process 12885 ... 151224 10:18:49 [Note] Plugin 'FEDERATED' is disabled. 151224 10:18:49 InnoDB: The InnoDB memory heap is disabled 151224 10:18:49 InnoDB: Mutexes and rw_locks use GCC atomic builtins 151224 10:18:49 InnoDB: Compressed tables use zlib 1.2.3 151224 10:18:49 InnoDB: Using Linux native AIO 151224 10:18:49 InnoDB: Initializing buffer pool, size = 128.0M 151224 10:18:49 InnoDB: Completed initialization of buffer pool 151224 10:18:49 InnoDB: highest supported file format is Barracuda. InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 151224 10:18:49 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: Last MySQL binlog file position 0 517005368, file name ./mysql-bin.000263 151224 10:18:50 InnoDB: Waiting for the background threads to start 151224 10:18:51 InnoDB: 5.5.46 started; log sequence number 18123439724 08:18:51 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.