InnoDB: Error: semaphore wait has lasted > 600 seconds
InnoDB: We intentionally crash the server, because it appears to be hung.
100622 17:12:08  InnoDB: Assertion failure in thread 1387125056 in file srv/srv0srv.c line 2342
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.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
100622 17:12:08 - mysqld got signal 6 ;
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=2147483648
read_buffer_size=4194304
max_used_connections=2049
max_threads=2048
thread_count=2049
connection_count=2049
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 44062624 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
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...
stack_bottom = (nil) thread_stack 0x40000
/usr/libexec/mysqld(my_print_stacktrace+0x21)[0x858bb7]
/usr/libexec/mysqld(handle_segfault+0x366)[0x58aa38]
/lib64/libpthread.so.0[0x3d8900e4c0]
/lib64/libc.so.6(gsignal+0x35)[0x3d88430215]
/lib64/libc.so.6(abort+0x110)[0x3d88431cc0]
/usr/libexec/mysqld[0x783f2b]
/lib64/libpthread.so.0[0x3d89006367]
/lib64/libc.so.6(clone+0x6d)[0x3d884d30ad]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
100622 17:20:23 mysqld_safe Number of processes running now: 0
100622 17:20:23 mysqld_safe mysqld restarted
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
100622 17:20:32  InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 143404745672560
100622 17:20:45  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 143404750915072
InnoDB: Doing recovery: scanned up to log sequence number 143404756157952
InnoDB: Doing recovery: scanned up to log sequence number 143404761400832
InnoDB: Doing recovery: scanned up to log sequence number 143404766643712

[a lot more of theese...]

InnoDB: Doing recovery: scanned up to log sequence number 143406355252736
InnoDB: Doing recovery: scanned up to log sequence number 143406357429818
InnoDB: 2 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 6805 row operations to undo
InnoDB: Trx id counter is 1892874600
100622 17:46:51  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 7
2 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
InnoDB: In a MySQL replication slave the last master binlog file
InnoDB: position 0 1073442905, file name thales-replmaster-bin.000054
InnoDB: Last MySQL binlog file position 0 955486931, file name ./thalesmaster-bin.044120
100622 17:48:46  InnoDB: Rolling back trx with id 189287440B, 24 rows to undo
InnoDB: Dropping table with id 0 37 in recovery if it exists
100622 17:48:50  InnoDB: error: space object of table'agent/LinkObs_agent1',
InnoDB: space id 25 did not exist in memory. Retrying an open.
100622 17:48:50  InnoDB: Assertion failure in thread 47925437559984 in file fil/fil0fil.c line 3001
InnoDB: Failing assertion: flags != DICT_TF_COMPACT
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.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
100622 17:48:50 - mysqld got signal 6 ;
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=2147483648
read_buffer_size=4194304
max_used_connections=0
max_threads=2048
thread_count=0
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 44062624 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
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...
stack_bottom = (nil) thread_stack 0x40000
/usr/libexec/mysqld(my_print_stacktrace+0x21)[0x858bb7]
/usr/libexec/mysqld(handle_segfault+0x366)[0x58aa38]
/lib64/libpthread.so.0[0x3d8900e4c0]
/lib64/libc.so.6(gsignal+0x35)[0x3d88430215]
/lib64/libc.so.6(abort+0x110)[0x3d88431cc0]
/usr/libexec/mysqld[0x7e9d47]
/usr/libexec/mysqld[0x7dda49]
/usr/libexec/mysqld[0x7de6e4]
/usr/libexec/mysqld[0x796815]
/usr/libexec/mysqld[0x787c1f]
/usr/libexec/mysqld[0x71f005]
/usr/libexec/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x683575]
/usr/libexec/mysqld[0x6fdb59]
/usr/libexec/mysqld(_Z11plugin_initPiPPci+0x94d)[0x7015c1]
/usr/libexec/mysqld[0x58e18b]
/usr/libexec/mysqld(_Z11mysqld_mainiPPc+0x72e)[0x58f110]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x3d8841d974]
/usr/libexec/mysqld[0x4d3b79]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
100622 17:48:52 mysqld_safe mysqld from pid file /var/lib/mysql/thales.opoint.com.pid ended