Hello.
> 0x808d8d7 handle_segfault + 423 > 0x82e68d8 pthread_sighandler + 184 > 0x80929a3 ip_to_hostname__FP7in_addrPUi + 483 > 0x809af45 check_connection__FP3THD + 213 Looks like it is a problem with gethostbyaddr(), which solved in your version according to the manual at: http://dev.mysql.com/doc/mysql/en/linux-x86.html As said at this page you should launch mysqld with --thread-stack=192K (you may try a greater value, because 192K is default in 4.1.10). If it doesn't help you may run mysqld with --skip-name-resolve. See: http://dev.mysql.com/doc/mysql/en/dns.html Batara Kesuma <[EMAIL PROTECTED]> wrote: > Hi, > > I use MySQL 4.1.10, and it crashes about once a day. I posted about this > bug two days ago, but I forgot to put the stack trace result there, > sorry for that. Now I put the stack trace result below. > > My kernel is 2.6.10, RAM is 4 GB. Single CPU with HT (shows up as 2 CPU > on linux). The MySQL that I use is the official RPM from mysql.com. > > Here is what I found in my error log: > > --- start: hostname.err ---- > 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=33554432 > read_buffer_size=2093056 > max_used_connections=80 > max_connections=400 > threads_connected=4 > It is possible that mysqld could use up to > key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections > = 3209660 K > bytes of memory > Hope that's ok; if not, decrease some variables in the equation. > > thd=0x56000440 > 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=0xbfe5f5a8, backtrace may not be correct. > Stack range sanity check OK, backtrace follows: > 0x808d8d7 > 0x82e68d8 > 0x80929a3 > 0x809af45 > 0x809b709 > 0x82e408c > 0x830d95a > 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 trace. Resolved > stack trace is much more helpful in diagnosing the problem, so please do > resolve it > Trying to get some variables. > Some pointers may be invalid and cause the dump to abort... > thd->query at (nil) is invalid pointer > thd->thread_id=7005520 > 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. > --- end: hostname.err --- > > And here is the stack trace result: > > [EMAIL PROTECTED] ~]# resolve_stack_dump -s mysqld.sym -n mysql.stack1 > 0x808d8d7 handle_segfault + 423 > 0x82e68d8 pthread_sighandler + 184 > 0x80929a3 ip_to_hostname__FP7in_addrPUi + 483 > 0x809af45 check_connection__FP3THD + 213 > 0x809b709 handle_one_connection + 297 > 0x82e408c pthread_start_thread + 220 > 0x830d95a thread_start + 4 > > Does anyone have the same problem? How do I fix this? Thank you very > much. > > Regards, > --bk > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
