> Hardware? > Operating System and version? > MySql version? > Precompiled, you compiled? > Which compiler?
Intel Dual 1Ghz, 1Gb RAM, RedHat Linux 6.2, kernel 2.4.16, MySQL 3.23.52 from rpms (happened the same with 3.23.46). As I said before, this only happens the last few days, we were running for almost a year without much problems. Anyone can explain/understand the stack trace? Cheers -- L > [EMAIL PROTECTED] wrote: > > > Hi. These last days, after some months of running relatively smoothly, > >I've been having some trouble with MySQL. Sometimes (yesterday 4 times) it > >just goes astray and virtually hangs. Load goes up to +200%, all > >connections are occupied and it just doesn't do anything. The only way to > >stop it is to killall -9 mysql because a mysqladmin shutdown won't do. > > > > Looking though the error file 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, > >[...] > > > >key_buffer_size=402649088 > >record_buffer=8384512 > >sort_buffer=33554424 > >max_used_connections=352 > >max_connections=400 > >threads_connected=287 > >It is possible that mysqld could use up to > >key_buffer_size + (record_buffer + sort_buffer)*max_connections = 4192696 K > >bytes of memory > >Hope that's ok, if not, decrease some variables in the equation > > > > (Is it ok? Box is a Dual 1Ghz, 1Gb ram, Linux 2.4.16 dedicated only to > >MySQL) > > > >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... > >Stack range sanity check OK, backtrace follows: > >0x806ede4 > >0x8120148 > >0x814ba77 > >0x80a147f > >0x807561a > >0x8073f97 > > > >[...] > > > >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=1733 > > > > Everytime the box hangs I get the same stack backtrace, I have resolved > >it and it's: > > > >0x806ede4 pack__12Field_stringPcPCcUi + 20 > >0x8120148 regatoi + 8 > >0x814ba6f __printf_fp + 5719 > >0x80a147f join_read_const__FP13st_join_table + 35 > >0x807561a push_front__t4List1Z3KeyP3Key + 18 > >0x8073f97 prepare__13select_exportRt4List1Z4Item + 443 > > > > ...but when I try to find the thread that caused it (1733 in this case) > >in the binary log it doesn't appear so I'm unable to determine what's > >causing the error. > > > > I thought at first that it could be a load peak issue, but this error is > >from today at 6am, and this isn't a busy hour. Everytime I get this i run > >myisamchk -r *.MYI. It seems that after some time (+30 minutes usually) > >mysql restarts and starts running again. > > --------------------------------------------------------------------- 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
