Oct 7 11:08:36 h1314631 mysqld[32734]: 071007 11:08:36 InnoDB:
Started; log sequence number 0 1346871925
Oct 7 11:08:38 h1314631 mysqld[32734]: 071007 11:08:38 [Note]
/usr/sbin/mysqld: ready for connections.
Oct 7 11:08:38 h1314631 mysqld[32734]: Version:
'5.0.45-Debian_1~bpo.1' soc
8:38 h1314631 mysqld[32734]: Version:
'5.0.45-Debian_1~bpo.1' socket: '/var/run/mysqld/mysqld.sock' port:
3306 Debian etch distribution
As far as I understand, this means, that the MySQL Server crashed and
mysqld_safe noticed that and restarted it.
I also see much databas
bian_1~bpo.1' socket: '/var/run/mysqld/mysqld.sock' port:
3306 Debian etch distribution
As far as I understand, this means, that the MySQL Server crashed and
mysqld_safe noticed that and restarted it.
I also see much database corruption, but I somewhat run into a chicken
&
ket: '/var/run/mysqld/mysqld.sock' port:
3306 Debian etch distribution
As far as I understand, this means, that the MySQL Server crashed and
mysqld_safe noticed that and restarted it.
I also see much database corruption, but I somewhat run into a chicken &
egg problem here. I don&
<[EMAIL PROTECTED]> wrote:
Sorry it is */*.MYI instead of */*.MYD
> -Original Message-
> From: Gregory Machin [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 22, 2007 12:02 PM
> To: Jean-Sebastien Pilon
> Cc: mysql@lists.mysql.com
> Subject: Re: database corruption ? h
Sorry it is */*.MYI instead of */*.MYD
> -Original Message-
> From: Gregory Machin [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 22, 2007 12:02 PM
> To: Jean-Sebastien Pilon
> Cc: mysql@lists.mysql.com
> Subject: Re: database corruption ? how to fix ?
>
>
March 22, 2007 8:41 AM
> To: mysql@lists.mysql.com
> Subject: database corruption ? how to fix ?
>
> hi
> when i try and do a mysqldump of the databases it exites with
> this error
>
> [EMAIL PROTECTED] diaendomet]# mysqldump -ucojjohealth -p --all-databases >
> al
t; To: mysql@lists.mysql.com
> Subject: database corruption ? how to fix ?
>
> hi
> when i try and do a mysqldump of the databases it exites with
> this error
>
> [EMAIL PROTECTED] diaendomet]# mysqldump -ucojjohealth -p --all-databases >
> alldatabases.sql
> Enter password:
>
hi
when i try and do a mysqldump of the databases it exites with this error
[EMAIL PROTECTED] diaendomet]# mysqldump -ucojjohealth -p --all-databases >
alldatabases.sql
Enter password:
mysqldump: Got error: 29: File '../diaendomet/users.MYD' not found
(Errcode: 2) when using LOCK TABLES
so i ran
To restore specific tables (or full databases) I often use this trick (I'm
just writing this down from memory, you would want to run it through a
test environment first). It runs something like this:
1) MASTER: query> FLUSH TABLES WITH READ LOCK;
query> SHOW MASTER STATUS\G
2) SLAVE:
Yes thats very true, as the corrupt slave would pick up from where it left
and its quite posssible that the record was already updated on the healthy
slave from the master, causing the replication to fail, but having said that
may be you could do this
1) stop the healthy slave
2) put a global read
Hi Kishore,
That's an interesting idea. However, given that the healthy slave
and the corrupt slave now have different values for
Exec_Master_Log_Pos, would restoring the tables from the healthy
slave necessarily be a good move?
I would be worried that the corrupt slave's counter positio
an "rsync" with the right options from the unaffected slave to the corrupt
one might prove to be an elegant technique
Kishore Jalleda
On 3/7/06, Michael Jeung <[EMAIL PROTECTED]> wrote:
>
> Hi Folks,
>
> We've got a Single Master/Multiple Slave environment.
> Recently, we had some corruption on o
Hi Folks,
We've got a Single Master/Multiple Slave environment.
Recently, we had some corruption on one of the slaves and I had to
repair the affected tables.
After the repair completed, some of the rows on the slave had been
deleted - so the Master and the Slave weren't exactly in synch.
Hi!
On Aug 09, Daniel Kasak wrote:
> Hi all.
>
> I've been testing out mysql-5.0.10 on my Powerbook ( Gentoo Linux PPC ),
> and I've hit an incredibly unfortunate bug. It is demonstrated
> adequately with the following:
...
> Is anyone interested in examining what went wrong? ie should I create
On Wednesday 10 August 2005 10:23 am, Daniel Kasak wrote:
> Fajar Priyanto wrote:
> >Well, it's not 5.0.x, it's 4.0.25-standard. I'm not sure how the error
> > appears in the first place. What I notice when I open the database using
> > phpMyadmin is that that particular troubled table status is "i
Fajar Priyanto wrote:
Well, it's not 5.0.x, it's 4.0.25-standard. I'm not sure how the error appears
in the first place. What I notice when I open the database using phpMyadmin
is that that particular troubled table status is "in use".
I'm allowed to ssh into the server, and hopefully I can s
On Wednesday 10 August 2005 06:50 am, Daniel Kasak wrote:
> A hosting provider running 5.0.x? That's whacky.
> When you say "my access to the shell is very limited", what does that
> mean exactly? Can you ssh in and run the 'mysql' command-line client? If
> you can, then do it, and you should be ab
Fajar Priyanto wrote:
This is what I think hit me too, Daniel.
Unfortunately, it's not on my own server (a hosting provider), so my access to
the shell is very limited.
My website is still running, but, I can't export the database using phpMyadmin
anymore, because the troubled table is on th
Timothy Smith wrote:
Hi, Daniel,
First, here's a trick that *should* work for dumping out the data.
Change directory to the MySQL data directory, and then use this little
shell command:
for d in mysql test; do (cd $d; tables=`/bin/ls -1 *.frm | sed -e s,\\.frm,,`;
mysqldump $d $tables); done
This is what I think hit me too, Daniel.
Unfortunately, it's not on my own server (a hosting provider), so my access to
the shell is very limited.
My website is still running, but, I can't export the database using phpMyadmin
anymore, because the troubled table is on the first list of tables.
D
Hi all.
I've been testing out mysql-5.0.10 on my Powerbook ( Gentoo Linux PPC ),
and I've hit an incredibly unfortunate bug. It is demonstrated
adequately with the following:
mysql> use entropy;
Database changed
mysql> show tables;
ERROR 1052 (23000): Column 'TABL
David,
- Alkuperäinen viesti -
Lähettäjä: "David Griffiths" <[EMAIL PROTECTED]>
Vastaanottaja: "Heikki Tuuri" <[EMAIL PROTECTED]>
Kopio: <[EMAIL PROTECTED]>
Lähetetty: Tuesday, October 19, 2004 9:33 PM
Aihe: Re: MySQL Database Corruption (InnoDB),
level locking, and foreign keys for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM
tables
http://www.innodb.com/order.php
Order MySQL support from http://www.mysql.com/support/index.html
..
From: David Griffiths ([EMAIL PROTECTED])
Subject: MySQL Dat
tml
..
From: David Griffiths ([EMAIL PROTECTED])
Subject: MySQL Database Corruption (InnoDB), according to Innodb Hot Backup
This is the only article in this thread
View: Original Format
Newsgroups: mailing.database.myodbc
Date: 2004-09-30 12:23:37 PST
I went to do some work on
I went to do some work on our database last night (dropping large
indexes, which can be time consuming). I checked to ensure that the
backup of that evening had run, but noticed that the size of the backup
was too small compared to previous days (I'm kicking myself for not
emailing the results
> Sent: Thursday, 25 September 2003 2:05 p.m.
> To: [EMAIL PROTECTED]
> Subject: Re: Database corruption
>
>
> We had the same problem when running on linux with the 2.4.18
> kernel. Upgraded to the 2.4.20 and no problems since.
>
> Don't know if that's your
PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 25, 2003 6:21 AM
Subject: Database corruption
Hi,
Advice on the cause of the following table corruption would be much
appreciated.
Some background:
This customer has been running MySQL for 3 or more years, and, for back
up
Hi,
Advice on the cause of the following table corruption would be much
appreciated.
Some background:
This customer has been running MySQL for 3 or more years, and, for back
up purposes, shuts MySQL down each night, takes a snapshot of the tables
for backup, and restarts.
We have sufferred a ta
Hello,
Sorry if this has been covered, but I've searched the archives with no
results.
I have 2 identical servers running mysql 3.23.54a on RedHat linux 7.2
(custom kernel 2.4.17). One is running as master, one slave using mysql
internal replication.
The primary server has a database where one o
I'm new to mysql.
I developed a unix korn shell script that performs three queries on our
database. Our DBA found corruption problems coincidental to my script
development. Is it possible that I could have corrupted the data with three
SELECT queries?
We are pretty fast-and-loose with security a
31 matches
Mail list logo
