G'day, I have an ubuntu hoary install. I have just used apt-get to install mysql-server. (Which I have done countless times with no problems)
However this time I get: Dec 11 04:12:36 ns3 mysqld_safe[3846]: started Dec 11 04:12:36 ns3 mysqld[3853]: mysqld got signal 11; Dec 11 04:12:36 ns3 mysqld[3853]: This could be because you hit a bug. It is also possible that this binary Dec 11 04:12:36 ns3 mysqld[3853]: or one of the libraries it was linked against is corrupt, improperly built, Dec 11 04:12:36 ns3 mysqld[3853]: or misconfigured. This error can also be caused by malfunctioning hardware. Dec 11 04:12:36 ns3 mysqld[3853]: We will try our best to scrape up some info that will hopefully help diagnose Dec 11 04:12:36 ns3 mysqld[3853]: the problem, but since we have already crashed, something is definitely wrong Dec 11 04:12:36 ns3 mysqld[3853]: and this may fail. Dec 11 04:12:36 ns3 mysqld[3853]: Dec 11 04:12:36 ns3 mysqld[3853]: key_buffer_size=8388608 Dec 11 04:12:36 ns3 mysqld[3853]: read_buffer_size=131072 Dec 11 04:12:36 ns3 mysqld[3853]: max_used_connections=0 Dec 11 04:12:36 ns3 mysqld[3853]: max_connections=100 Dec 11 04:12:36 ns3 mysqld[3853]: threads_connected=0 Dec 11 04:12:36 ns3 mysqld[3853]: It is possible that mysqld could use up to Dec 11 04:12:36 ns3 mysqld[3853]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K Dec 11 04:12:36 ns3 mysqld[3853]: bytes of memory Dec 11 04:12:36 ns3 mysqld[3853]: Hope that's ok; if not, decrease some variables in the equation. Dec 11 04:12:36 ns3 mysqld[3853]: Dec 11 04:12:36 ns3 mysqld[3853]: thd=0x8440638 Dec 11 04:12:36 ns3 mysqld[3853]: Attempting backtrace. You can use the following information to find out Dec 11 04:12:36 ns3 mysqld[3853]: where mysqld died. If you see no messages after this, something went Dec 11 04:12:36 ns3 mysqld[3853]: terribly wrong... Dec 11 04:12:36 ns3 mysqld[3853]: Cannot determine thread, fp=0x41e50148, backtrace may not be correct. Dec 11 04:12:36 ns3 mysqld[3853]: Stack range sanity check OK, backtrace follows: Dec 11 04:12:36 ns3 mysqld[3853]: 0x80fde42 Dec 11 04:12:36 ns3 mysqld[3853]: 0x41e50440 Dec 11 04:12:36 ns3 mysqld[3853]: (nil) Dec 11 04:12:36 ns3 mysqld[3853]: New value of fp=(nil) failed sanity check, terminating stack trace! Dec 11 04:12:36 ns3 mysqld[3853]: Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved Dec 11 04:12:36 ns3 mysqld[3853]: stack trace is much more helpful in diagnosing the problem, so please do Dec 11 04:12:36 ns3 mysqld[3853]: resolve it Dec 11 04:12:36 ns3 mysqld[3853]: Trying to get some variables. Dec 11 04:12:36 ns3 mysqld[3853]: Some pointers may be invalid and cause the dump to abort... Dec 11 04:12:36 ns3 mysqld[3853]: thd->query at 0x7daee3e0 is invalid pointer Dec 11 04:12:36 ns3 mysqld[3853]: thd->thread_id=1633955117 Dec 11 04:12:36 ns3 mysqld[3853]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains Dec 11 04:12:36 ns3 mysqld[3853]: information that should help you find out what is causing the crash. Dec 11 04:12:36 ns3 mysqld_safe[3858]: ended Dec 11 04:12:43 ns3 /etc/init.d/mysql[3912]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in Dec 11 04:12:43 ns3 /etc/init.d/mysql[3912]: ^G/usr/bin/mysqladmin: connect to server at 'localhost' failed Dec 11 04:12:43 ns3 /etc/init.d/mysql[3912]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)' Dec 11 04:12:43 ns3 /etc/init.d/mysql[3912]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists! Dec 11 04:12:43 ns3 /etc/init.d/mysql[3912]: Anybody with any hints where to look great fully received. Regards, Ashley -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
