Bug #9900 Server crashed
Submitted: 14 Apr 2005 12:29 Modified: 25 Apr 2005 1:48
Reporter: Broer van Smeden Email Updates:
Status: Won't fix Impact on me:
Category:MySQL Server: InnoDB storage engine Severity:S1 (Critical)
Version:4.1.9 OS:openvms
Assigned to: CPU Architecture:Any

[14 Apr 2005 12:29] Broer van Smeden
After inserting data into the database on VMS (some rows gave constraint failures and were removed), the database seems to be filled. When I wanted to make a backup with the MySQL Adminstrator tool, it failed.
After checking the on VMS, the process MYSQL_SERVER process not running anymore.
Next is the latest logging (including the VMS crash):
I/O thread 0 state: waiting for i/o request (insert buffer thread)
I/O thread 1 state: waiting for i/o request (log thread)
I/O thread 2 state: waiting for i/o request (read thread)
I/O thread 3 state: waiting for i/o request (write thread)
Pending normal aio reads: 0, aio writes: 0,
 ibuf aio reads: 0, log i/o's: 0, sync i/o's: 0
Pending flushes (fsync) log: 0; buffer pool: 0
5632 OS file reads, 704301 OS file writes, 699135 OS fsyncs
0.00 reads/s, 0 avg bytes/read, 0.00 writes/s, 0.00 fsyncs/s
Ibuf for space 0: size 1, free list len 0, seg size 2, is empty
Ibuf for space 0: size 1, free list len 0, seg size 2,
321 inserts, 321 merged recs, 11 merges
Hash table size 69257, used cells 12258, node heap has 14 buffer(s)
0.00 hash searches/s, 0.00 non-hash searches/s
Log sequence number 0 224053198
Log flushed up to   0 224053198
Last checkpoint at  0 224053198
0 pending log writes, 0 pending chkp writes
697098 log i/o's done, 0.00 log i/o's/second
Total memory allocated 35505706; in additional pool allocated 1954176
Buffer pool size   1024
Free buffers       0
Database pages     1010
Modified db pages  0
Pending reads 0
Pending writes: LRU 0, flush list 0, single page 0
Pages read 10839, created 9344, written 36582
0.00 reads/s, 0.00 creates/s, 0.00 writes/s
No buffer pool page gets since the last printout
0 queries inside InnoDB, 0 queries in queue
Main thread id 96130432, state: waiting for server activity
Number of rows inserted 766389, updated 0, deleted 480027, read 761050
0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 0.00 reads/s
InnoDB: ###### Diagnostic info printed to the standard error stream
InnoDB: Error: semaphore wait has lasted > 3600 seconds
InnoDB: We intentionally crash the server, because it appears to be hung.
050413 12:18:30InnoDB: Assertion failure in thread 91919744 in file MYSQL_ROOT:[innobase.srv]srv0srv.c;2 line 1879
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/mysql/en/Forcing_recovery.html
InnoDB: about forcing recovery.
mysqld got signal 10;
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.

It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 80383 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

%CMA-F-EXIT_THREAD, current thread has been requested to exit
%TRACE-F-TRACEBACK, symbolic stack dump follows
  image    module    routine             line      rel PC           abs PC      
 PTHREAD$RTL                                0 000000000002C50C 000000007BCEC50C
 PTHREAD$RTL                                0 0000000000052DC8 000000007BD12DC8
                                            0 FFFFFFFF8015B764 FFFFFFFF8015B764
                                            0 FFFFFFFF8028685C FFFFFFFF8028685C
                                            0 FFFFFFFF80B1A094 FFFFFFFF80B1A094
                                            0 FFFFFFFF80B19BC4 FFFFFFFF80B19BC4
                                            0 FFFFFFFF8016D55C FFFFFFFF8016D55C
                                            0 FFFFFFFF8016D55C FFFFFFFF8016D55C
----- above condition handler called with exception 0000000C:
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000000000000000, PC=00000000002D5914, PS=0000001B
----- end of exception message
                                            0 FFFFFFFF800C1CCC FFFFFFFF800C1CCC
 MYSQLD  SRV0SRV  srv_error_monitor_thread
                                        50794 0000000000003A34 00000000002D5914
 PTHREAD$RTL                                0 000000000003E504 000000007BCFE504
 PTHREAD$RTL                                0 000000000002C630 000000007BCEC630
                                            0 0000000000000000 0000000000000000
 PTHREAD$RTL                                                 ?                ?
                                            0 FFFFFFFF8028759C FFFFFFFF8028759C
-RMS-E-FNF, file not found
  WDVO         job terminated at 13-APR-2005 12:18:31.03

  Accounting information:
  Buffered I/O count:            4198603      Peak working set size:     117680
  Direct I/O count:              3033549      Peak virtual size:         430576
  Page faults:                     15167      Mounted volumes:                0
  Charged CPU time:        0 00:33:10.66      Elapsed time:       9 00:15:13.82

How to repeat:
Not clear
[14 Apr 2005 16:40] Heikki Tuuri

How did you port InnoDB to OpenVMS?

[15 Apr 2005 9:09] Broer van Smeden
We use the port of "http://www.pi-net.dyndns.org/anonymous/kits/#mysql done by from Jean-François Piéronne.
Actually I might uderstand what is happening.
I've de database filled and want to delete a foreign key constraint using the (gui running under windows) MYSQL administrator tool. When executing the drop statement, the statement will not finish and the tool seems to be hanging. This might also cause a hanging thread.
[25 Apr 2005 1:48] Heikki Tuuri

Unfortunately, we have no plans of porting InnoDB to OpenVMS.

If the writer of the port can fix this problem, and contribute a patch, we will look into this.