mysql crashing

MySQL & MariaDB Other MySQL® Questions
1

[B]hello, i have problem with hiden crashing of mysql, about 4-6 times per day… anybody know, what’s happen?

===========================================================[/B]

in syslog i saw this:

[B]Quote:[/B]
Nov 28 17:12:39 db-360-1 mysqld[24190]: key_buffer_size=402653184 Nov 28 17:12:39 db-360-1 mysqld[24190]: read_buffer_size=4190208 Nov 28 17:12:39 db-360-1 mysqld[24190]: max_used_connections=152 Nov 28 17:12:39 db-360-1 mysqld[24190]: max_connections=1000 Nov 28 17:12:39 db-360-1 mysqld[24190]: threads_connected=6 Nov 28 17:12:39 db-360-1 mysqld[24190]: It is possible that mysqld could use up to Nov 28 17:12:39 db-360-1 mysqld[24190]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 192600 K Nov 28 17:12:39 db-360-1 mysqld[24190]: bytes of memory Nov 28 17:12:39 db-360-1 mysqld[24190]: Hope that's ok; if not, decrease some variables in the equation. Nov 28 17:12:39 db-360-1 mysqld[24190]: Nov 28 17:12:39 db-360-1 mysqld[24190]: thd=0x90b37a00 Nov 28 17:12:39 db-360-1 mysqld[24190]: Attempting backtrace. You can use the following information to find out Nov 28 17:12:39 db-360-1 mysqld[24190]: where mysqld died. If you see no messages after this, something went Nov 28 17:12:39 db-360-1 mysqld[24190]: terribly wrong... Nov 28 17:12:39 db-360-1 mysqld[24190]: Cannot determine thread, fp=0x95388268, backtrace may not be correct. Nov 28 17:12:39 db-360-1 mysqld[24190]: Stack range sanity check OK, backtrace follows: Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x81c0619 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x820740e Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x8207547 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x8207d52 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x821bbdc Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x81945db Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x8193922 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x8193c03 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x8143b98 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x82227b5 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x82084f2 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x820b425 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x820fdb7 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x8209fc5 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x820fd77 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x8209fc5 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x820fd77 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x8209fc5 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x820fd77 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x8209fc5 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x820fd77 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x8209fc5 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x820fd77 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x8209fc5 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x820fd77 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x8209fc5 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x820fd77 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x8209fc5 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x820fd77 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x8213ae7 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x822005d Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x8221d80 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x82225ee Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x81d75e5 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x81dbb57 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x81dc010 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x81dd2d8 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0x81ddce4 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0xb7f34240 Nov 28 17:12:39 db-360-1 mysqld[24190]: 0xb7d6f4ae Nov 28 17:12:39 db-360-1 mysqld[24190]: New value of fp=(nil) failed sanity check, terminating stack trace! Nov 28 17:12:39 db-360-1 mysqld[24190]: Please read [URL]http://dev.mysql.com/doc/mysql/en/using-stack-trace.html[/URL] and follow instructions on how to resolve the stack trace. Resolved Nov 28 17:12:39 db-360-1 mysqld[24190]: stack trace is much more helpful in diagnosing the problem, so please do Nov 28 17:12:39 db-360-1 mysqld[24190]: resolve it Nov 28 17:12:39 db-360-1 mysqld[24190]: Trying to get some variables. Nov 28 17:12:39 db-360-1 mysqld[24190]: Some pointers may be invalid and cause the dump to abort... Nov 28 17:12:39 db-360-1 mysqld[24190]: thd->query at 0x88a71048 is invalid pointer Nov 28 17:12:39 db-360-1 mysqld[24190]: thd->thread_id=660194
2

It could be anything from wrong setup (too much memory configured for mysql to use), to corrupted db files (try myisamchk if you use myisam tables) to hardware failures.

First of all I’d suggest to try to check all your tables for corruption and then try to resolve those stack traces and post them here.

3

i used mysqlcheck with check, extended, analyze and all is OK.

and about memory… server have more memory and vmstat say:

[B]Quote:[/B]
procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu---- r b swpd free buff cache si so bi bo in cs us sy id wa 0 0 64 1571004 370576 6077140 0 0 0 1 1 0 9 1 90 0

have you idea for me, how i can check and test if probles is with memory setting?