linux-ax25.org website issues
There seems to be a database problem at the www.linux-ax25.org website. Does anyone have the contact info for the webmaster to let them know there is a problem?
73 de Mike, W1NR
Quoted 3 lines · On Fri, Oct 12, 2007 at 09:22:37AM -0400, Mike McCarthy, W1NR wrote:
There seems to be a database problem at the www.linux-ax25.org website. Does anyone have the contact info for the webmaster to let them know there is a problem?
You might try [email protected] ;-)
What happened is that mysql once more shot itself into the foot:
[root@ftp wikidb_ham]# myisamchk text.MYI
Checking MyISAM file: text.MYI
Data records: 2253 Deleted blocks: 10
myisamchk: warning: Table is marked as crashed
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
- check data record references index: 1
myisamchk: error: Found 2252 keys of 2253
- check record links
myisamchk: error: Keypointers and record positions doesn't match MyISAM-table 'text.MYI' is corrupted
Fix it using switch "-r" or "-o"
[root@ftp wikidb_ham]#
MySQL marking one of its tables as crashed without crashing itself has unfortunately become a somewhat regular event. I think it may have started around the time when the system got migrated from a dual P3 to a Xeon P4 running all 64-bit software so already quite a while ago. Maybe somebody here has seen the same sort of issue?
73 de DL5RB op Ralf
--
Loc. JN47BS / CQ 14 / ITU 28 / DOK A21
Packet: DL5RB@DB0FHN.#BAY.DEU.EU
Quoted 7 lines · On 10/12/07, Ralf Baechle DL5RB <[email protected]> wrote:
Quoted 3 lines · On Fri, Oct 12, 2007 at 09:22:37AM -0400, Mike McCarthy, W1NR wrote:
There seems to be a database problem at the www.linux-ax25.org website. Does anyone have the contact info for the webmaster to let them know there is a problem?
You might try [email protected] ;-)
That'd be too logical for a ham radio operator to figure out (tounge in cheek)
Quoted 19 lines
What happened is that mysql once more shot itself into the foot:
[root@ftp wikidb_ham]# myisamchk text.MYI
Checking MyISAM file: text.MYI
Data records: 2253 Deleted blocks: 10
myisamchk: warning: Table is marked as crashed
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
- check data record references index: 1
myisamchk: error: Found 2252 keys of 2253
- check record links
myisamchk: error: Keypointers and record positions doesn't match MyISAM-table 'text.MYI' is corrupted
Fix it using switch "-r" or "-o"
[root@ftp wikidb_ham]#
Quoted 5 lines
MySQL marking one of its tables as crashed without crashing itself has unfortunately become a somewhat regular event. I think it may have started around the time when the system got migrated from a dual P3 to a Xeon P4 running all 64-bit software so already quite a while ago. Maybe somebody here has seen the same sort of issue?
I see this fairly often on the mysql servers at work - but usually as a result of a hardware crash. We use a shell script that will run a "CHECK TABLE" command on all tables, then follow it with a script that looks at the output to find corrupt tables, and does a "REPAIR TABLE" on them.
The normal operation of MySQL is to lock the table when it detects corruption - that way it can continue to serve other requests that it can complete.
Jeremy, NW7JU
Quoted 5 lines · On Fri, Oct 12, 2007 at 06:16:01PM +0100, Ralf Baechle DL5RB wrote:
MySQL marking one of its tables as crashed without crashing itself has unfortunately become a somewhat regular event. I think it may have started around the time when the system got migrated from a dual P3 to a Xeon P4 running all 64-bit software so already quite a while ago. Maybe somebody here has seen the same sort of issue?
It's happening to me all the time (with my MythTV installation). It started when I migrated from 32-bit to dual-core 64-bit. MySQL is running at all times but corrupts its own tables.
On their forums, lots of people have reported similar problems in the past which have supposedly been fixed. I have the latest version and it still occurs. I have not had a response to my post on the forum yet.
Hamish
Signature · 1 line
Hamish Moffatt VK3SB <[email protected]> <[email protected]>
Quoted 7 lines · Hamish Moffatt
Quoted 5 lines · On Fri, Oct 12, 2007 at 06:16:01PM +0100, Ralf Baechle DL5RB wrote:
MySQL marking one of its tables as crashed without crashing itself has unfortunately become a somewhat regular event. I think it may have started around the time when the system got migrated from a dual P3 to a Xeon P4 running all 64-bit software so already quite a while ago. Maybe somebody here has seen the same sort of issue?
Quoted 7 lines
It's happening to me all the time (with my MythTV installation). It started when I migrated from 32-bit to dual-core 64-bit. MySQL is running at all times but corrupts its own tables.
On their forums, lots of people have reported similar problems in the past which have supposedly been fixed. I have the latest version and it still occurs. I have not had a response to my post on the forum yet.
Oh well, time for the good old UNIX glue - cronjobs ...
Even though as a software developer that solution gives me the creeps ;)
73 de DL5RB op Ralf
--
Loc. JN47BS / CQ 14 / ITU 28 / DOK A21
Packet: DL5RB@DB0FHN.#BAY.DEU.EU