On Thu, 8 Feb 2007 11:46:39 +0100 Arnau Bria wrote: > Hi, [...] > This is what I see in my mysqld.err log: > > 070208 11:26:17 [Warning] No argument was provided to --log-bin, and > --log-bin-index was not used; so replication may break when this > MySQL server acts as a master and has his hostname changed!! Please > use '--log-bin=afrodita-bin' to avoid this problem. mysqld got signal > 4; 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. > > ****I think I can ignore this******** > > key_buffer_size=0 > read_buffer_size=258048 > 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 = 76399 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=0xb690808d, backtrace may not be correct. > Bogus stack limit or frame pointer, fp=0xb690808d, > stack_bottom=0xbfcb0000, thread_stack=196608, aborting backtrace. 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. > > *****WTH!!!!****** I had to remove all bin files from /var/lib/mysql After that, all works fine!
cheers! -- Arnau Bria http://blog.emergetux.net Wiggum: Dispara a las ruedas Lou. Lou: eee, es un tanque jefe. Wiggum: Me tienes hartito con todas tus excusas. -- [email protected] mailing list
