error log available on request. Ezmlm rejected it. Its always in memcpy+49 just before it gets to the pthread handler and the segfault handler. This is pretty consistent.
I have a query that was 100% reliable, until the server went into production. Now its serving 15 queries/sec, and crashes pretty often. And for extra fun, the query that fails is NOT the one that seems to trigger it. This query is run constantly, mostly with no errors. When I run a report query, other simultaneous queries on the same data seem to get the errors. 0x806d85a handle_segfault__Fi + 406 0x82a81e2 pthread_sighandler + 162 0x82daa5f memcpy + 39 0x80951fb store_record_in_cache__FP13st_join_cache + 255 0x8092ad0 sub_select_cache__FP4JOINP13st_join_tableb + 156 Machine is 1.6 ghz p4, 512 megs ram, 2x IDE disks. OS is rh 7.2, all updates, glibc 2.2.4, though mysql-max does not use that, Server is mysql-max 3.23.49a, from the rpm from mysql.com. Tried a source recompile, exact same symptoms and error location. Tried also 3.23.41 from redhats's source tree, recompiled with --innodb, since I need the innodb consistent read handler, the performance under myISAM is disappointing under load. Errors under .41/using glibc are nearly identical, modulo different version and shared libc. (glibc 2.2.4): 0x80bf15f handle_segfault__Fi + 431 0x4002a4f3 _end + 936436875 0x4018863f _end + 937870807 0x80e8309 store_record_in_cache__FP13st_join_cache + 217 0x80e535f sub_select_cache__FP4JOINP13st_join_tableb + 159 0x80e54c2 sub_select__FP4JOINP13st_join_tableb + 258 -- Jay "yohimbe" Thorne [EMAIL PROTECTED] Mgr Sys & Tech, Userfriendly.org --------------------------------------------------------------------- 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
