Hi Jørn,
>> I would say that this sort of performance drop is not typical. Some
>> users have reported a smaller performance loss in single threaded
>> workloads in 5.6.
>
> But dropping from an average of 1800 jobs per minute down to 300? I don't
> think that should be expected.
I would agree
On Wednesday 22 January 2014 22:56, you wrote:
> Hi Jørn,
>
> > But I must say I'm not very impressed by the speed. I'm running a test on
> > an application that do a lot of reads and writes queries and the general
> > performance has dropped to 50% of the what I had in 5.5.20.
>
> I would say that
Hi Jørn,
But I must say I'm not very impressed by the speed. I'm running a test on an
application that do a lot of reads and writes queries and the general
performance has dropped to 50% of the what I had in 5.5.20.
I would say that this sort of performance drop is not typical. Some
users hav
On Tuesday 14 January 2014 21:51, Jesper Wisborg Krogh wrote:
> Hi Jørn,
>
> On 15/01/2014 04:36, Jørn Dahl-Stamnes wrote:
> > 140114 18:20:08 InnoDB: Error: data file /data/mysql/data/ibdata3 uses
> > page size 1024,
> > 140114 18:20:08 InnoDB: but the only supported page size in this release
> >
Hi Jørn,
On 15/01/2014 04:36, Jørn Dahl-Stamnes wrote:
140114 18:20:08 InnoDB: Error: data file /data/mysql/data/ibdata3 uses page
size 1024,
140114 18:20:08 InnoDB: but the only supported page size in this release
is=16384
140114 18:20:08 InnoDB: Could not open or create data files.
That erro
Hello,
Got a test server with version 5.5.20. I wanted to unmount/mount the disk
where the innodb files was located, so I did a shutdown followed by unmount,
then a mount before I tried to start the MySQL server. But it did not work as
shown in the log below.
I wanted to unmount the disk since
com> wrote:
> Hi there,
>
> I just had my mysql dB crash really badly on a small server I'm running
> and wonder if someone could point me in the right direction. I'm pretty
> basic with mysql... I set up master/slave replication to another site, so
> this could be a
Hi there,
I just had my mysql dB crash really badly on a small server I'm running
and wonder if someone could point me in the right direction. I'm pretty
basic with mysql... I set up master/slave replication to another site, so
this could be a backup, so long as the errors were not
17:46, schrieb Rick James:
> If a crash occurs in the middle of an ALTER, the files may not get cleaned up.
>
>> -Original Message-
>> From: Reindl Harald [mailto:h.rei...@thelounge.net]
>> Sent: Thursday, June 20, 2013 12:57 PM
>> To: mysql@lists.mysql.com
&g
If a crash occurs in the middle of an ALTER, the files may not get cleaned up.
> -Original Message-
> From: Reindl Harald [mailto:h.rei...@thelounge.net]
> Sent: Thursday, June 20, 2013 12:57 PM
> To: mysql@lists.mysql.com
> Subject: Re: How can I drop a table that is n
Hi Frank,
On 20/06/2013 05:00, Franck Dernoncourt wrote:
Hi all,
A table `logs/#sql-ib203` appeared after a MySQL crash due to disk space
shortage while deleting some attributes in a table in the `logs` database
and adding an index.
`USE logs; SHOW TABLES;` does not list the table `logs/#sql
#sql files are temp tables that vanish when the ALTER (or whatever) finishes.
If you find one sitting around, it sounds like a crash happened in the middle
of the ALTER.
> -Original Message-
> From: Reindl Harald [mailto:h.rei...@thelounge.net]
> Sent: Wednesday, June 19, 2013
i know what happened but how get rid of these two bullshit files
after *three years* not touched and used by mysqld
Am 20.06.2013 21:28, schrieb Rick James:
> #sql files are temp tables that vanish when the ALTER (or whatever) finishes.
> If you find one sitting around, it sounds like a
On Thu, Jun 20, 2013 at 3:28 PM, Rick James wrote:
> #sql files are temp tables that vanish when the ALTER (or whatever)
> finishes. If you find one sitting around, it sounds like a crash happened
> in the middle of the ALTER.
Yes the crash happened during an ALTER: the table `logs/#
On Thu, Jun 20, 2013 at 7:13 AM, Denis Jedig wrote:
>
> If you already tried enclosing the table name in backticks (DROP TABLE
> `#sql-ib203`) and using the DROP TEMPORARY TABLE syntax without success,
Yep, no success with:
DROP TEMPORARY TABLE `logs/#sql-ib203`;
DROP TEMPORARY TABLE `/#sql-ib20
This may be a naive question, but I'm not sure I can see you've covered
this: Have you tried "USE logs" before DROP TABLE `#sql-ib203` (without
the "logs/" bit)?
/ Carsten
On 19-06-2013 21:00, Franck Dernoncourt wrote:
Hi all,
A table `logs/#sql-ib203` appea
Franck,
Am 19.06.2013 21:00, schrieb Franck Dernoncourt:
A table `logs/#sql-ib203` appeared after a MySQL crash
the #sql-ib tables are temporarily created during an
ALTER TABLE operation for recovery purposes. Apparently these
temporary tables might stay in certain circumstances even after
Am 19.06.2013 21:00, schrieb Franck Dernoncourt:
> `USE logs; SHOW TABLES;` does not list the table `logs/#sql-ib203`, but
> when trying to `ALTER` the table that was being changed during the crash
> MySQL complains about the existence of the table `logs/#sql-ib203`:
>
>>
Hi all,
A table `logs/#sql-ib203` appeared after a MySQL crash due to disk space
shortage while deleting some attributes in a table in the `logs` database
and adding an index.
`USE logs; SHOW TABLES;` does not list the table `logs/#sql-ib203`, but
when trying to `ALTER` the table that was being
t: Friday, February 01, 2013 10:49 AM
> To: mysql mailing list
> Subject: Can't drop table after crash
>
> We had a power hit and when the server came back we had InnoDB
> corruption. (I can't get out to the internet from the system with the
> db so can I can't paste the
ssage-
>> From: Tom [mailto:livefortheda...@gmail.com]
>> Sent: Wednesday, November 21, 2012 5:17 PM
>> To: mysql@lists.mysql.com
>> Subject: Innodb, MySQL 5.5.28 - Would an incorrect setting in my.cnf
>> cause mysqld to randomly crash on high load?
>>
>&g
t; To: mysql@lists.mysql.com
> Subject: Innodb, MySQL 5.5.28 - Would an incorrect setting in my.cnf
> cause mysqld to randomly crash on high load?
>
> We have a high-end server, 128GB RAM, 32 Core , Xeon, SSD RAID 10 -
> running Ubuntu 12.04 with MySQL 5.5.28 . Doing random imports to large
>
Hi,
We have MySQL cluster 7.2.7 with the following setup.
1 ndb_mgmd, 1 mysqld on one host
2 ndbmtd on another host
We use MySQL cluster Manager known as MCM (v: 1.1.6) to manage the cluster.
We don't use ndb_mgm client at all.
I wanted to simulate and test the restore using ndb_restore.
In or
Hi,
Lately I got this messgae in my errorLog file, need more datails why the DB
was restarted!
120711 19:42:06 mysqld restarted
120711 19:42:06 [Warning] Asked for 196608 thread stack, but got 126976
120711 19:42:07 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery
On Wed, May 2, 2012 at 4:58 AM, vishesh kumar wrote:
> I am getting following in error log
>
>
> 120502 07:52:05 mysqld started
> 120502
> Cc: mysql@lists.mysql.com
> Subject: Re: MySQL Crash when Open_files reach 128
>
> I am getting following in error log
>
> ---
> ---
>
e .
> >>
> >> I didn't set any open_files limit in my.cnf .
> >>
> >> For testing i set open_files_limit to 300 but still MySQL crashing after
> >> 128.
> >>
> >> ~Vishesh
> >>
> >> On Wed, May 2, 2012 at 4:28 PM
idn't set any open_files limit in my.cnf .
>>
>> For testing i set open_files_limit to 300 but still MySQL crashing after
>> 128.
>>
>> ~Vishesh
>>
>> On Wed, May 2, 2012 at 4:28 PM, Reindl Harald wrote:
>>
>>>
>>>
>>>
in my.cnf .
>
> For testing i set open_files_limit to 300 but still MySQL crashing after
> 128.
>
> ~Vishesh
>
> On Wed, May 2, 2012 at 4:28 PM, Reindl Harald wrote:
>
>>
>>
>> Am 02.05.2012 12:52, schrieb vishesh kumar:
>> > Hi Members,
>> >
>&g
,
> >
> > I am using MySQL 5.0.67 . I am facing the problem of MySQL crashing
> > problem . MySQL Crash after every a few minutes . On investigation i
> > noticed that when the Open_files status variable reach 128 MySQL C
Am 02.05.2012 12:52, schrieb vishesh kumar:
> Hi Members,
>
> I am using MySQL 5.0.67 . I am facing the problem of MySQL crashing
> problem . MySQL Crash after every a few minutes . On investigation i
> noticed that when the Open_files status variable reach 128 MySQL Cr
Hi zhongtao,
thank you for reporting this bug. It has been filed as
http://bugs.mysql.com/bug.php?id=60279
Regards,
Roy
On 24.02.11 08.08, tanzhongt wrote:
create table t1(a int);
create table t2(b int);
PREPAREstmt FROM "select sum(b) from t2 group by b having b in (select b from
t1
Hi：
I find a crash bug, version is mysql 5.5.8
Just try:
use test;
drop table if exists t1,t2;
create table t1(a int);
create table t2(b int);
PREPAREstmt FROM "select sum(b) from t2 group by b having b in (select b from
t1)";
execute stmt;
art mysql with new binary as
> basedir and see whether innodb has enabled or not. Check the error log why
> the innodb is getting disabled, make a copy of it here too.
>
> On Tue, Oct 12, 2010 at 2:57 PM, Willy Mularto wrote:
> Hi List,
> Last night accidentally one of my InnoDB t
night accidentally one of my InnoDB table crash. And cause client can
> not connect to MySQL, it always said cannot connect to socket, even the
> daemon is launched. I tried to set innodb_force_recovery from 0 to 6 and
> only number 3 bring back the connection. After that I dump the data and drop
Hi List,
Last night accidentally one of my InnoDB table crash. And cause client can not
connect to MySQL, it always said cannot connect to socket, even the daemon is
launched. I tried to set innodb_force_recovery from 0 to 6 and only number 3
bring back the connection. After that I dump the
Uwe Brauer wrote:
>
> What I had to do in addition was to copy the ibdata1
> *then* I recovered the content of the db.
>
> Thanks a lot
>
>
> Uwe Brauer
>
Uwe,
Congratulations! That's great news! Sorry I didn't know to mention
that step. Where is your 'ibdata1'? Mine is in '/var/lib/mysql' so
(was: hard disk crash: how to discover the db?)
>>>>> On Thu, 09 Sep 2010 18:02:09 -0400, George Larson
>>>>> wrote:
> We do nightly backups at work just by taring the mysql directory. In
> my environment, that is /var/lib/mysql.
> Like this:
> On Thu, 09 Sep 2010 18:02:09 -0400, George Larson
> wrote:
> We do nightly backups at work just by taring the mysql directory. In
> my environment, that is /var/lib/mysql.
> Like this:
> service mysql stop
> cd /var/lib/mysql
> rm -rf *
> tar zxvf file.tar
>
Have you tried testdisk or photorec data recovery application.follow this
link www.cgsecurity.org/
thanks
On Fri, 2010-09-10 at 15:57 +0200, Uwe Brauer wrote:
> > On Fri, 10 Sep 2010 04:43:39 -0400, Mike McMullin
> > wrote:
>
>> On Thu, 2010-09-09 at 18:02 -0400, George Larson wrote:
>>>
>>> Good luck!
>>> G
>
>> While this sounds like an idea, does anyone know if the
If you still have the mysqld binary and you _think_ it is version
5.3.something, you could try this:
strings /usr/libexec/mysqld | grep "5.3.*"
The version # should be somewhere near the top of the output. (Is on my copy
anyway, of 5.0.x)
--
*Johnny Withers*
jwith
I agree with everyone else here.
This NOT a backup job listed here. it is a RESTORE job that is restoring
data previously backed up into a file named 'file.tar' (should probably be
file.tar.gz or file.tgz anyway).
This sequence of commands should never be run on a server that you are
wanting to b
Shawn Green (MySQL) wrote:
> On 9/10/2010 10:01 AM, george larson wrote:
>>
>> Uwe Brauer wrote:
>> ...
>> The only one I know of, for my environment, is /etc/my.cnf. I believe
>> that it can be located elsewhere but you could just use 'find' to find
>> it. I've broken my dev. MySQL many, many
On 9/10/2010 10:01 AM, george larson wrote:
Uwe Brauer wrote:
...
The only one I know of, for my environment, is /etc/my.cnf. I believe
that it can be located elsewhere but you could just use 'find' to find
it. I've broken my dev. MySQL many, many times and that's the only file
I know about ou
Hi Steve.
Steve Staples wrote:
> did I miss the joke here? Why does this backup script look SO wrong,
> and very malicious?
>
> service mysql stop -- stopping mysql... that's fine.
> cd /var/lib/mysql -- changing directories to the /var/lib/mysql, ok...
> fine
> rm -rf * -- WHAT? WHY ARE YOU RE
> On Fri, 10 Sep 2010 10:01:30 -0400, george larson
> wrote:
> The only one I know of, for my environment, is
> /etc/my.cnf. I believe that it can be located
> elsewhere but you could just use 'find' to find it.
> I've broken my dev. MySQL many, many times and that's
> t
did I miss the joke here? Why does this backup script look SO wrong,
and very malicious?
service mysql stop -- stopping mysql... that's fine.
cd /var/lib/mysql -- changing directories to the /var/lib/mysql, ok...
fine
rm -rf * -- WHAT? WHY ARE YOU REMOVING RECUSIVLY and FORCING DELETES on
all t
> On Thu, 09 Sep 2010 18:02:09 -0400, George Larson
> wrote:
> We do nightly backups at work just by taring the mysql directory. In
> my environment, that is /var/lib/mysql.
> Like this:
> service mysql stop
> cd /var/lib/mysql
> rm -rf *
> tar zxvf file.tar
>
Uwe Brauer wrote:
>> On Thu, 09 Sep 2010 18:02:09 -0400, George Larson
>> wrote:
>
>> We do nightly backups at work just by taring the mysql directory. In
>> my environment, that is /var/lib/mysql.
>
>> Like this:
>
>> service mysql stop
>> cd /var/lib/mysql
>>
> On Fri, 10 Sep 2010 04:43:39 -0400, Mike McMullin
> wrote:
> On Thu, 2010-09-09 at 18:02 -0400, George Larson wrote:
>>
>> Good luck!
>> G
> While this sounds like an idea, does anyone know if there are actual
> version idiosyncrasies that need to be looked at fir
> On Fri, 10 Sep 2010 10:57:54 +0200, Joerg Bruehe
> wrote:
> Hi George, everybody!
> George Larson wrote:
>> We do nightly backups at work just by taring the mysql directory. In
>> my environment, that is /var/lib/mysql.
>>
>> Like this:
>>
>> service mysql st
And still, nobody answered the man's actual question: can a Linux mysqld
read mac datafiles ?
I'd say "make a copy and try it". As long as you always keep a copy of the
original files, you're not risking anything. You might run into things
varying from incompatible MySQL versions to different endi
Hi George, everybody!
George Larson wrote:
> We do nightly backups at work just by taring the mysql directory. In
> my environment, that is /var/lib/mysql.
>
> Like this:
>
> service mysql stop
> cd /var/lib/mysql
> rm -rf *
For your own benefit, I hope you don't do that on the mach
On Thu, 2010-09-09 at 18:02 -0400, George Larson wrote:
> We do nightly backups at work just by taring the mysql directory. In
> my environment, that is /var/lib/mysql.
>
> Like this:
>
> service mysql stop
> cd /var/lib/mysql
> rm -rf *
> tar zxvf file.tar
> rm -rf ib_logfile*
> chown -R mysql.
We do nightly backups at work just by taring the mysql directory. In
my environment, that is /var/lib/mysql.
Like this:
service mysql stop
cd /var/lib/mysql
rm -rf *
tar zxvf file.tar
rm -rf ib_logfile*
chown -R mysql.mysql
service mysql start
Something similar might work for you. Somebody wit
andrew.2.mo...@nokia.com wrote:
Try using the failed hdd as a slave in a Linux machine.
You might find that the hdd won't boot to OS but may have enough in it to
access the file system.
I have done that already and I have access. But I don't know how to
extract the db (via dump) since the
Try using the failed hdd as a slave in a Linux machine. You might find that the
hdd won't boot to OS but may have enough in it to access the file system.
- Reply message -
From: "ext Uwe Brauer"
Date: Thu, Sep 9, 2010 21:31
Subject: hard disk crash: how to discover the
Hello
This is a real nightmare. A Mac crashed, the hard disk could
be saved. Right now it can't be booted.
But I don't know precisely the version of the OS
(most likely Mac X 10.4), nor the version of mysql (most
likely 5.3.x) and to make things worse I did not generate a
dump.
So is there any c
Dear Nilnandan,
Thanks for the quick reply.
But this particular variable is not working in only one proc call...but
rest all procedures creating temporary tables, does not affect my
replication slaves.
So I am not able to identify the problem.
Here's the snapshot of my procedure which is
Hi Manasi,
Please try with this one.
Replicate_Wild_Ignore_Table = mydb\temp_.%
Regards,
Nilnandan Joshi
Manasi Save wrote:
Hi All,
I have kept
Replicate_Wild_Ignore_Table = mydb%.temp_%
this is temporary table which i want should not be replicated. But
still it is getting replicated an
Hi All,
I have kept
Replicate_Wild_Ignore_Table = mydb%.temp_%
this is temporary table which i want should not be replicated. But still
it is getting replicated and slave is getting crashed.
any input will be a great help.
--Thanks and Regards, Manasi Save Artificial Machines
Private Li
Dear Shawn,
Thanks for the quick reply.
To your points, First I have a query regarding your last line if I want
to run master-master replication I should run it in active-passive mode.
Does that mean that I should run only one master at a time. But I am
doing it because I am not keeping two
Hello Manasi,
Manasi Save wrote:
Dear All,
I am using MySQL Master-Master Replication.
Where most of the times it is happening that my slave crashes with two
errors either :-
1. Duplicate Entry (Error No:- 1062)
That means that a row with the same PRIMARY or UNIQUE key value(s)
already
Dear All,I am using MySQL Master-Master Replication.
Where most of the times it is happening that my slave crashes with two
errors either :- 1. Duplicate Entry (Error No:- 1062)2. Does not
find the row for update or delete. (Error No :- 1032)Well I google
the problem but unable to find exact reaso
rade_errors e WHERE e.orderno
= orders.orderno)
GROUP BY orders.orderno, a.alias, orders.size, currency_list.code
LIMIT 100
thd->thread_id=590766
thd->killed=NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is
Hi PJ,
Try adding "innodb_force_recovery = 4" to the mysqld section of your
config file before restarting the server.If you can dump your tables
using "4" then only some data on corrupt individual pages is lost. If
you have to use innodb_force_recovery = 6, that means your db pages
are left in an
Hi,
any message on the error log? Have you tried restarting the mysql server?
On Tue, May 26, 2009 at 7:24 PM, PJ wrote:
> Hydro Quebec just f***ed my server just as I was booting up three
> machines; XP is ok, FreeBSD 7.1 is the one with mysql problem, FreeBSD
> 4.10 - don't know, but boots ok
Hydro Quebec just f***ed my server just as I was booting up three
machines; XP is ok, FreeBSD 7.1 is the one with mysql problem, FreeBSD
4.10 - don't know, but boots ok. Result: can't access database. One
table seems to abort mysqld. PhpMyAdmin connects to all databases except
one.
mysql> CHECK TA
I have opened a bug about this issue: http://bugs.mysql.com/bug.php?id=44914
Joel
On Tue, May 12, 2009 at 10:55 PM, Joel Heenan wrote:
> Mysql List,
>
> I have a crash that has occured a number of times on a production CentOS
> 4.4 machine. It occurs when using a product calle
Mysql List,
I have a crash that has occured a number of times on a production CentOS 4.4
machine. It occurs when using a product called Interspire Email Marketer and
doing an import of some 30,000 email addresses. Unfortunately, I have not
been able to reproduce the crash myself (I have tried
Hello,
We see this error in the event viewer.
The application, C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt.exe,
generated an
application error The error occurred on 12/04/2008 @ 13:26:05.398 The exception
generated
was c005 at address 005471B4 (mysqld_nt).
This is repeating daily
il
now! ;)) The mysql manual just says 'if you have a crashed table you can
repair it.' Well...
1. What IS a table crash? What file/relation/... gets corrupted? And how
does table recovery basically work?
2. If you had a crashed table: Where would you start looking for the
reason? And
anual just says 'if you have a crashed table you can
repair it.' Well...
1. What IS a table crash? What file/relation/... gets corrupted? And how
does table recovery basically work?
2. If you had a crashed table: Where would you start looking for the
reason? And where would you look ne
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
my replication slave crashed. Now, I am unable to restart with following
error message:
081021 21:34:21 [Note] Slave SQL thread initialized, starting
replication in log 'log.000129' at position 28457291, relay log
'/video/mysql/mysqld-relay-bin.0
On Wed, Oct 08, 2008 at 06:43:46PM -0400, Michael Dykman wrote:
> Assuming all of these databases reside on the same filesystem, it
> looks to me like your disk is failing. Do you have backups you can
> restore from? YOu might wnt to swp out your disks for new hardware
> before you try.
I know t
Hi.
I had a very big trouble with my MySQL databases. After four years
of usage of the MySQL all DBs crashed.
Each table is marked as crashed and myisamchk trucates the table, mostly to
zero rows. Some of them are not totaly dropped:
# myisamchk -o klik_cas.MYI
- recovering (with keycache) MyISAM
artup.
>> >>
>> >> Is there something about how their MySQL is setup on their system that
>> >> could cause such a crash?
>> > [snip]
>> >>mysql_library_init(num_elements, server_options, server_groups);
>> >>m_db = my
of us
> >> that use 5.1, including myself. However the following backtrace is
> >> from the second person to have this issue. Its repeatable, happens at
> >> startup.
> >>
> >> Is there something about how their MySQL is setup on their system that
&
llowing backtrace is
>> from the second person to have this issue. Its repeatable, happens at
>> startup.
>>
>> Is there something about how their MySQL is setup on their system that
>> could cause such a crash?
> [snip]
>>mysql_library_init(num
llowing backtrace is
>> from the second person to have this issue. Its repeatable, happens at
>> startup.
>>
>> Is there something about how their MySQL is setup on their system that
>> could cause such a crash?
> [snip]
>>mysql_library_init(num
On Fri, Sep 26, 2008 at 2:27 PM, Martin Gainty <[EMAIL PROTECTED]> wrote:
> 2 items-
>
> check that the my.cnf file cannot be found on your path
Yea its right, plus we tried switching to --no-defaults instead of
specifying an (empty) file. That didn't work either.
> or your server groups are (usu
[EMAIL PROTECTED]
> To: mysql@lists.mysql.com
> Subject: Re: Odd crash with MySQL Embedded 5.1.28
> CC: [EMAIL PROTECTED]; [EMAIL PROTECTED]
>
> On Fri, Sep 26, 2008 at 9:37 AM, Ian Monroe <[EMAIL PROTECTED]> wrote:
> > So we're using MySQL Embedded in Amarok, it work
happens at
> startup.
>
> Is there something about how their MySQL is setup on their system that
> could cause such a crash?
[snip]
>mysql_library_init(num_elements, server_options, server_groups);
> m_db = mysql_init(NULL); // <- crash happens HERE
So we did figure out that
could cause such a crash?
Thread 1 (Thread 0xb397d960 (LWP 23945)):
[KCrash Handler]
#6 0xb750550d in ?? () from /lib/tls/i686/cmov/libc.so.6
#7 0xb7506cad in malloc () from /lib/tls/i686/cmov/libc.so.6
#8 0xaf0525af in my_malloc (size=1228, my_flags=48) at my_malloc.c:34
#9 0xaf069d
it isn't found when I do a CHECK TABLE on
*any* of the tables. InnoDB is running in super-safe (double-write) mode.
The most recent crash spit out this memory status:
Memory status:
Non-mmapped space allocated from system: 541413376
Number of free chunks: 7121
Number of fastbin block
or some time and can't
> seem to get around MySQL crashing at about 1GB of backup data. (the database
> is about 400GB).
>
> I have a page corruption, but it isn't found when I do a CHECK TABLE on
> *any* of the tables. InnoDB is running in super-safe (double-write) mode.
unning in super-safe (double-write) mode.
The most recent crash spit out this memory status:
Memory status:
Non-mmapped space allocated from system: 541413376
Number of free chunks: 7121
Number of fastbin blocks: 0
Number of mmapped regions:18
Space in mmapped regions: -206326988
0
InnoDB: ## Diagnostic info printed to the standard error stream
InnoDB: Error: semaphore wait has lasted > 600 seconds
InnoDB: We intentionally crash the server, because it appears to be
hung.
080710 4:34:17InnoDB: Assertion failure in thread 34382814000 in file
srv0srv.c line 2093
InnoDB: We i
I run 4.1.20 in master/master for nagios clustering. Everything was
working fine until both machines went down due to power failure in the
IDC. On powering back up one of the machines has come back fine but on
the 'secondary' bearing in mind this is master/master but actually the
01 machin
Hi
I run 4.1.20 in master/master for nagios clustering. Everything was
working fine until both machines went down due to power failure in the
IDC. On powering back up one of the machines has come back fine but on
the 'secondary' bearing in mind this is master/master but actually the
01 machi
Check the permission on mysql database realted files, it shoud be owned by
mysql user.
regards
anandkl
On Feb 13, 2008 4:42 PM, Saravanan <[EMAIL PROTECTED]> wrote:
> Hi List,
>
> I got crash when i was creating procedure and it listed the following
> error
>
> *** glibc
Hi List,
I got crash when i was creating procedure and it listed the following error
*** glibc detected *** /usr/local/mysql2/libexec/mysqld: corrupted
double-linked list: 0x0b4ae810 ***
=== Backtrace: =
/lib/libc.so.6[0x8949be]
/lib/libc.so.6(cfree+0x90)[0x897fc0]
/usr/lib/libstdc
e
From: Krishna Chandra Prajapati [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 13, 2008 8:05 AM
To: Eli Shemer
Subject: Re: crash
Hi,
The below information shows that innodb data get crashed and then started
the recovery of data. During recovery of data there was a memory shortage
(Out
]
Sent: Wednesday, February 13, 2008 8:05 AM
To: Eli Shemer
Subject: Re: crash
Hi,
The below information shows that innodb data get crashed and then started
the recovery of data. During recovery of data there was a memory shortage
(Out of memory). At last recovery gets completed.
Thanks
Source distribution
Number of processes running now: 0
080212 17:23:24 mysqld restarted
080212 17:23:25 InnoDB: Started; log sequence number 0 43743
080212 17:23:25 [Note] Recovering after a crash using mysql-bin
080212 17:23:25 [Note] Starting crash recovery...
080212 17:23:25 [Note] Cra
See Thread at: http://www.techienuggets.com/Detail?tx=24273 Posted on behalf of
a User
Help! I'm still facing this problem. I can run a check error successfully but
when I try to dump the database using MySQL Administrator halfway through one
table the server crashes. See message at the end. I
See Thread at: http://www.techienuggets.com/Detail?tx=24273 Posted on behalf of
a User
Hi I'm running 5.0.51a on Windows machine. The server crashes with:
080210 15:56:38 InnoDB: Page checksum 2545965801, prior-to-4.0.14-form
checksum 1667729874
InnoDB: stored checksum 1195984440, prior-to-4.0
I've got MySQL 5.0.55a running on a Windows XP system. All tables in the
active database on the system are innodb. The startup log says that innodb
recovery completed and that connections are available. Meanwhile, mysql is
writing to the hdd at around 2MB/sec according to process explorer.
I ca
o: mysql@lists.mysql.com
> Subject: Unable to restart after crash
>
> Hi,
>
> My mysql server crashed last night, and when it rebooted, was unable to
> restart. Here is the error log:
>
> Jan 13 00:12:54 localhost mysqld_safe[1324]: started
> Jan 13 00:12:55 localhost my
1 - 100 of 672 matches
Mail list logo
