Hi there, I have a problem with mysql. I have an application basically to track clicks to my website and last night it crashed. Can you have a look aty my situation? I run a server with 2GB RAM and a XEON processor!
Thank you. - Max - error log ----- InnoDB: Warning: a long semaphore wait: --Thread 1175628720 has waited at row0mysql.c line 1683 for 241.00 seconds the semaphore: Mutex at 40e1b168 created file srv0srv.c line 1647, lock var 1 Last time reserved in file trx0trx.c line 309, waiters flag 1 InnoDB: ###### Starts InnoDB Monitor for 30 secs to print diagnostic info: InnoDB: ###### Diagnostic info printed to the standard output InnoDB: Warning: a long semaphore wait: --Thread 1175628720 has waited at row0mysql.c line 1683 for 674.00 seconds the semaphore: Mutex at 40e1b168 created file srv0srv.c line 1647, lock var 1 Last time reserved in file trx0trx.c line 309, waiters flag 1 InnoDB: Error: semaphore wait has lasted > 600 seconds InnoDB: We intentionally crash the server, because it appears to be hung. 050225 15:29:55 InnoDB: Assertion failure in thread 1165138864 in file sync0arr.c line 934 InnoDB: Failing assertion: 0 InnoDB: We intentionally generate a memory trap. InnoDB: Send a detailed bug report to mysql@lists.mysql.com 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=8388600 read_buffer_size=131072 max_used_connections=652 max_connections=1000 threads_connected=640 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 2184184 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. You seem to be running 32-bit Linux and have 640 concurrent connections. If you have not changed STACK_SIZE in LinuxThreads and built the binary yourself, LinuxThreads is quite likely to steal a part of the global heap for the thread stack. Please read http://www.mysql.com/doc/L/i/Linux.html 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=0x4572955c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x80d9be4 0xca1f18 (nil) 0xc9b79c 0xaae27a New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://www.mysql.com/doc/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 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. 050225 15:31:46 Error reading packet from server: Lost connection to MySQL server during query (server_errno=2013) 050225 15:31:46 Slave I/O thread: Failed reading log event, reconnecting to retry, log 's2-bin.003' position 99034 InnoDB: Thread 1356766128 stopped in file ut0mem.c line 157 InnoDB: Thread 1230535600 stopped in file trx0trx.c line 288 InnoDB: Thread 1310583728 stopped in file ../../innobase/fil/../include/sync0sync.ic line 109 Number of processes running now: 0 050225 15:36:08 mysqld restarted 050225 15:36:23 InnoDB: Database was not shut down normally. InnoDB: Starting recovery from log files... InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 1132661722 InnoDB: Doing recovery: scanned up to log sequence number 0 1132661722 InnoDB: In a MySQL replication slave the last master binlog file -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
