All of lore.kernel.org
 help / color / mirror / Atom feed
* linux-ax25.org website issues
@ 2007-10-12 13:22 Mike McCarthy, W1NR
  2007-10-12 17:16 ` Ralf Baechle DL5RB
  0 siblings, 1 reply; 5+ messages in thread
From: Mike McCarthy, W1NR @ 2007-10-12 13:22 UTC (permalink / raw)
  To: opensuse-ham, linux-hams

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: linux-ax25.org website issues
  2007-10-12 13:22 linux-ax25.org website issues Mike McCarthy, W1NR
@ 2007-10-12 17:16 ` Ralf Baechle DL5RB
  2007-10-12 19:27   ` Jeremy Utley
  2007-10-13  1:06   ` Hamish Moffatt
  0 siblings, 2 replies; 5+ messages in thread
From: Ralf Baechle DL5RB @ 2007-10-12 17:16 UTC (permalink / raw)
  To: Mike McCarthy, W1NR; +Cc: opensuse-ham, linux-hams

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 webmaster@linux-ax25.org ;-)

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: linux-ax25.org website issues
  2007-10-12 17:16 ` Ralf Baechle DL5RB
@ 2007-10-12 19:27   ` Jeremy Utley
  2007-10-13  1:06   ` Hamish Moffatt
  1 sibling, 0 replies; 5+ messages in thread
From: Jeremy Utley @ 2007-10-12 19:27 UTC (permalink / raw)
  To: Ralf Baechle DL5RB; +Cc: linux-hams

On 10/12/07, Ralf Baechle DL5RB <ralf@linux-mips.org> wrote:
> 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 webmaster@linux-ax25.org ;-)

That'd be too logical for a ham radio operator to figure out (tounge in cheek)

>
> 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?

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: linux-ax25.org website issues
  2007-10-12 17:16 ` Ralf Baechle DL5RB
  2007-10-12 19:27   ` Jeremy Utley
@ 2007-10-13  1:06   ` Hamish Moffatt
  2007-10-15 17:40     ` Ralf Baechle DL5RB
  1 sibling, 1 reply; 5+ messages in thread
From: Hamish Moffatt @ 2007-10-13  1:06 UTC (permalink / raw)
  To: linux-hams

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
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: linux-ax25.org website issues
  2007-10-13  1:06   ` Hamish Moffatt
@ 2007-10-15 17:40     ` Ralf Baechle DL5RB
  0 siblings, 0 replies; 5+ messages in thread
From: Ralf Baechle DL5RB @ 2007-10-15 17:40 UTC (permalink / raw)
  To: linux-hams

On Sat, Oct 13, 2007 at 11:06:17AM +1000, Hamish Moffatt wrote:

> 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.

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2007-10-15 17:40 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-10-12 13:22 linux-ax25.org website issues Mike McCarthy, W1NR
2007-10-12 17:16 ` Ralf Baechle DL5RB
2007-10-12 19:27   ` Jeremy Utley
2007-10-13  1:06   ` Hamish Moffatt
2007-10-15 17:40     ` Ralf Baechle DL5RB

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.