(gdb) where #0 0x8828f7b7 in sigsuspend () from /lib/libc.so.6 #1 0x88246bbf in sigsuspend () from /usr/lib/libthr.so.2 #2 0x8853c10d in sig_wait_basic () from /usr/local/libexec/apache22/mod_speedycgi.so #3 0x8853c13f in speedy_sig_wait () from /usr/local/libexec/apache22/mod_speedycgi.so #4 0x8853b656 in speedy_frontend_connect () from /usr/local/libexec/apache22/mod_speedycgi.so #5 0x8853d491 in cgi_handler () from /usr/local/libexec/apache22/mod_speedycgi.so #6 0x08071b4a in ap_run_handler () #7 0x08071f15 in ap_invoke_handler () #8 0x0807c969 in ap_process_request () #9 0x0807a571 in ap_process_http_connection () #10 0x080773fa in ap_run_process_connection () #11 0x0807ffe7 in child_main () #12 0x0808021e in make_child () #13 0x080802ac in startup_children () #14 0x08080a9e in ap_mpm_run () #15 0x08061ae8 in main () (gdb)
InnoDB: Warning: a long semaphore wait: --Thread 485456896 has waited at btr0cur.c line 366 for 242.00 seconds the semaphore: S-lock on RW-latch at 0xa74dcb4 created in file dict0dict.c line 3706 a writer (thread id 481861120) has reserved it in mode wait exclusive number of readers 1, waiters flag 1 Last time read locked in file btr0cur.c line 366 Last time write locked in file btr0cur.c line 359 (ry InnoDB: ###### Starts InnoDB Monitor for 30 secs to print diagnostic info: InnoDB: Pending preads 0, pwrites 0
===================================== 071120 21:19:52 INNODB MONITOR OUTPUT ===================================== (ry ---------------------------- END OF INNODB MONITOR OUTPUT ============================ InnoDB: ###### Diagnostic info printed to the standard error stream InnoDB: Error: semaphore wait has lasted > 600 seconds InnoDB: We intentionally crash the server, because it appears to be hung. 071120 21:29:24InnoDB: Assertion failure in thread 140652032 in file srv0srv.c line 2093 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html InnoDB: about forcing recovery. 071120 21:29:24 - 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. 0720株価【870】 △△ ◆cZfSunOs.U 2007/11/21(水) 00:19:37ID:AjCTetBU0>>719 done. 0721株価【870】 △△ ◆cZfSunOs.U 2007/11/22(木) 02:22:21ID:luYPmZXZ0>>719 のはダウングレード後，今のところ落ち着いてる模様．
Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, ch2qb5@banana3198.maido3.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
