I am getting the below error: ERROR 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock'
So I did a touch /var/lib/mysql/mysql.sock and tried restarting mysql. I still received the above error when I tried connecting to mysql. So I checked to see if mysql.sock was still there and it turns out it was removed somehow. I've been running mysql for about three weeks now without any problems. Any idea why this is happening and why it's happening now and not earlier? I've included the .err from /var/lib/mysql directory below. Thanks for the help. Dan Cox .error: (trimmed) 030126 18:59:30 mysqld started /usr/sbin/mysqld: ready for connections 030201 22:31:36 /usr/sbin/mysqld: Normal shutdown 030201 22:31:36 /usr/sbin/mysqld: Shutdown Complete 030201 22:31:36 mysqld ended 030202 10:29:42 mysqld started 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=100 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 225791 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=0xbfffdf58, stack_bottom=0x562c8c00, thread_stack=65536, aborting backtrace. Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x5520f990 is invalid pointer thd->thread_id=1717920867 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 1717920867 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 030202 10:29:43 mysqld ended --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
