Dotaz: Gentoo: Mysql socket connection

[Ondrej Maly]

Dobry den,

vim ze se to tu resilo 1000x, vse sem procetl, google zkusil a nic nenasel, prosim Vas proto o pomoc.

System Gentoo, kernel-2.6.12.3, mysql-4.1.8

po spusteni /etc/init.d/mysql start [OK]

v logu: Mysql started Mysql ended

v ps -ax mysql neni (je spustena a hned ukoncena), presto /etc/init.d/mysql status vypise ze bezi a nelze zastavit ;(

ve /var/run/mysql nemam .pid ani sock

mam podezreni na zapomenutou nejakou podporu v jadre?

Odpovědi

[Zdeněk Burda]

A co máš v logu mysql?

[Ing. Zdeněk Burda]

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_connections=100
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 233983 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x8465268
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...
Cannot determine thread, fp=0xbfad30a8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x814617d
0xb7e5bc6d
0x81fdb60
0x8147874
0xb7c2229e
0x80d2b41
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do 
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil)  is invalid pointer
thd->thread_id=0
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
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_connections=100
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 233983 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x8465268
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...
Cannot determine thread, fp=0xbff10718, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x814617d
0xb7d99c6d
0x81fdb60
0x8147874
0xb7b6029e
0x80d2b41
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do 
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil)  is invalid pointer
thd->thread_id=0
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.