Quote From : valley June 1, 2015, 3:02 pm Quote From : doganmanis June 1, 2015, 1:48 pm Quote From : valley January 7, 2015, 6:11 am Create the file /var/run/mysqld and set owner and group as "mysql"
Hope this helps
how to create the file?
i have the same prob
The following 2 commands should do the trick.
mkdir /var/run/mysqld
chown mysql:mysql /var/run/mysqld
Note : Make sure you are logged in as root to be able to execute the above commands.
Hope this helps
no luck for me :(
i got error mysql pid file cannot start/missing something like that
i try to remove mariadb then reinstall again but nothing change :(
this is my server error
PHP Code InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
150601 21:56:07 [ERROR] mysqld got signal 6 ;
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.
To report this bug, see http://kb.askmonty.org/en/reporting-bugs
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.
Server version: 5.5.42-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 465688 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0x0
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 = 0x0 thread_stack 0x48000
mysys/stacktrace.c:246(my_print_stacktrace)[0x865c52d]
sql/signal_handler.cc:153(handle_fatal_signal)[0x82da7eb]
[0xb76e6500]
/lib/libc.so.6(abort+0x17a)[0xb73e83ea]
btr/btr0btr.c:3383(btr_compress)[0x855f04a]
btr/btr0cur.c:3222(btr_cur_compress_if_useful)[0x85641af]
btr/btr0cur.c:3471(btr_cur_pessimistic_delete)[0x856f7b1]
row/row0purge.c:177(row_purge_remove_clust_if_poss_low)[0x86295a4]
row/row0purge.c:216(row_purge_remove_clust_if_poss)[0x862a086]
que/que0que.c:1259(que_thr_step)[0x861fdd8]
trx/trx0purge.c:1220(trx_purge)[0x853adad]
srv/srv0srv.c:4210(srv_purge_thread)[0x852e0dd]
/lib/libpthread.so.0(+0x6b39)[0xb76cbb39]
/lib/libc.so.6(clone+0x5e)[0xb749ed7e]
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.
150601 21:56:08 mysqld_safe mysqld from pid file /var/lib/mysql/mysqld.pid ended
please someone help me
|