Re: ERROR 2002 (HY000): Can't connect to local MySQL server through socket : please read also this thread

[c c]

Hi
i have the same problem too, below is mysqld.log :

================================================================

050328 14:13:40 mysqld started
/usr/sbin/mysqld: Can't create/write to file '/tmp/ibA9EkGG' (Errcode: 13)
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=0
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 = 217599 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=(nil)
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=0xfee719c8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80baeee
0x8326824
0x8324ef7
0x832263e
0x82f423b
0x8143102
0x82b0963
0x818bed5
0x8143a17
0x813bc5d
0x80bb429
0x80be885
0x8336a24
0x8048121
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 tra
ce. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
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.
050328 14:13:40 mysqld ended

========================================================

Can anyone help me here ? I am using Fedora core 3 , the Mysql server uses to work perfectly OK, this problem only happened recently and i didn't make any changes to the OS and Mysql configurations, i am really puzzled why this problem can happen suddenly. Pls help, thanks