View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000200 | MySQL v5 for OS/2 & eComStation | public | 2007-07-18 07:50 | 2020-08-24 03:14 | |
Reporter | evgen | Assigned To | psmedley | ||
Priority | normal | Severity | major | Reproducibility | sometimes |
Status | closed | Resolution | unable to reproduce | ||
Summary | 0000200: mysld posible not thread-safe | ||||
Description | Server version: 5.0.45 Source distribution, libc063 build hang up periodically, seems anywere at pthread_ - aftre pxpMyAdmin "reair" operation - while running seems that v4 can make autorestart an some condition and v5 can't | ||||
Additional Information | InnoDB: tablespace but not the InnoDB log files. See 11:43 InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html InnoDB: for more information. 070718 3:16:24InnoDB: Assertion failure in thread 11 in file os0sync.c line 151 InnoDB: Failing assertion: 0 == pthread_cond_init(&(event->cond_var), NULL) 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. Killed by SIGSEGV pid=0x00e4 ppid=0x0083 tid=0x000b slot=0x00e2 pri=0x020e mc=0x0001 D:\BIN\MYSQL5\BIN\MYSQLD.EXE MYSQLD 0:003204e0 cs:eip=005b:003304e0 ss:esp=0053:0299d00c ebp=0299d024 ds=0053 es=0053 fs=150b gs=0000 efl=00012246 eax=0000018d ebx=20f5fdd0 ecx=00000000 edx=00000000 edi=20efa6dc esi=0000005a Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it. | ||||
Tags | No tags attached. | ||||
|
A number of assertions like: 070720 8:09:19InnoDB: Assertion failure in thread 13 in file os0sync.c line 151 InnoDB: Failing assertion: 0 == pthread_cond_init(&(event->cond_var), NULL) |
|
Next screanshot. Recreate data bases from the scratch: * create initials, * then create new db and import it with mysql -> source * next check with mysqlcheck.exe --all-databases - no errors found * next create second db and have trape when do mysql -> source... UNIX Socket is \socket\MySQL 18:31 070720 17:22:54 [Note] D:\bin\mysql5\bin\mysqld.exe: ready for connections. Version: '5.0.45' socket: '\socket\MySQL' port: 3306 Source distribution 070720 18:30:24InnoDB: Assertion failure in thread 11 in file os0sync.c line 151 InnoDB: Failing assertion: 0 == pthread_cond_init(&(event->cond_var), NULL) 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. Killed by SIGSEGV pid=0x16eb ppid=0x1699 tid=0x000b slot=0x00c1 pri=0x021f mc=0x0001 D:\BIN\MYSQL5\BIN\MYSQLD.EXE MYSQLD 0:003204e0 cs:eip=005b:003304e0 ss:esp=0053:0295dc4c ebp=0295dc64 ds=0053 es=0053 fs=150b gs=0000 efl=00012246 eax=0000018d ebx=20e86110 ecx=00000000 edx=00000000 edi=20e8537c esi=0000005a Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it. |
|
Next one. After mysql crash at db import it wrotes: 070725 15:48:21070725 15:48:21 [ERROR] Cannot find table rapid/logging from the internal data dictionary of InnoDB though the .frm file for the table exists. At deleting datebase: DROP DATABASE `rapid` MySQL said: #1051 - (ER_BAD_TABLE_ERROR - Message: Unknown table '%s' ) It is possible to delete logging.frm by hands from F:\bin\mysql5\data\rapid\logging.frm --------- So for some reason at Mysql restart logging.frm is not deleted |
|
Please test with MySQL v5.1 - many things are fixed since 5.0.45 |
|
Mark as resolved pending feedback due to timeframe since original bug report |
Date Modified | Username | Field | Change |
---|---|---|---|
2007-07-18 07:50 | evgen | New Issue | |
2007-07-20 08:01 | evgen | Note Added: 0000668 | |
2007-07-20 14:43 | evgen | Note Added: 0000669 | |
2007-07-25 12:31 | evgen | Note Added: 0000679 | |
2010-07-31 10:34 | psmedley | Note Added: 0001683 | |
2010-07-31 10:34 | psmedley | Assigned To | => psmedley |
2010-07-31 10:34 | psmedley | Status | new => feedback |
2011-10-22 23:39 | psmedley | Note Added: 0002021 | |
2011-10-22 23:39 | psmedley | Status | feedback => resolved |
2011-10-22 23:39 | psmedley | Resolution | open => unable to reproduce |
2020-08-24 03:14 | psmedley | Status | resolved => closed |