I have a table with over 26 million records that experiences a high volume of traffic.
Recently, query results became a little screwy; upon investigation it was found that
the table and the index were fouled up.
The results of an isamchk on the table yielded:
Checking ISAM file: /usr8/hydrolo
Joel Fowler <[EMAIL PROTECTED]> writes:
> I've also reported this problem to Red Hat' Bugzilla as I understand
> they're responsible for the /etc/logrotate.d/mysql script. It's
> Bugzilla [Bug 51711] "Changed - MySQL looses bin-logs during
> logrotate".
3.23.41-1 uses a new method for flushing l
sys/mysqld ] && \
>>>> /bin/kill -HUP `/bin/cat /var/run/mysqld/mysqld.pid` || /bin/true
>>>> endscript
>>>> postrotate
>>>> [ -e /var/lock/subsys/mysqld ] && \
>>>> /bin/kill -HUP `/bin/cat /va
No, unfortunately they just seem to be gone along with the integrity of
most good recovery strategies.
Joel Fowler
==
At 01:16 PM 8/14/01 -0500, Gerald Clark wrote:
>I don't recall ever losing a log.
>Are you sure logrotate isn't renaming it
postrotate
>>> [ -e /var/lock/subsys/mysqld ] && \
>>> /bin/kill -HUP `/bin/cat /var/run/mysqld/mysqld.pid` ||
>>> /bin/true
>>> endscript
>>> }
>>> Problem Synopsis:
>>> ==
>>
[ -e /var/lock/subsys/mysqld ] && \
>> /bin/kill -HUP `/bin/cat /var/run/mysqld/mysqld.pid` || /bin/true
>> endscript
>>}
>>Problem Synopsis:
>>==
>>1. /etc/logrotate.d/mysql executes a "kill -HUP " during pre
te.d/mysql executes a "kill -HUP " during pre
> and postrotate operations.
> 2. -HUP causes mysqld to discard all existing bin-logs (DISASTER) and
> start a new one.
> 3. This destroys recovery strategies built on bin-logs.
> It also (as far as I can tell) will cause repli
ogrotate.d/mysql executes a "kill -HUP " during pre
and postrotate operations.
2. -HUP causes mysqld to discard all existing bin-logs (DISASTER) and start
a new one.
3. This destroys recovery strategies built on bin-logs.
It also (as far as I can tell) will cause replication to loose
]; Rischbode, Horst;
[EMAIL PROTECTED]
Subject: Re[2]: AW: password-recovery for root-user?
>
http://www.mysql.com/documentation/mysql/bychapter/manual_Privilege_system.h
FYI: The link you requested was not found.
Sie schrieben am Mittwoch, 18. Juli 2001, 16:17:24:
>>mysqld --skip-gra
mysql/bychapter/manual_Privilege_system.h
> tml
> -ravi.
> -Original Message-
> From: Andy Tanner [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 18, 2001 10:03 AM
> To: Werner Stuerenburg; Rischbode, Horst
> Cc: [EMAIL PROTECTED]
> Subject: RE: AW: password-recove
ode, Horst
Cc: [EMAIL PROTECTED]
Subject: RE: AW: password-recovery for root-user?
Similarly - how about
- take a copy of you original mysql database tables
- overwrite the mysql database tables with the original installation tables
- login as root (the password will be blank)
- import y
Message-
From: Werner Stuerenburg [mailto:[EMAIL PROTECTED]]
Sent: 18 July 2001 13:26
To: Rischbode, Horst
Cc: [EMAIL PROTECTED]
Subject: Re: AW: password-recovery for root-user?
You can reinstall the complete system from scratch, if you are
superuser to that system. Would be the easiest way to
You can reinstall the complete system from scratch, if you are
superuser to that system. Would be the easiest way to do it, I
guess.
> I'm trying to get the root-password to be deleted or set to a
> new value without knowing the old password. (Forgotten...)
table
--
Herzlich
Werner Stuerenburg
Selamat pagi saja.
- Original Message -
From: Rischbode, Horst <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 18, 2001 3:23 PM
Subject: AW: password-recovery for root-user?
mit freundlichem Gruss
Horst Rischbode
---
Deutsche Telekom AG Tel: ++49
che Nachricht-
> Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Gesendet am: Mittwoch, 18. Juli 2001 10:18
> An: Rischbode, Horst
> Betreff: Re: password-recovery for root-user?
>
> Your message cannot be posted because it appears to be either spam or
> simply off
they has humane
users backups are needed!
I hope this help?
Simon
-Original Message-
From: Paul Kelly [mailto:[EMAIL PROTECTED]]
Sent: 25 June 2001 17:16
To: '[EMAIL PROTECTED]'
Subject: Recovery Problem
Hi All,
sorry if this is duplicated...
I'm trying to reco
Hi All,
sorry if this is duplicated...
I'm trying to recover data from a table after all rows in the table were accidentally
deleted.
I have looked at the .MYD file and all of the information still seems to be there,
albeit, flagged as deleted (I assume).
Is there any way to recover t
Hi All,
I'm trying to recover data from a table after all rows in the table were
accidentally deleted.
I have looked at the .MYD file and all of the information still seems to be there,
albeit, flagged as deleted (I assume).
Is there any way to recover this information, and "undelete"
Greetings list,
I have a semi large table (~10gig) that when I run a select query
from the table it gives me an errno 145. So I run myisamchk on the table,
as it is a myisam table. However, my problem is, when I run myisamchk it
tells me that the table has about 20 million data records, th
Hi,
> The server where the db was located got hacked and I had to
> reinstall the whole thing. The old HD is preserved as was
> and the server got a new HD. I moved the old db to the new
> disk and when I try to access it, I get the following error:
>
> mysql> use thedb;
> Can't read dir of '
"Kay Aleksic" <[EMAIL PROTECTED]> wrote:
> I am dealing with my first MySQL server/db, and I ran into some trouble.
>
> The server where the db was located got hacked and I had to reinstall the
> whole thing. The old HD is preserved as was and the server got a new HD. I
> moved the old db to the n
errno 13 is 'permission denied'.
It looks like your permissions aren't set correctly.
-Jeff
- Original Message -
From: "Kay Aleksic" <[EMAIL PROTECTED]>
To: "MySQL List (E-mail)" <[EMAIL PROTECTED]>
Sent: Wednesday, May 09, 2001 3:10 PM
database recovery (errcode 13)?
Hi list,
I am dealing with my first MySQL server/db, and I ran into some trouble.
The server where the db was located got hacked and I had to reinstall the
whole thing. The old HD is preserved as was and the server got a new HD. I
moved the old db to the new disk an
Hi list,
I am dealing with my first MySQL server/db, and I ran into some trouble.
The server where the db was located got hacked and I had to reinstall the
whole thing. The old HD is preserved as was and the server got a new HD. I
moved the old db to the new disk and when I try to access it, I g
Hi!
> "Peter" == Peter Zaitsev <[EMAIL PROTECTED]> writes:
Peter> Hello mysql,
Peter> It seems like mysql sometimes tries to hard to repair the table with
Peter> myisam tables with fixed row format.
Peter> I've had a chance to several times found data in one of the tables
Peter> co
Hello mysql,
It seems like mysql sometimes tries to hard to repair the table with
myisam tables with fixed row format.
I've had a chance to several times found data in one of the tables
completely destroyed - the data looked like random.
mysql> select * from g01layers_stat_cities limit
On Thursday 12 April 2001 14:03, Ken Menzel wrote:
> Hi Sasha,
>
> > Looks like you found two bugs at once. The first one is that someone
> mysqld
> > segfaults, probably a bug in processing some query or possibly some
> OS issue,
> > but there is not much we can tell at this point - the only way
Hi Sasha,
> Looks like you found two bugs at once. The first one is that someone
mysqld
> segfaults, probably a bug in processing some query or possibly some
OS issue,
> but there is not much we can tell at this point - the only way to
track it
> down would be if you had full logging enabled and
On Thursday 12 April 2001 10:49, Ken Menzel wrote:
> We had a crash of MySQL this morning for some reason. (Why who
> knows!) The real problem was it would not restart until the log.*
> files were deleted. It looks like it was trying to perform a recovery
> on a dropped database.
We had a crash of MySQL this morning for some reason. (Why who
knows!) The real problem was it would not restart until the log.*
files were deleted. It looks like it was trying to perform a recovery
on a dropped database. The server would not start. This is not cool!
We dropped the test
>Hi
>
>We are evaluating various RDBMS for use on within an airborne server
>(Embedded NT4.0) environment.
>
>This environment does not have reliable power. Aircraft are powered cycled
>without regard for delicate OS environments etc.
Here in south Arlington, Va., the power also cycles without re
Burkies, Norman writes:
> Hi
>
> We are evaluating various RDBMS for use on within an airborne server
> (Embedded NT4.0) environment.
>
> This environment does not have reliable power. Aircraft are powered cycled
> without regard for delicate OS environments etc.
>
> We like MySql because it is
Hi
We are evaluating various RDBMS for use on within an airborne server
(Embedded NT4.0) environment.
This environment does not have reliable power. Aircraft are powered cycled
without regard for delicate OS environments etc.
We like MySql because it is fairly lightweight (regards processor/mem
Readers of the mailing list,
when I was writing about recovery in the upcoming Innobase manual,
I realized that a logical log used in MySQL in the roll-forward recovery
from a backup does not work properly. The problem is that
the log does not contain enough information on the snapshot a
Elekes Attila wrote:
>
> Steve Ruby wrote:
>
> > Elekes Attila wrote:
> > >
> > > Hi!
> > >
> > > The mysql server (version 3.22.32-4) has hanged up, and the restarting
> > > causes a part of the
> > > *.ISM and *.ISD files are gone. Unfortuanetly, I have not got a backup
> > > from these files
Steve Ruby wrote:
> Elekes Attila wrote:
> >
> > Hi!
> >
> > The mysql server (version 3.22.32-4) has hanged up, and the restarting
> > causes a part of the
> > *.ISM and *.ISD files are gone. Unfortuanetly, I have not got a backup
> > from these files :(
> > Is there any method to recover the my
Elekes Attila wrote:
>
> Hi!
>
> The mysql server (version 3.22.32-4) has hanged up, and the restarting
> causes a part of the
> *.ISM and *.ISD files are gone. Unfortuanetly, I have not got a backup
> from these files :(
> Is there any method to recover the mysql tables from the remaining
> *.M
Hi!
The mysql server (version 3.22.32-4) has hanged up, and the restarting
causes a part of the
*.ISM and *.ISD files are gone. Unfortuanetly, I have not got a backup
from these files :(
Is there any method to recover the mysql tables from the remaining
*.MYD, *MYI and *.frm
files ? Thanks for AN
201 - 238 of 238 matches
Mail list logo
