Jump to content

Problem - mysqld got signal 11


Recommended Posts

Hello!
I have a problem with turkish serverfiles. My mysql can't start! I have an error "mysqld got signal 11"

>service mysql-server status
>mysql is not running
>service mysql-server start
>mysql is starting
>service mysql-server status
>mysql is not running
Ethost.err

181007 17:58:53 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2018-10-07 17:58:53 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-10-07 17:58:53 5887 [Note] Plugin 'FEDERATED' is disabled.
2018-10-07 17:58:53 5887 [Note] InnoDB: The InnoDB memory heap is disabled
2018-10-07 17:58:53 5887 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-10-07 17:58:53 5887 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-10-07 17:58:53 5887 [Note] InnoDB: Not using CPU crc32 instructions
2018-10-07 17:58:53 5887 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-10-07 17:58:53 5887 [Note] InnoDB: Completed initialization of buffer pool
2018-10-07 17:58:53 5887 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2018-10-07 17:58:53 5887 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2018-10-07 17:58:53 5887 [Note] InnoDB: Database physically writes the file full: wait...
2018-10-07 17:58:53 5887 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2018-10-07 17:58:53 5887 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
2018-10-07 17:58:54 5887 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2018-10-07 17:58:54 5887 [Warning] InnoDB: New log files created, LSN=45781
2018-10-07 17:58:54 5887 [Note] InnoDB: Doublewrite buffer not found: creating new
2018-10-07 17:58:54 5887 [Note] InnoDB: Doublewrite buffer created
2018-10-07 17:58:54 5887 [Note] InnoDB: 128 rollback segment(s) are active.
2018-10-07 17:58:54 5887 [Warning] InnoDB: Creating foreign key constraint system tables.
2018-10-07 17:58:54 5887 [Note] InnoDB: Foreign key constraint system tables created
2018-10-07 17:58:54 5887 [Note] InnoDB: Creating tablespace and datafile system tables.
2018-10-07 17:58:54 5887 [Note] InnoDB: Tablespace and datafile system tables created.
2018-10-07 17:58:54 5887 [Note] InnoDB: Waiting for purge to start
2018-10-07 17:58:54 5887 [Note] InnoDB: 5.6.14 started; log sequence number 0
2018-10-07 17:58:54 5887 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: e40e91a9-ca49-11e8-849d-080027db0e05.
2018-10-07 17:58:54 5887 [Note] Server hostname (bind-address): '*'; port: 3306
2018-10-07 17:58:54 5887 [Note] IPv6 is available.
2018-10-07 17:58:54 5887 [Note]   - '::' resolves to '::';
2018-10-07 17:58:54 5887 [Note] Server socket created on IP: '::'.
15:58:54 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=8388608
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 = 67551 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Anyone knows how to fix this? Thank u for all answers!
Greetings!
 

Link to comment
Share on other sites

  • Replies 0
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

Announcements



×
×
  • Create New...

Important Information

Terms of Use / Privacy Policy / Guidelines / We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.