ali_2636
July 19th, 2016, 20:46
سلام
نمی دونم امروز چی شد سرور خوابید و این پیغام نمایش داده میشه و mysql ران نمیشه
Error establishing a database connection
دوستان لطفا کمکم کنید هرکاری فکر کنید کردم
بیلد mysql
تغییر mysql_inst به yes
آپدیت centosو custombuildو mysql
[root@server ~]# wget -O /etc/my.cnf http://files.directadmin.com/services/all/mysql/my-huge-5.5.cnf
mv /etc/my.cnf /etc/my.cnf.moved
./build mysql
نتیجه نداد
از تو کنترل پنل هم که اجرا می کنم این ارور میده
/sbin/service mysqld reload 2>&1:-s
[root@server ~]# /sbin/service mysqld restart
ERROR! MySQL server PID file could not be found!
Starting MySQL.. ERROR! The server quit without updating PID file (/var/lib/mysql/server.myServerDomain.com.pid).
[root@server ~]# service mysqld status
ERROR! MySQL is not running, but lock file (/var/lock/subsys/mysql) exists
[root@server ~]# tail -200 /var/lib/mysql/*.err
160719 23:09: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: Last MySQL binlog file position 0 325693534, file name ./mysql-bin.000027
160719 23:09:08 InnoDB: Waiting for the background threads 160719 23:09:09 mysqld_safe mysqld from pid file /var/lib/mysql/server.zamzamghadir.com.pid ended
160719 23:10:01 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160719 23:10:01 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
160719 23:10:01 [Note] /usr/sbin/mysqld (mysqld 5.5.48-log) starting as process 15859 ...
160719 23:10:01 [Note] Plugin 'FEDERATED' is disabled.
160719 23:10:01 InnoDB: The InnoDB memory heap is disabled
160719 23:10:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160719 23:10:01 InnoDB: Compressed tables use zlib 1.2.3
160719 23:10:01 InnoDB: Using Linux native AIO
160719 23:10:01 InnoDB: Initializing buffer pool, size = 128.0M
160719 23:10:01 InnoDB: Completed initialization of buffer pool
160719 23:10:01 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!
160719 23:10:01 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 325693534, file name ./mysql-bin.000027
160719 23:10:01 InnoDB: Waiting for the background threads to start
160719 23:10:02 InnoDB: 5.5.48 started; log sequence number 16349892854
18:40:02 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=402653184
read_buffer_size=2097152
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 = 1013456 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 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7a9405]
/usr/sbin/mysqld(handle_fatal_signal+0x403)[0x6762d3]
/lib64/libpthread.so.0(+0xf710)[0x7fa3bc6cf710]
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.
160719 23:10:02 mysqld_safe mysqld from pid file /var/lib/mysql/server.zamzamghadir.com.pid ended
160719 23:10:08 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160719 23:10:08 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
160719 23:10:08 [Note] /usr/sbin/mysqld (mysqld 5.5.48-log) starting as process 16200 ...
160719 23:10:08 [Note] Plugin 'FEDERATED' is disabled.
160719 23:10:08 InnoDB: The InnoDB memory heap is disabled
160719 23:10:08 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160719 23:10:08 InnoDB: Compressed tables use zlib 1.2.3
160719 23:10:08 InnoDB: Using Linux native AIO
160719 23:10:08 InnoDB: Initializing buffer pool, size = 128.0M
160719 23:10:08 InnoDB: Completed initialization of buffer pool
160719 23:10:08 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!
160719 23:10: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: Last MySQL binlog file position 0 325693534, file name ./mysql-bin.000027
160719 23:10:09 InnoDB: Waiting for the background threads 160719 23:10:10 mysqld_safe mysqld from pid file /var/lib/mysql/server.zamzamghadir.com.pid ended
160719 23:11:02 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160719 23:11:02 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
160719 23:11:02 [Note] /usr/sbin/mysqld (mysqld 5.5.48-log) starting as process 16611 ...
160719 23:11:02 [Note] Plugin 'FEDERATED' is disabled.
160719 23:11:02 InnoDB: The InnoDB memory heap is disabled
160719 23:11:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160719 23:11:02 InnoDB: Compressed tables use zlib 1.2.3
160719 23:11:02 InnoDB: Using Linux native AIO
160719 23:11:02 InnoDB: Initializing buffer pool, size = 128.0M
160719 23:11:02 InnoDB: Completed initialization of buffer pool
160719 23:11:02 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!
160719 23:11:02 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 325693534, file name ./mysql-bin.000027
160719 23:11:02 InnoDB: Waiting for the background threads to start
160719 23:11:03 InnoDB: 5.5.48 started; log sequence number 16349892854
18:41: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=402653184
read_buffer_size=2097152
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 = 1013456 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 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7a9405]
/usr/sbin/mysqld(handle_fatal_signal+0x403)[0x6762d3]
/lib64/libpthread.so.0(+0xf710)[0x7f751571a710]
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.
160719 23:11:03 mysqld_safe mysqld from pid file /var/lib/mysql/server.zamzamghadir.com.pid ended
160719 23:11:09 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160719 23:11:09 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
160719 23:11:09 [Note] /usr/sbin/mysqld (mysqld 5.5.48-log) starting as process 16937 ...
160719 23:11:09 [Note] Plugin 'FEDERATED' is disabled.
160719 23:11:09 InnoDB: The InnoDB memory heap is disabled
160719 23:11:09 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160719 23:11:09 InnoDB: Compressed tables use zlib 1.2.3
160719 23:11:09 InnoDB: Using Linux native AIO
160719 23:11:09 InnoDB: Initializing buffer pool, size = 128.0M
160719 23:11:09 InnoDB: Completed initialization of buffer pool
160719 23:11:09 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!
160719 23:11:09 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 325693534, file name ./mysql-bin.000027
160719 23:11:09 InnoDB: Waiting for the background threads 160719 23:11:10 mysqld_safe mysqld from pid file /var/lib/mysql/server.zamzamghadir.com.pid ended
160719 23:12:02 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160719 23:12:02 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
160719 23:12:02 [Note] /usr/sbin/mysqld (mysqld 5.5.48-log) starting as process 17348 ...
160719 23:12:02 [Note] Plugin 'FEDERATED' is disabled.
160719 23:12:02 InnoDB: The InnoDB memory heap is disabled
160719 23:12:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160719 23:12:02 InnoDB: Compressed tables use zlib 1.2.3
160719 23:12:02 InnoDB: Using Linux native AIO
160719 23:12:02 InnoDB: Initializing buffer pool, size = 128.0M
160719 23:12:02 InnoDB: Completed initialization of buffer pool
160719 23:12:02 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!
160719 23:12:02 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 325693534, file name ./mysql-bin.000027
160719 23:12:02 InnoDB: Waiting for the background threads to start
160719 23:12:03 InnoDB: 5.5.48 started; log sequence number 16349892854
18:42: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=402653184
read_buffer_size=2097152
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 = 1013456 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 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7a9405]
/usr/sbin/mysqld(handle_fatal_signal+0x403)[0x6762d3]
/lib64/libpthread.so.0(+0xf710)[0x7f6519d9e710]
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.
160719 23:12:03 mysqld_safe mysqld from pid file /var/lib/mysql/server.zamzamghadir.com.pid ended
160719 23:12:09 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160719 23:12:09 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
160719 23:12:09 [Note] /usr/sbin/mysqld (mysqld 5.5.48-log) starting as process 17689 ...
نمی دونم امروز چی شد سرور خوابید و این پیغام نمایش داده میشه و mysql ران نمیشه
Error establishing a database connection
دوستان لطفا کمکم کنید هرکاری فکر کنید کردم
بیلد mysql
تغییر mysql_inst به yes
آپدیت centosو custombuildو mysql
[root@server ~]# wget -O /etc/my.cnf http://files.directadmin.com/services/all/mysql/my-huge-5.5.cnf
mv /etc/my.cnf /etc/my.cnf.moved
./build mysql
نتیجه نداد
از تو کنترل پنل هم که اجرا می کنم این ارور میده
/sbin/service mysqld reload 2>&1:-s
[root@server ~]# /sbin/service mysqld restart
ERROR! MySQL server PID file could not be found!
Starting MySQL.. ERROR! The server quit without updating PID file (/var/lib/mysql/server.myServerDomain.com.pid).
[root@server ~]# service mysqld status
ERROR! MySQL is not running, but lock file (/var/lock/subsys/mysql) exists
[root@server ~]# tail -200 /var/lib/mysql/*.err
160719 23:09: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: Last MySQL binlog file position 0 325693534, file name ./mysql-bin.000027
160719 23:09:08 InnoDB: Waiting for the background threads 160719 23:09:09 mysqld_safe mysqld from pid file /var/lib/mysql/server.zamzamghadir.com.pid ended
160719 23:10:01 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160719 23:10:01 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
160719 23:10:01 [Note] /usr/sbin/mysqld (mysqld 5.5.48-log) starting as process 15859 ...
160719 23:10:01 [Note] Plugin 'FEDERATED' is disabled.
160719 23:10:01 InnoDB: The InnoDB memory heap is disabled
160719 23:10:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160719 23:10:01 InnoDB: Compressed tables use zlib 1.2.3
160719 23:10:01 InnoDB: Using Linux native AIO
160719 23:10:01 InnoDB: Initializing buffer pool, size = 128.0M
160719 23:10:01 InnoDB: Completed initialization of buffer pool
160719 23:10:01 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!
160719 23:10:01 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 325693534, file name ./mysql-bin.000027
160719 23:10:01 InnoDB: Waiting for the background threads to start
160719 23:10:02 InnoDB: 5.5.48 started; log sequence number 16349892854
18:40:02 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=402653184
read_buffer_size=2097152
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 = 1013456 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 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7a9405]
/usr/sbin/mysqld(handle_fatal_signal+0x403)[0x6762d3]
/lib64/libpthread.so.0(+0xf710)[0x7fa3bc6cf710]
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.
160719 23:10:02 mysqld_safe mysqld from pid file /var/lib/mysql/server.zamzamghadir.com.pid ended
160719 23:10:08 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160719 23:10:08 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
160719 23:10:08 [Note] /usr/sbin/mysqld (mysqld 5.5.48-log) starting as process 16200 ...
160719 23:10:08 [Note] Plugin 'FEDERATED' is disabled.
160719 23:10:08 InnoDB: The InnoDB memory heap is disabled
160719 23:10:08 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160719 23:10:08 InnoDB: Compressed tables use zlib 1.2.3
160719 23:10:08 InnoDB: Using Linux native AIO
160719 23:10:08 InnoDB: Initializing buffer pool, size = 128.0M
160719 23:10:08 InnoDB: Completed initialization of buffer pool
160719 23:10:08 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!
160719 23:10: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: Last MySQL binlog file position 0 325693534, file name ./mysql-bin.000027
160719 23:10:09 InnoDB: Waiting for the background threads 160719 23:10:10 mysqld_safe mysqld from pid file /var/lib/mysql/server.zamzamghadir.com.pid ended
160719 23:11:02 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160719 23:11:02 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
160719 23:11:02 [Note] /usr/sbin/mysqld (mysqld 5.5.48-log) starting as process 16611 ...
160719 23:11:02 [Note] Plugin 'FEDERATED' is disabled.
160719 23:11:02 InnoDB: The InnoDB memory heap is disabled
160719 23:11:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160719 23:11:02 InnoDB: Compressed tables use zlib 1.2.3
160719 23:11:02 InnoDB: Using Linux native AIO
160719 23:11:02 InnoDB: Initializing buffer pool, size = 128.0M
160719 23:11:02 InnoDB: Completed initialization of buffer pool
160719 23:11:02 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!
160719 23:11:02 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 325693534, file name ./mysql-bin.000027
160719 23:11:02 InnoDB: Waiting for the background threads to start
160719 23:11:03 InnoDB: 5.5.48 started; log sequence number 16349892854
18:41: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=402653184
read_buffer_size=2097152
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 = 1013456 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 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7a9405]
/usr/sbin/mysqld(handle_fatal_signal+0x403)[0x6762d3]
/lib64/libpthread.so.0(+0xf710)[0x7f751571a710]
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.
160719 23:11:03 mysqld_safe mysqld from pid file /var/lib/mysql/server.zamzamghadir.com.pid ended
160719 23:11:09 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160719 23:11:09 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
160719 23:11:09 [Note] /usr/sbin/mysqld (mysqld 5.5.48-log) starting as process 16937 ...
160719 23:11:09 [Note] Plugin 'FEDERATED' is disabled.
160719 23:11:09 InnoDB: The InnoDB memory heap is disabled
160719 23:11:09 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160719 23:11:09 InnoDB: Compressed tables use zlib 1.2.3
160719 23:11:09 InnoDB: Using Linux native AIO
160719 23:11:09 InnoDB: Initializing buffer pool, size = 128.0M
160719 23:11:09 InnoDB: Completed initialization of buffer pool
160719 23:11:09 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!
160719 23:11:09 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 325693534, file name ./mysql-bin.000027
160719 23:11:09 InnoDB: Waiting for the background threads 160719 23:11:10 mysqld_safe mysqld from pid file /var/lib/mysql/server.zamzamghadir.com.pid ended
160719 23:12:02 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160719 23:12:02 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
160719 23:12:02 [Note] /usr/sbin/mysqld (mysqld 5.5.48-log) starting as process 17348 ...
160719 23:12:02 [Note] Plugin 'FEDERATED' is disabled.
160719 23:12:02 InnoDB: The InnoDB memory heap is disabled
160719 23:12:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160719 23:12:02 InnoDB: Compressed tables use zlib 1.2.3
160719 23:12:02 InnoDB: Using Linux native AIO
160719 23:12:02 InnoDB: Initializing buffer pool, size = 128.0M
160719 23:12:02 InnoDB: Completed initialization of buffer pool
160719 23:12:02 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!
160719 23:12:02 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 325693534, file name ./mysql-bin.000027
160719 23:12:02 InnoDB: Waiting for the background threads to start
160719 23:12:03 InnoDB: 5.5.48 started; log sequence number 16349892854
18:42: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=402653184
read_buffer_size=2097152
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 = 1013456 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 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7a9405]
/usr/sbin/mysqld(handle_fatal_signal+0x403)[0x6762d3]
/lib64/libpthread.so.0(+0xf710)[0x7f6519d9e710]
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.
160719 23:12:03 mysqld_safe mysqld from pid file /var/lib/mysql/server.zamzamghadir.com.pid ended
160719 23:12:09 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160719 23:12:09 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
160719 23:12:09 [Note] /usr/sbin/mysqld (mysqld 5.5.48-log) starting as process 17689 ...