The X
16-03-2005, 00:33
sono davvero in crisi perchè sono diversi giorni ke il mysql va in tilt e non riesco a capire quale sia il problema MA sopratutto l'origine di tutti i mali...
Questo è il report ke appare nel syslog ogni volta ke mysqld va in tilt
mysqld[15202]: mysqld got signal 11;
mysqld[15202]: This could be because you hit a bug. It is also possible that this binary
mysqld[15202]: or one of the libraries it was linked against is corrupt, improperly built,
mysqld[15202]: or misconfigured. This error can also be caused by malfunctioning hardware.
mysqld[15202]: We will try our best to scrape up some info that will hopefully help diagnose
mysqld[15202]: the problem, but since we have already crashed, something is definitely wrong
mysqld[15202]: and this may fail.
mysqld[15202]:
mysqld[15202]: key_buffer_size=367001600
mysqld[15202]: read_buffer_size=1044480
mysqld[15202]: max_used_connections=138
mysqld[15202]: max_connections=400
mysqld[15202]: threads_connected=130
mysqld[15202]: It is possible that mysqld could use up to
mysqld[15202]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1175996 K
mysqld[15202]: bytes of memory
mysqld[15202]: Hope that's ok; if not, decrease some variables in the equation.
mysqld[15202]:
mysqld[15202]: thd=0x8895e00
mysqld[15202]: Attempting backtrace. You can use the following information to find out
mysqld[15202]: where mysqld died. If you see no messages after this, something went
mysqld[15202]: terribly wrong...
mysqld[15202]: Cannot determine thread, fp=0xbb3ff2e8, backtrace may not be correct.
mysqld[15202]: Stack range sanity check OK, backtrace follows:
mysqld[15202]: 0x8152d61
mysqld[15202]: 0x4004cf54
mysqld[15202]: 0x84934ed
mysqld[15202]: 0x84768ca
mysqld[15202]: 0x82005e1
mysqld[15202]: 0x81695e2
mysqld[15202]: 0x8163f9b
mysqld[15202]: 0x816bf83
mysqld[15202]: 0x81630bd
mysqld[15202]: 0x4004a0ba
mysqld[15202]: 0x40189d6a
mysqld[15202]: New value of fp=(nil) failed sanity check, terminating stack trace!
mysqld[15202]: Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
mysqld[15202]: stack trace is much more helpful in diagnosing the problem, so please do
mysqld[15202]: resolve it
mysqld[15202]: Trying to get some variables.
mysqld[15202]: Some pointers may be invalid and cause the dump to abort...
mysqld[15202]: thd->query at 0x889f268 = SELECT vota.PROD_ID, product.NOME, product.LAST_MOD, LINK_EXT,TOP_ID, COUNT(*) AS NUM, SUM(COUNT) AS TOTALE, DATA_SCAD, ATTIVO FROM vota, product WHERE vota.PROD_ID IN ( 0, 154, 145, 163, 158, 148, 355, 162, 122)
mysqld[15202]: thd->thread_id=39
mysqld[15202]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains
mysqld[15202]: information that should help you find out what is causing the crash.
mysqld_safe[15549]: Number of processes running now: 0
mysqld_safe[15551]: restarted
Qlc anima pia mi può dare 1 mano ? :(
TNK
Questo è il report ke appare nel syslog ogni volta ke mysqld va in tilt
mysqld[15202]: mysqld got signal 11;
mysqld[15202]: This could be because you hit a bug. It is also possible that this binary
mysqld[15202]: or one of the libraries it was linked against is corrupt, improperly built,
mysqld[15202]: or misconfigured. This error can also be caused by malfunctioning hardware.
mysqld[15202]: We will try our best to scrape up some info that will hopefully help diagnose
mysqld[15202]: the problem, but since we have already crashed, something is definitely wrong
mysqld[15202]: and this may fail.
mysqld[15202]:
mysqld[15202]: key_buffer_size=367001600
mysqld[15202]: read_buffer_size=1044480
mysqld[15202]: max_used_connections=138
mysqld[15202]: max_connections=400
mysqld[15202]: threads_connected=130
mysqld[15202]: It is possible that mysqld could use up to
mysqld[15202]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1175996 K
mysqld[15202]: bytes of memory
mysqld[15202]: Hope that's ok; if not, decrease some variables in the equation.
mysqld[15202]:
mysqld[15202]: thd=0x8895e00
mysqld[15202]: Attempting backtrace. You can use the following information to find out
mysqld[15202]: where mysqld died. If you see no messages after this, something went
mysqld[15202]: terribly wrong...
mysqld[15202]: Cannot determine thread, fp=0xbb3ff2e8, backtrace may not be correct.
mysqld[15202]: Stack range sanity check OK, backtrace follows:
mysqld[15202]: 0x8152d61
mysqld[15202]: 0x4004cf54
mysqld[15202]: 0x84934ed
mysqld[15202]: 0x84768ca
mysqld[15202]: 0x82005e1
mysqld[15202]: 0x81695e2
mysqld[15202]: 0x8163f9b
mysqld[15202]: 0x816bf83
mysqld[15202]: 0x81630bd
mysqld[15202]: 0x4004a0ba
mysqld[15202]: 0x40189d6a
mysqld[15202]: New value of fp=(nil) failed sanity check, terminating stack trace!
mysqld[15202]: Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
mysqld[15202]: stack trace is much more helpful in diagnosing the problem, so please do
mysqld[15202]: resolve it
mysqld[15202]: Trying to get some variables.
mysqld[15202]: Some pointers may be invalid and cause the dump to abort...
mysqld[15202]: thd->query at 0x889f268 = SELECT vota.PROD_ID, product.NOME, product.LAST_MOD, LINK_EXT,TOP_ID, COUNT(*) AS NUM, SUM(COUNT) AS TOTALE, DATA_SCAD, ATTIVO FROM vota, product WHERE vota.PROD_ID IN ( 0, 154, 145, 163, 158, 148, 355, 162, 122)
mysqld[15202]: thd->thread_id=39
mysqld[15202]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains
mysqld[15202]: information that should help you find out what is causing the crash.
mysqld_safe[15549]: Number of processes running now: 0
mysqld_safe[15551]: restarted
Qlc anima pia mi può dare 1 mano ? :(
TNK