wheel

I can\'t start mysql. I get a socket error (there are not socket files in /tmp or elsewhere) whenever I try to run mysql or anything related from the command line. The machine just came from a developer who said mysql was running when it left his place. The only thing I think I did was look at drakconf and confirm that the network settings were correct. When I check localhost.err (where localhost=machine name) I get this: 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 agaist 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=8388600 record_buffer=131072 sort_buffer=2097144 max_used_connections=0 max_connections=256 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 565245 K bytes of memory Hope that\'s ok, if not, decrease some variables in the equation 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... Bogus stack limit or frame pointer, fp=0xbfffec78, stack_bottom=0xcd9a2e0, thread_stack=65536, aborting backtrace. Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0xbe08570 is invalid pointer thd->thread_id=65537 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 65537 did to cause the crash. In some cases of really bad corruption, the values shown above may be invalid The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains information that should help you find out what is causing the crash 030415 00:13:52 mysqld ended