Hi,
Apollogies to all those that had problems over the last few days, I was moving to Virginia over the weekend and changing ISPs.
I am investigating what caused the lastest bout of database corruption, but I believe that it may have been deliberate ...
However, I have put a quick mechanism in place that will allow Flash and other (yet-to-be-determined) admins to fix corrupted tables.
Thanks for all the e-mails letting me know about the problem. I am now back on line so I'll be keeping an eye on things.
Cheers
JohnM
Forum problems - Fixed for now ?
Re: Forum problems - Fixed for now ?
Good news that it's working again 
http://www.vbulletin.com/forum/showthread.php?t=69803
"Section 1. MySQL database/table corruption - why does it occur?
--------------------------------------------------------------------------------
Facts: [Source: http://www.mysql.com/doc/en/Table_types.html ]
- As of MySQL Version 3.23.6, you can choose between three basic table formats (ISAM, HEAP and MyISAM).
- Newer versions of MySQL support additional table types (InnoDB, or BDB), depending on how you compile it.
- The default table type is usually MyISAM. MyISAM table is made up of 3 actual files on disk. The table definition file, '.frm', the table index is stored in a file with the `.MYI' (MYIndex) extension, and the actual data is stored in a file with the `.MYD' (MYData) extension.
- vBulletin's table type is MyISAM for all tables except Sessions table which is HEAP format (in memory only table)
- It's important to get the exact/specific mysql error code to help diagnose what type of corruption is occuring.
--------------------------------------------------------------------------------
Reasons for corruption:
Database corruption generally server side related, and has nothing to do with what the end user/vb members do on your forums [ http://www.mysql.com/doc/en/Corrupted_M ... ables.html ]. The following are the main reasons for database corruption:
- The mysqld process being killed in the middle of a write.
- Unexpected shutdown of the computer (for example, if the computer is turned off).
- A hardware error such as faulty memory/cpu/motherboard and or hard drive.
- You are using an external program (like myisamchk) on a live table.
- A software bug in the MySQL or MyISAM code
Symptoms of corruption
When you get error messages such as:
- Incorrect key file for table
- tbl_name.frm' is locked against change
- Can't find file `tbl_name.MYI' (Errcode: ###)
- Unexpected end of file
- Record file is crashed
- Got error ### from table handler..."
==========================
A full harddisk may cause problem too:
http://www.karakas-online.de/forum/view ... 2805૵
This page seems useful:JohnMurga wrote:I am investigating what caused the lastest bout of database corruption, but I believe that it may have been deliberate ...
http://www.vbulletin.com/forum/showthread.php?t=69803
"Section 1. MySQL database/table corruption - why does it occur?
--------------------------------------------------------------------------------
Facts: [Source: http://www.mysql.com/doc/en/Table_types.html ]
- As of MySQL Version 3.23.6, you can choose between three basic table formats (ISAM, HEAP and MyISAM).
- Newer versions of MySQL support additional table types (InnoDB, or BDB), depending on how you compile it.
- The default table type is usually MyISAM. MyISAM table is made up of 3 actual files on disk. The table definition file, '.frm', the table index is stored in a file with the `.MYI' (MYIndex) extension, and the actual data is stored in a file with the `.MYD' (MYData) extension.
- vBulletin's table type is MyISAM for all tables except Sessions table which is HEAP format (in memory only table)
- It's important to get the exact/specific mysql error code to help diagnose what type of corruption is occuring.
--------------------------------------------------------------------------------
Reasons for corruption:
Database corruption generally server side related, and has nothing to do with what the end user/vb members do on your forums [ http://www.mysql.com/doc/en/Corrupted_M ... ables.html ]. The following are the main reasons for database corruption:
- The mysqld process being killed in the middle of a write.
- Unexpected shutdown of the computer (for example, if the computer is turned off).
- A hardware error such as faulty memory/cpu/motherboard and or hard drive.
- You are using an external program (like myisamchk) on a live table.
- A software bug in the MySQL or MyISAM code
Symptoms of corruption
When you get error messages such as:
- Incorrect key file for table
- tbl_name.frm' is locked against change
- Can't find file `tbl_name.MYI' (Errcode: ###)
- Unexpected end of file
- Record file is crashed
- Got error ### from table handler..."
==========================
A full harddisk may cause problem too:
http://www.karakas-online.de/forum/view ... 2805૵
[url=http://puppylinux.org]Puppylinux.org - Community home page of Puppy Linux[/url] hosted by Barry (creator of Puppy), created and maintained by the [url=http://puppylinux.org/user/readarticle.php?article_id=8]Puppy Linux Foundation[/url] since 2005
-
Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
Hope you settle in OK John.Like a speeding bullet - two new forums and this page came into being in the few days of the move . . .
http://puppylinux.org/wikka/ForumsPuppy
Hope everything works out OK
Welcome to the South
Glad to hear you moved away from the Big Apple -Ted
-Ted
Well done, John & many thanks for your great contribution.
Are you +5 or +6hrs, now?
Barry's site has gone 404. If you are going to take it down permanently, Barry, any chance you could get together with John to meld the posts you received into his board. I speak in ignorance of these things (as usual) but maybe some date-ordering might work?
Are you +5 or +6hrs, now?
Barry's site has gone 404. If you are going to take it down permanently, Barry, any chance you could get together with John to meld the posts you received into his board. I speak in ignorance of these things (as usual) but maybe some date-ordering might work?