I'm just reporting it and don't yet have a rhyme or reason but 4.0.24 will not remain stable on my system for more than 48 hours and usually dies in the middle of the night under heavy use. Backleveling to 4.0.22 for now. -this is an isam installation
Theese kind of errors are very difficult to reproduce and to debug. So I'm not trying to give an answer here. anyway permit me to quote here MySQL documentation here [1] [quote] [...] when the improved MyISAM engine was introduced as the default. ISAM is deprecated [...] you are advised to convert any remaining ISAM tables to MyISAM as soon as possible. To convert an ISAM table to a MyISAM table, use an ALTER TABLE statement: mysql> ALTER TABLE tbl_name TYPE = MYISAM; [...] Many of the properties of MyISAM tables are also true for ISAM tables. However, there are also many differences. The following list describes some of the ways that ISAM is distinct from MyISAM: [snip list of propertyes that isam lack and exist in myisam] # Tables are checked and repaired with isamchk rather than with myisamchk. # Tables are compressed with pack_isam rather than with myisampack. [/quote] The only suggestion I'm capable to give you is to schedule a switch to myisam table types as soon as possible. Using the "alter table" syntax permit you to do this also one table at time (please test and backup before do it). [1] http://dev.mysql.com/doc/mysql/en/isam-storage-engine.html
I'm in agreement with Francesco that you should consider MyISAM rather than the old ISAM engine. If only for the fact that you can do online checks on it instead of being forced to do offline checks. If your data set isn't too large or propiertary, could you try to reproduce it on another machine, and then possibly put together instructions on reproducing the failure?
My mistake, I said the wrong type, I split my time between the mainframe and PC. It is Type=MyISAM. I'll do what I can about duplicating the error. If the database goes down in the next two days I'll know I was wrong in my assumptions. Clearly I am spoiled on MySQL's stablity, but the last week has been a rocky road and has started to affect revenues.
Apache has been backleveled to prior version. 20 Mar 2005; Elfyn McBratney <beu@gentoo.org> apache-1.3.33-r1.ebuild, +apache-1.3.33-r2.ebuild: Version bump to fix incompatabilities with mod_ssl and older dbm libs. 1.3.33-r1 -> -r2. Marked stable on x86 for bug #86052. Has been superseded with: 03 Apr 2005; Elfyn McBratney <beu@gentoo.org> apache-1.3.33-r1.ebuild: Back into testing for you - hard masked; going back in once arches have confirmed that it's working correctly with mod_ssl (or someone from the apache herd nurses its stabilisation *wink* ;) Since I'm also having problems with the version of MySQL that previously had been stable I'm taking their word for it that the problem is Apache related. Closing.
